List Dynamics Opportunities: 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
Status state_code	select	Optional	Filter by opportunity state
Limit top	number	Optional	Max records to return

Sample request

{
  "state_code": "{{trigger.state_code}}",
  "top": "{{trigger.top}}"
}

Returns

{
  "value": [
    {
      "name": "Acme Q2 expansion",
      "statecode": 0,
      "opportunityid": "22222222-2222-2222-2222-222222222222",
      "estimatedvalue": 50000
    }
  ]
}

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

FAQ

Questions about List Dynamics Opportunities.

What does the List Dynamics Opportunities action do in Microsoft Dynamics 365?

Paginated opportunities with filters by stage, owner, value, recently updated. For pipeline-reporting workflows that aggregate by stage or owner.

What inputs does List Dynamics Opportunities require?

List Dynamics Opportunities 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 List Dynamics Opportunities support batch operations?

Yes. Run List Dynamics Opportunities 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