Get Record

dynamics_crm.get_record
ActionCRM & salesconnection required

Calls the Microsoft Dynamics 365 API with the connection's credentials.

Retrieve one row by its id and return it, so a later step can read its columns directly.

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

5 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
entity_set
The entity set to work with: 'accounts', 'contacts', 'opportunities', 'leads', 'incidents' (cases), 'tasks', or any other table's entity set name, including custom tables. It is the plural name from the table's 'Copy set name' in Power Apps, which is not always the plural of the table name.
stringYes——accounts
record_id
The row's primary key GUID, or an alternate-key predicate such as firstname='Joe',emailaddress1='joe@contoso.com'.
stringYes——00000000-0000-0000-0000-000000000001
select
Comma-separated column names to return ($select). Always name the columns you need: without it Dataverse returns every column on the row.
stringNo——name,revenue,createdon
expand
Related rows to return inline ($expand), naming navigation properties, for example primarycontactid($select=fullname).
stringNo———
include_formatted_values
Also return the display text of choice, lookup and money columns alongside their raw values, as @OData.Community.Display.V1.FormattedValue annotations.
booleanNofalse——

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "entity_set": "accounts",
  "include_formatted_values": false,
  "record_id": "00000000-0000-0000-0000-000000000001",
  "select": "name,revenue,createdon"
}

Output

One shape.

result

The provider's response object, as returned.

Extra keys beyond the ones listed can appear.

{}

Notes

  • The output is the row itself, so a downstream step reads $json.name rather than $json.record.name.

See Get Record 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.