Short answer: Drop the "Microsoft Dynamics 365 → Create Dynamics Account" 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 |
|---|---|---|---|
Name name | string | Required | Account (company) name |
Website website | string | Optional | Website URL |
Phone phone | string | Optional | Main phone |
Industry Code industry | string | Optional | Industry code (integer per Dynamics 365 option set) |
Annual Revenue revenue | number | Optional | Annual revenue |
{"name": "{{trigger.name}}","website": "{{trigger.website}}","phone": "{{trigger.phone}}","industry": "{{trigger.industry}}","revenue": "{{trigger.revenue}}"}
{"name": "Acme Corp","accountid": "11111111-1111-1111-1111-111111111111","createdon": "2025-01-15T10: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.