AActionAshbyUpdated May 2026

What jobs are open in Ashby?

Short answer: Drop the "Ashby → List Jobs" 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
Status filter (Open/Closed) status	string	Optional	—

Sample request

{
  "status": "{{trigger.status}}"
}

Returns

{
  "results": [
    {
      "id": "job_abc",
      "team": {
        "name": "R&D"
      },
      "title": "Engineer",
      "status": "Open"
    }
  ]
}

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

Triggered by

Apps that pair well as the trigger for List Jobs.

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 Jobs.

What does the List Jobs action do in Ashby?

Returns open requisitions with team, location, status. Useful for "auto-post our open roles to the company careers page" sync workflows and for routing inbound applications to the right job.

What inputs does List Jobs require?

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

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