Execute Action
dynamics_crm.execute_action
ActionCRM & salesconnection required
Calls the Microsoft Dynamics 365 API with the connection's credentials.
Call a Dataverse Web API action — a built-in message such as WinOpportunity or Merge, or a custom action or custom API.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Microsoft Dynamics 365
- Secret shape
- {"client_id": "…", "client_secret": "…", "refresh_token": "…"}
- Config it needs
- org_url, tenant, api_version
- Resolved by
- config.connection_id, else node.connection_id
Configuration
4 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
action The action name, without a namespace — for example WinOpportunity, Merge or new_AddNoteToContact. | string | Yes | — | — | WinOpportunity |
entity_set For an action bound to a table, the entity set it is bound to. Leave empty for an unbound action. | string | No | — | — | — |
record_id For an action bound to a single row, that row's id. Leave empty for an action bound to the whole collection. | string | Conditional | — | only with entity_set | — |
parameters The action's parameters as a JSON object. An entity parameter needs its type spelled out, for example {"@odata.type": "Microsoft.Dynamics.CRM.letter"}. | object | No | — | — | {"@odata.type":"Microsoft.Dynamics.CRM.letter"} |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"action": "WinOpportunity",
"parameters": {
"@odata.type": "Microsoft.Dynamics.CRM.letter"
}
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
action The action that was called. | string | — |
result The action's response, empty for an action that returns nothing (204 No Content). | object | — |
{
"action": "",
"result": {}
}Notes
- A bound action is called on the row's URL with the Microsoft.Dynamics.CRM namespace, which this node adds; Dataverse rejects a bound call without it.
Related Microsoft Dynamics 365 nodes
See Execute Action run in a workflow.
In a technical demo we add the Microsoft Dynamics 365 connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.