Create CRM contacts from app records
When a new record is created in Movement, create or update the contact in Close.
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.
Movement Explore Movement →
TriggersFires when a new record is added to an app built in Movement.
Fires when a record changes in an Movement app.
Fires when a record is deleted in an Movement app.
Adds a new record to an app built in Movement.
Updates an existing record in an Movement app.
Removes a record from an Movement app.
Close Explore Close →
TriggersFires when a new contact or lead is added to Close.
Fires when a field on a contact changes in Close.
Fires when a deal, case or record moves to a new stage in Close.
Fires when a deal is marked won in Close.
Creates or updates a contact in Close.
Creates a new deal in Close.
Moves a deal or record to a new stage in Close.
Logs a call, email, or note against a record in Close.
More Movement + Close workflows
See all Movement + Close integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Create CRM contacts from app records” between Movement and Close?
Yes — describe it in the box above and Knit's Integrations Agent researches Movement and Close'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.
Can a record in Movement create a CRM contact?
Yes. When a record is created in Movement, Close can create or update the matching contact, company or deal.
Will CRM changes show up in my app?
When a deal or contact changes in Close, the matching record in Movement can be updated so app users always see current data.