Microsoft Dataverse Tools

Microsoft Dataverse stores and manages business data used by Dynamics 365 and Power Platform apps. Use these tools in a workflow to query, create, and retrieve records from Dataverse tables through the OData Web API, authenticating with an OAuth bearer access token and your Dataverse environment URL.

Overview

Operations

All operations call the Dataverse Web API at {{orgUrl}}/api/data/v9.2/... using OData v4 headers.

Configuration

microsoft_dataverse_query_records

Query records from a table, optionally narrowing results with an OData $filter and limiting the result count with $top.

microsoft_dataverse_create_record

Create a new record in a table. The response uses Prefer: return=representation, so the created record is returned in full.

microsoft_dataverse_get_record

Retrieve a single record by its GUID.

Outputs

microsoft_dataverse_query_records

• data (json) — Array of Dataverse records matching the query (the OData value array).
• metadata (json) — Query metadata, containing:
  • entitySetName (string) — The queried entity set name.
  • count (number) — Number of records returned.

microsoft_dataverse_create_record

• data (json) — The created Dataverse record.
• metadata (json) — Record identifiers, containing:
  • entitySetName (string) — The entity set name.
  • recordId (string) — The created record ID (extracted from the response body or the OData-EntityId header).

microsoft_dataverse_get_record

• data (json) — The Dataverse record.
• metadata (json) — Record identifiers, containing:
  • entitySetName (string) — The entity set name.
  • recordId (string) — The record ID.

YAML Example

microsoft_dataverse_1:
  type: microsoft_dataverse
  name: "Microsoft Dataverse"
  inputs:
    operation: "microsoft_dataverse_query_records"
    orgUrl: "https://myorg.crm.dynamics.com"
    entitySetName: "accounts"
    filter: "statecode eq 0"
    top: 10
    accessToken: "{{MICROSOFT_DATAVERSE_ACCESS_TOKEN}}"
  connections:
    outgoing:
      - target: next-block-id

To create a record instead, switch the operation and supply fields:

microsoft_dataverse_create:
  type: microsoft_dataverse
  name: "Create Account"
  inputs:
    operation: "microsoft_dataverse_create_record"
    orgUrl: "https://myorg.crm.dynamics.com"
    entitySetName: "accounts"
    fields:
      name: "Contoso Ltd"
    accessToken: "{{MICROSOFT_DATAVERSE_ACCESS_TOKEN}}"
  connections:
    outgoing:
      - target: next-block-id

Tips

• Auth setup: accessToken is a Microsoft Entra ID (Azure AD) OAuth bearer token scoped to your Dataverse environment (https://myorg.crm.dynamics.com/.default). Store it as a secret (e.g., {{MICROSOFT_DATAVERSE_ACCESS_TOKEN}}) rather than hard-coding it — tokens are short-lived and must be refreshed.
• Use the plural entity set name, not the table logical name: entitySetName must be the OData plural collection name (e.g., accounts, contacts, opportunities), not the singular logical name (account).
• Reference outputs downstream with double braces, e.g. {{microsoft_dataverse_1.data}} for the records array or {{microsoft_dataverse_create.metadata.recordId}} for a newly created record's GUID.
• Filtering: filter uses raw OData $filter syntax (e.g., statecode eq 0 and revenue gt 100000). If omitted, all records up to top are returned (default top is 10).