AActionAshbyUpdated May 2026

How do I list Ashby candidates?

Short answer: Drop the "Ashby → List Candidates" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 3 Ashby actions

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
Cursor (paginate) cursor	string	Optional	—
Limit limit	string	Optional	—

Sample request

{
  "cursor": "{{trigger.cursor}}",
  "limit": "{{trigger.limit}}"
}

Returns

{
  "results": [
    {
      "id": "abc",
      "name": "Jane Doe",
      "primaryEmailAddress": {
        "value": "jane@x.com",
        "isPrimary": true
      }
    }
  ],
  "moreDataAvailable": false
}

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

Triggered by

Apps that pair well as the trigger for List Candidates.

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

Google Sheets → Ashby

2 Google Sheets triggers

HubSpot → Ashby

18 HubSpot triggers

FAQ

Questions about List Candidates.

What does the List Candidates action do in Ashby?

Paginated candidate retrieval with filters by source, stage, recently active, posting. Useful for "this morning, who advanced to onsite yesterday" digest workflows for hiring managers.

What inputs does List Candidates require?

List Candidates 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 Ashby 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 Candidates support batch operations?

Yes. Run List Candidates inside a Loop node to process arrays. Tiny Command handles Ashby's rate limits automatically so you don't have to throttle manually.

More actions