MActionMicrosoft Dynamics 365Updated June 2026

How do I search Dynamics 365 contacts?

Short answer: You can search dynamics contacts in Microsoft Dynamics 365 by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Microsoft Dynamics 365 Search Dynamics Contacts action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Search Dynamics Contacts in Microsoft Dynamics 365 — start free
Inputs

The fields this action accepts.

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

FieldTypeRequiredDescription
Email
email
stringOptionalFilter by primary email (exact match)
Last Name
last_name
stringOptionalFilter by last name (exact match)
Limit
top
numberOptionalMax records to return
Sample request
{
"email": "{{trigger.email}}",
"last_name": "{{trigger.last_name}}",
"top": "{{trigger.top}}"
}
Returns
{
"value": [
{
"lastname": "Doe",
"contactid": "00000000-0000-0000-0000-000000000001",
"firstname": "Jane",
"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 Search Dynamics Contacts.

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

FAQ

Questions about Search Dynamics Contacts.

What does the Search Dynamics Contacts action do in Microsoft Dynamics 365?
Lookup by name, email, or other field. The standard "find before update" pattern for upsert workflows.
What inputs does Search Dynamics Contacts require?
Search Dynamics Contacts has no required inputs. Sensible defaults are applied if you leave fields blank.
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 Search Dynamics Contacts support batch operations?
Yes. Run Search Dynamics Contacts inside a Loop node to process arrays. TinyCommand 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
Get Dynamics Contact
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.
Action
List Dynamics Opportunities
Paginated opportunities with filters by stage, owner, value, recently updated. For pipeline-reporting workflows that aggregate by stage or owner.
Search Dynamics Contacts in Microsoft Dynamics 365 — start free