When new business card in Sansan, sync it to Microsoft Dynamics 365 CRM.
When a new business card is added in Sansan, sync customer data into Microsoft Dynamics 365 CRM.
See all Sansan + Microsoft Dynamics 365 integrations or talk to a human
4.9/5 on G2·
Google for Startups Accelerator
How 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.
Sansan Explore Sansan →
TriggersFires when a new contact or lead is added to Sansan.
Fires when a field on a contact changes in Sansan.
Fires when a deal, case or record moves to a new stage in Sansan.
Fires when a deal is marked won in Sansan.
Creates or updates a contact in Sansan.
Creates a new deal in Sansan.
Moves a deal or record to a new stage in Sansan.
Logs a call, email, or note against a record in Sansan.
Microsoft Dynamics 365 Explore Microsoft Dynamics 365 →
TriggersFires when a new contact or lead is added to Microsoft Dynamics 365.
Fires when a field on a contact changes in Microsoft Dynamics 365.
Fires when a deal, case or record moves to a new stage in Microsoft Dynamics 365.
Fires when a deal is marked won in Microsoft Dynamics 365.
Creates or updates a contact in Microsoft Dynamics 365.
Creates a new deal in Microsoft Dynamics 365.
Moves a deal or record to a new stage in Microsoft Dynamics 365.
Logs a call, email, or note against a record in Microsoft Dynamics 365.
More Sansan + Microsoft Dynamics 365 workflows
Sync newly created leads across CRM platforms
When a new lead is captured in Sansan, automatically create or update the matching contact in Microsoft Dynamics 365 to keep records synchronized.
See details
Mirror deal outcomes in secondary pipeline accounts
Whenever a deal is marked won in Microsoft Dynamics 365, update the corresponding opportunity stage in Sansan for unified revenue reporting.
See details
Log pipeline stage updates as CRM activities
When a deal moves forward in Sansan, log a status update activity on the corresponding account record in Microsoft Dynamics 365.
See details
See all Sansan + Microsoft Dynamics 365 integrations → · Browse the full workflow library →
Common questions
Can Knit build “When new business card in Sansan, sync it to Microsoft Dynamics 365 CRM.” between Sansan and Microsoft Dynamics 365?
Yes — describe it in the box above and Knit's Integrations Agent researches Sansan 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.