Create Greenhouse Candidate: 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
First Name first_name	string	Required	Contact's first (given) name.
Last Name last_name	string	Required	Contact's last (family) name.
Email email	string	Required	The email address. Used as the recipient or identifier depending on context.
Phone phone	string	Optional	Phone number in E.164 format (with country code, no spaces).
Current Company company	string	Optional	—
Current Title title	string	Optional	—
Applications applications	array	Optional	Array of {job_id: number}
On Behalf Of (user id) on_behalf_of	string	Required	—

Sample request

{
  "first_name": "e.g. Jane",
  "last_name": "e.g. Doe",
  "email": "e.g. user@example.com",
  "phone": "e.g. +14155551234",
  "company": "{{trigger.company}}"
}

Returns

{
  "id": 12345,
  "last_name": "Doe",
  "first_name": "Jane",
  "applications": [
    {
      "id": 999
    }
  ]
}

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

FAQ

Questions about Create Greenhouse Candidate.

What does the Create Greenhouse Candidate action do in Greenhouse?

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.

What inputs does Create Greenhouse Candidate require?

Required: First Name, Last Name, Email, On Behalf Of (user id). 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 Create Greenhouse Candidate support batch operations?

Yes. Run Create Greenhouse Candidate 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