Short answer: Drop the "Microsoft Dynamics 365 → Create 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 |
|---|---|---|---|
First Name first_name | string | Optional | Contact first name |
Last Name last_name | string | Required | Contact last name |
Email email | Optional | Primary email | |
Phone phone | string | Optional | Business phone |
Job Title job_title | string | Optional | Job title |
Parent Account ID company_id | string | Optional | GUID of an existing account to link as parent |
{"first_name": "{{trigger.first_name}}","last_name": "{{trigger.last_name}}","email": "{{trigger.from}}","phone": "{{trigger.phone}}","job_title": "{{trigger.job_title}}"}
{"lastname": "Doe","contactid": "00000000-0000-0000-0000-000000000001","createdon": "2025-01-15T10:00:00Z","firstname": "Jane","emailaddress1": "jane@example.com"}
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.