Short answer: Drop the "Microsoft Dynamics 365 → Create Dynamics Opportunity" 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 |
|---|---|---|---|
Topic name | string | Required | Opportunity topic (display name) |
Estimated Value estimated_value | number | Optional | Estimated revenue |
Estimated Close Date estimated_close_date | date | Optional | Estimated close date (YYYY-MM-DD) |
Account ID account_id | string | Optional | GUID of the account this opportunity is linked to |
Contact ID contact_id | string | Optional | GUID of the primary contact |
{"name": "{{trigger.name}}","estimated_value": "{{trigger.estimated_value}}","estimated_close_date": "2025-06-30","account_id": "{{trigger.account_id}}","contact_id": "{{trigger.contact_id}}"}
{"name": "Acme Q2 expansion","createdon": "2025-01-15T10:00:00Z","opportunityid": "22222222-2222-2222-2222-222222222222","estimatedvalue": 50000}
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.