Short answer: Drop the "Microsoft Dynamics 365 → Create Dynamics Task" 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 |
|---|---|---|---|
Subject subject | string | Required | Task subject |
Description description | string | Optional | Task details |
Due Date due_date | datetime | Optional | Scheduled end (ISO 8601) |
Priority priority_code | select | Optional | — |
Regarding Contact ID regarding_contact_id | string | Optional | Contact GUID this task is regarding (optional) |
{"subject": "{{trigger.subject}}","description": "{{trigger.description}}","due_date": "2025-06-30T17:00:00Z","priority_code": "{{trigger.priority_code}}","regarding_contact_id": "{{trigger.regarding_contact_id}}"}
{"subject": "Follow up with Jane Doe","createdon": "2025-01-15T10:00:00Z","activityid": "33333333-3333-3333-3333-333333333333"}
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.