AActionAshbyUpdated September 2026

What jobs are open in Ashby?

Short answer: You can list jobs in Ashby by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Ashby List Jobs action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List Jobs in Ashby — start free All 3 Ashby actions

List Jobs in Ashby — start free

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 run history shows the failed step with its input and the error message Ashby returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does List Jobs support batch operations?

Run List Jobs inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Ashby's rate limits.

More actions

Other Ashby actions.

Action

Create Candidate

Creates a new candidate with name, email, optional initial application against a job, and source attribution. The standard hook for "sourced via LinkedIn or Sales Navigator → push to Ashby with the right source for sourcing-analytics rollup".

Action

List Candidates

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.

List Jobs in Ashby — start free