D365 Execute Action

Description

The D365 Execute Action node allows you to execute a custom or system action within Microsoft Dynamics 365 / Dataverse.
This includes both global actions (not bound to a specific record) and entity-bound actions (executed against a specific record).

It can be used to automate business logic already defined in Dynamics, such as:

• Invoking a workflow or process
• Triggering plug-ins or Power Automate flows
• Executing system-defined actions (e.g., WinOpportunity, QualifyLead)
• Running custom actions created in your Dynamics environment

---

How to Use

When added to a workflow, this node presents a configuration form with the following input fields.

Field	Type	Description	Required	Visible When
ServiceAccount - Microsoft Dynamics 365	Service Account Picker	Select the service account that has permission to execute actions in Dynamics 365.	✅	Always
Action Name	Text	The name of the action to execute. This must match the internal name defined in Dataverse (e.g., WinOpportunity, new_CustomActionName).	✅	Always
Entity Type	Text	The logical name of the entity the action is bound to (e.g., account, opportunity, lead). Leave blank for global actions.	❌	Only for entity-bound actions
Entity Id	Text	The GUID of the record to which the action applies. Required only if the action is entity-bound. Example: 8a5fdb6e-2f87-4b91-b3f5-22b985efb21c	❌	Only for entity-bound actions
Parameters	Key/Value Dictionary	Defines any input parameters that the action requires. These values must match the action’s defined input fields in Dynamics 365. Example: { "Subject": "Follow-up Call", "PriorityCode": 1 }	❌	Optional for all actions

---

Behavior

• If both Entity Type and Entity Id are provided, the node executes an entity-bound action.
• If those fields are left blank, the node executes a global action.
• The node automatically serializes all parameter values into JSON before sending the request.
• The HTTP response is parsed and returned as a structured output variable.

---

Example Configurations

Example 1 – Execute Global Action

Setting	Example Value
ServiceAccount - Microsoft Dynamics 365	DynamicsProdService
Action Name	new_GlobalRefreshAction
Parameters	{ "RefreshType": "Full", "UserId": "admin@tentech.com" }

Result:
Triggers a custom global action called new_GlobalRefreshAction in Dynamics 365 with the provided parameters.

---

Example 2 – Execute Entity-Bound Action

Setting	Example Value
ServiceAccount - Microsoft Dynamics 365	DynamicsProdService
Action Name	WinOpportunity
Entity Type	opportunity
Entity Id	e4c47c0d-49c1-4c73-9a54-0e79ac22c831
Parameters	{ "Status": 3, "ActualRevenue": 150000 }

Result:
Executes the built-in WinOpportunity action for the given Opportunity record and returns the HTTP response and any output values.

---

Outputs

After execution, the node generates the following output variables:

Output Variable	Type	Description
Action Name	Text	The name of the executed Dynamics 365 action.
Response Data	Object	The data returned from the action’s response (parsed from JSON if available).
Status Code	Number	The HTTP status code from the Dataverse API (e.g., 200 = Success).
Entity Type	Text	The entity type (if provided).
Entity Id	Text	The record ID (if provided).

---

Example Workflow Usage

1. Use a D365 Query or Search node to find a record and retrieve its ID.
2. Pass that record ID into the Entity Id input of this node.
3. Set Action Name to a custom or system action name, such as WinOpportunity.
4. Define any required Parameters.
5. Use Response Data in a downstream node to extract returned values or log results.

---

Status Messages

Status	Description
Completed	Action executed successfully and returned a valid response.
Fail	Execution failed (e.g., invalid action name, missing parameters, or permissions error).

---

Error Handling

If the execution fails, the workflow will stop at this node with a Fail status.
Common error causes include:

• Invalid or missing service account
• Invalid action name or entity reference
• Required parameters not supplied
• Permissions issue or Dataverse API error
• Invalid GUID format for entity ID

---

---

Notes

• The Action Name must exactly match the internal logical name of the action in Dynamics 365 (not its display name).
• Parameters must match the data types expected by the action definition.
• You can use workflow variables or outputs from previous nodes inside parameter values (e.g., {LastRecordId}).
• The node uses the Dataverse REST API for action execution and supports both system and custom actions.
• If the response body contains JSON, it will automatically be parsed into structured data.

---

Category: Integrations → Microsoft Dynamics 365 Task Name: D365ExecuteAction