Move Application to Stage: Greenhouse action

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
Application ID application_id	string	Required	—
Target Stage ID to_stage_id	string	Required	—
On Behalf Of on_behalf_of	string	Required	—

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.

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. Tiny Command handles Greenhouse's rate limits automatically so you don't have to throttle manually.

More actions