ActionGreenhouseUpdated September 2026

How do I list Greenhouse candidates?

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

List Greenhouse Candidates in Greenhouse — start free All 4 Greenhouse actions

List Greenhouse Candidates in Greenhouse — 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
Per Page per_page	string	Optional	–
Updated After (ISO) updated_after	string	Optional	–

Sample request

{
  "per_page": "{{trigger.per_page}}",
  "updated_after": "{{trigger.updated_after}}"
}

Returns

[
  {
    "id": 12345,
    "last_name": "Doe",
    "first_name": "Jane",
    "applications": [
      {
        "status": "active",
        "current_stage": {
          "name": "Phone Screen"
        }
      }
    ]
  }
]

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

Triggered by

Apps that pair well as the trigger for List Greenhouse Candidates.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Greenhouse

2 Google Sheets triggers

HubSpot → Greenhouse

18 HubSpot triggers

FAQ

Questions about List Greenhouse Candidates.

What does the List Greenhouse Candidates action do in Greenhouse?

Paginated candidates with filters by source, status, recently active. For "yesterday's advancements" daily hiring-manager digests.

What inputs does List Greenhouse Candidates require?

List Greenhouse Candidates 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 Greenhouse returns an error?

The run history shows the failed step with its input and the error message Greenhouse 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 Greenhouse Candidates support batch operations?

Run List Greenhouse Candidates 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 Greenhouse's rate limits.

More actions

Other Greenhouse actions.

Action

Create Greenhouse Candidate

Pushes a sourced candidate with email, name, optional initial application against a job, source attribution. For "LinkedIn Sales Navigator → push prospect to Greenhouse for the recruiter" sourcing workflows.

Action

List Greenhouse Jobs

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

Action

Move Application to Stage

Transitions an application to a new pipeline stage. For "scorecard passed → auto-advance to next stage" workflows or for "bulk-reject after deadline" maintenance.

List Greenhouse Candidates in Greenhouse — start free