Read and write Dataverse table rows and Dynamics 365 accounts through a named environment and application user.
Explore 11 workflow actions for Microsoft Dataverse and Dynamics 365, including account permissions and operation limits.
4 read actions7 write actions
WORKFLOW ACTIONS
What you can configure.
Choose an action in the workflow builder, connect an account, and map its inputs. These actions are available in the catalog; your account access and a successful test determine whether they work for your setup.
Create Dynamics 365 account
Write
Create a Dynamics 365 account with a name and writable scalar columns.
Permissions and limits
Account permissions
Dataverse account create privilege
Operation limits
The Dataverse application user must have privileges on the selected table.
Writes are sent once. If the provider response is lost, NodeHub does not retry automatically.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Create or update row
Write
Create or update row
Permissions and limits
Account permissions
Dataverse table write privilege
Operation limits
Upsert targets an explicit row GUID. It does not resolve alternate keys or report whether Dataverse created or updated the row.
The Dataverse application user must have privileges on the selected table.
Writes are sent once. If the provider response is lost, NodeHub does not retry automatically.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Create row
Write
Create a Dataverse row with writable scalar columns.
Permissions and limits
Account permissions
Dataverse table create privilege
Operation limits
The Dataverse application user must have privileges on the selected table.
Writes are sent once. If the provider response is lost, NodeHub does not retry automatically.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Delete Dynamics 365 account
Write
Delete one Dynamics 365 account by its account ID.
Permissions and limits
Account permissions
Dataverse account delete privilege
Operation limits
The Dataverse application user must have privileges on the selected table.
Writes are sent once. If the provider response is lost, NodeHub does not retry automatically.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Delete row
Write
Delete row
Permissions and limits
Account permissions
Dataverse table write privilege
Operation limits
The Dataverse application user must have privileges on the selected table.
Writes are sent once. If the provider response is lost, NodeHub does not retry automatically.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Get Dynamics 365 account
Read
Get one Dynamics 365 account by its account ID.
Permissions and limits
Account permissions
Dataverse account read privilege
Get row
Read
Get one Dataverse row by entity set name and GUID.
Permissions and limits
Account permissions
Dataverse table read privilege
List Dynamics 365 accounts
Read
Read one bounded page of Dynamics 365 accounts.
Permissions and limits
Account permissions
Dataverse account read privilege
Operation limits
Returns one page of at most 100 accounts. Follow-up pages are not fetched automatically.
List rows
Read
Read one bounded page of Dataverse rows.
Permissions and limits
Account permissions
Dataverse table read privilege
Operation limits
Returns one page of at most 100 rows. Follow-up pages are not fetched automatically.
Update Dynamics 365 account
Write
Update writable scalar columns on an existing Dynamics 365 account.
Permissions and limits
Account permissions
Dataverse account write privilege
Operation limits
The Dataverse application user must have privileges on the selected table.
Writes are sent once. If the provider response is lost, NodeHub does not retry automatically.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Update row
Write
Update row
Permissions and limits
Account permissions
Dataverse table write privilege
Operation limits
The Dataverse application user must have privileges on the selected table.
Writes are sent once. If the provider response is lost, NodeHub does not retry automatically.
A repeated request may repeat the external action. Review the previous result before retrying a write.
SETUP
Start with a controlled test.
01Connect the intended account
Use the account and permissions required for your process. Review the connection check before configuring a workflow action.
02Review inputs and access
Select a listed operation and map its required inputs. Use test records and add a human approval before writes that need review.
03Confirm the result
Inspect step outputs and confirm the result in Microsoft Dataverse and Dynamics 365. A saved workflow is not a completed provider action.
Data & Docs · CONNECTION
