Search Dynamics Contacts: Microsoft Dynamics 365 action

Inputs

The fields this action accepts.

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

Field	Type	Required	Description
Email email	string	Optional	Filter by primary email (exact match)
Last Name last_name	string	Optional	Filter by last name (exact match)
Limit top	number	Optional	Max 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.

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. Tiny Command handles Microsoft Dynamics 365's rate limits automatically so you don't have to throttle manually.

More actions