Start free
MActionMicrosoft Dynamics 365Updated June 2026

How do I fetch a Dynamics 365 contact?

Short answer: Drop the "Microsoft Dynamics 365 → Get Dynamics Contact" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this actionAll 9 Microsoft Dynamics 365 actions
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Contact ID
contact_id
stringRequiredGUID of the contact
Sample request
{
  "contact_id": "{{trigger.contact_id}}"
}
Returns
{
  "jobtitle": "VP Marketing",
  "lastname": "Doe",
  "contactid": "00000000-0000-0000-0000-000000000001",
  "firstname": "Jane",
  "telephone1": "+1 415 555 0100",
  "emailaddress1": "jane@example.com"
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Get Dynamics Contact.

Any of these apps can fire this action as part of a workflow.

M
Gmail → Microsoft Dynamics 365
1 Gmail triggers
M
Slack → Microsoft Dynamics 365
13 Slack triggers
M
Google Sheets → Microsoft Dynamics 365
2 Google Sheets triggers
M
HubSpot → Microsoft Dynamics 365
18 HubSpot triggers
FAQ

Questions about Get Dynamics Contact.

What does the Get Dynamics Contact action do in Microsoft Dynamics 365?
Returns a contact by ID with all standard and custom fields plus related account, opportunities, activities. The standard lookup before update or for enrichment workflows.
What inputs does Get Dynamics Contact require?
Required: Contact ID. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Microsoft Dynamics 365 returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Get Dynamics Contact support batch operations?
Yes. Run Get Dynamics Contact inside a Loop node to process arrays. Tiny Command handles Microsoft Dynamics 365's rate limits automatically so you don't have to throttle manually.
More actions

Other Microsoft Dynamics 365 actions.

Action
Create Dynamics Account
Creates a company/account record in Dynamics with name, industry, custom fields. For "new B2B prospect → account record before contact" workflows.
Action
Create Dynamics Contact
Creates a contact tied to an account with email, name, custom fields. For "form submission → push to Dynamics" sync workflows.
Action
Create Dynamics Opportunity
Creates a sales opportunity with estimated value, close date, owner. For "qualified lead → auto-create opportunity in the right pipeline" workflows.
Action
Create Dynamics Task
Creates a follow-up task tied to a contact, account, or opportunity. For "deal stagnant → create follow-up task" or "support ticket needs review → assign as task" patterns.
Action
List Dynamics Opportunities
Paginated opportunities with filters by stage, owner, value, recently updated. For pipeline-reporting workflows that aggregate by stage or owner.
Action
Search Dynamics Contacts
Lookup by name, email, or other field. The standard "find before update" pattern for upsert workflows.

Send get dynamics contact from your workflows.

Triggered by anything in the catalog. Free tier available. No credit card.

Try for freeRequest a demo