When a lead stage updates in Kommo, move entity funnel stage in Uspacy.
When a lead stage updates in Kommo, move entity funnel stage in Uspacy.
Google for Startups AcceleratorHow Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Uspacy Explore Uspacy →
TriggersFires when a new contact or lead is added to Uspacy.
Fires when a field on a contact changes in Uspacy.
Fires when a deal, case or record moves to a new stage in Uspacy.
Fires when a deal is marked won in Uspacy.
Creates or updates a contact in Uspacy.
Creates a new deal in Uspacy.
Moves a deal or record to a new stage in Uspacy.
Logs a call, email, or note against a record in Uspacy.
Kommo Explore Kommo →
TriggersFires when a new contact or lead is added to Kommo.
Fires when a field on a contact changes in Kommo.
Fires when a deal, case or record moves to a new stage in Kommo.
Fires when a deal is marked won in Kommo.
Creates or updates a contact in Kommo.
Creates a new deal in Kommo.
Moves a deal or record to a new stage in Kommo.
Logs a call, email, or note against a record in Kommo.
More Uspacy + Kommo workflows
See all Uspacy + Kommo integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “When a lead stage updates in Kommo, move entity funnel stage in Uspacy.” between Uspacy and Kommo?
Yes — describe it in the box above and Knit's Integrations Agent researches Uspacy and Kommo's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
Why would a team need to connect two CRM systems?
Common reasons include a merger or acquisition where each side kept its own CRM, or separate teams (direct sales vs. partner-led) standardized on different tools that still need shared contact and deal data.
Does this cause duplicate contact records?
No — the Agent can match on email or a shared identifier to update an existing contact in the other system instead of creating a duplicate.