Start free
ActionGreenhouseUpdated June 2026

How do I advance a Greenhouse application?

Short answer: You can move application to stage in Greenhouse by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Greenhouse Move Application to Stage action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Move Application to Stage in Greenhouse — start free All 4 Greenhouse actions
Move Application to Stage 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.

FieldTypeRequiredDescription
Application ID
application_id
stringRequired–
Target Stage ID
to_stage_id
stringRequired–
On Behalf Of
on_behalf_of
stringRequired–
Sample request
{
  "application_id": "{{trigger.application_id}}",
  "to_stage_id": "{{trigger.to_stage_id}}",
  "on_behalf_of": "{{trigger.on_behalf_of}}"
}
Returns
{
  "id": 999,
  "current_stage": {
    "id": 5,
    "name": "Onsite"
  }
}

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

Triggered by

Apps that pair well as the trigger for Move Application to Stage.

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

Gmail → Greenhouse
1 Gmail triggers
Slack → Greenhouse
13 Slack triggers
Google Sheets → Greenhouse
2 Google Sheets triggers
HubSpot → Greenhouse
18 HubSpot triggers
FAQ

Questions about Move Application to Stage.

What does the Move Application to Stage action do in Greenhouse?
Transitions an application to a new pipeline stage. For "scorecard passed → auto-advance to next stage" workflows or for "bulk-reject after deadline" maintenance.
What inputs does Move Application to Stage require?
Required: Application ID, Target Stage ID, On Behalf Of. Every input accepts a static value or a variable from any upstream node in your workflow.
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 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 Move Application to Stage support batch operations?
Yes. Run Move Application to Stage inside a Loop node to process arrays. TinyCommand handles Greenhouse's rate limits automatically so you don't have to throttle manually.
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 Candidates
Paginated candidates with filters by source, status, recently active. For "yesterday's advancements" daily hiring-manager digests.
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.
Move Application to Stage in Greenhouse — start free