Short answer: Drop the "Ashby → List Candidates" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 | — |
{"cursor": "{{trigger.cursor}}","limit": "{{trigger.limit}}"}
{"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.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.