When receive lead in Slimster, sync it to Microsoft Dynamics 365 CRM.
When a new lead is received in Slimster, create a new lead record in Microsoft Dynamics 365 CRM.
See all Slimster + Microsoft Dynamics 365 integrations or talk to a human
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.
Slimster Explore Slimster →
TriggersFires when a new lead or contact is created in Slimster.
Fires when a deal moves to a new stage in Slimster.
Fires when a deal is marked won in Slimster.
Fires when a field on a contact changes in Slimster.
Creates or updates a contact in Slimster.
Creates a new deal in Slimster.
Moves a deal to a new stage in Slimster.
Logs a call, email, or note against a record in Slimster.
Microsoft Dynamics 365 Explore Microsoft Dynamics 365 →
TriggersFires when a new lead or contact is created in Microsoft Dynamics 365.
Fires when a deal moves to a new stage in Microsoft Dynamics 365.
Fires when a deal is marked won in Microsoft Dynamics 365.
Fires when a field on a contact changes in Microsoft Dynamics 365.
Creates or updates a contact in Microsoft Dynamics 365.
Creates a new deal in Microsoft Dynamics 365.
Moves a deal to a new stage in Microsoft Dynamics 365.
Logs a call, email, or note against a record in Microsoft Dynamics 365.
More Slimster + Microsoft Dynamics 365 workflows
See all Slimster + Microsoft Dynamics 365 integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “When receive lead in Slimster, sync it to Microsoft Dynamics 365 CRM.” between Slimster and Microsoft Dynamics 365?
Yes — describe it in the box above and Knit's Integrations Agent researches Slimster and Microsoft Dynamics 365'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.