Short answer: Drop the "Ashby → List Jobs" 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 |
|---|---|---|---|
Status filter (Open/Closed) status | string | Optional | — |
{"status": "{{trigger.status}}"}
{"results": [{"id": "job_abc","team": {"name": "R&D"},"title": "Engineer","status": "Open"}]}
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.