Short answer: Drop the "Workable → 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 |
|---|---|---|---|
Limit limit | number | Optional | Limit |
Stage Filter stage | string | Optional | Stage Filter |
{"limit": "{{trigger.limit}}","stage": "{{trigger.stage}}"}
{"paging": {"next": null},"candidates": [{"id": "cand_123","name": "Jane Smith","email": "jane@example.com","headline": "Senior Dev"}]}
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.