Short answer: Drop the "Microsoft Dynamics 365 → Update Dynamics Contact" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Contact ID contact_id | string | Required | GUID of the contact to update |
First Name first_name | string | Optional | New first name |
Last Name last_name | string | Optional | New last name |
Email email | Optional | New primary email | |
Phone phone | string | Optional | New business phone |
Job Title job_title | string | Optional | New job title |
{"contact_id": "{{trigger.contact_id}}","first_name": "{{trigger.first_name}}","last_name": "{{trigger.last_name}}","email": "{{trigger.from}}","phone": "{{trigger.phone}}"}
{"lastname": "Doe-Smith","contactid": "00000000-0000-0000-0000-000000000001","firstname": "Jane","modifiedon": "2025-01-16T12:00:00Z"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.