Short answer: Drop the "Microsoft Dynamics 365 → Update 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 |
|---|---|---|---|
Account ID account_id | string | Required | GUID of the account |
Name name | string | Optional | New account name |
Website website | string | Optional | New website URL |
Phone phone | string | Optional | New main phone |
Annual Revenue revenue | number | Optional | New annual revenue |
{"account_id": "{{trigger.account_id}}","name": "{{trigger.name}}","website": "{{trigger.website}}","phone": "{{trigger.phone}}","revenue": "{{trigger.revenue}}"}
{"name": "Acme Corp","accountid": "11111111-1111-1111-1111-111111111111","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.