ActionGreenhouseUpdated September 2026

How do I add a candidate to Greenhouse?

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

Create Greenhouse Candidate in Greenhouse — start free All 4 Greenhouse actions

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

Triggered by

Apps that pair well as the trigger for Create Greenhouse Candidate.

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 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 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 Create Greenhouse Candidate support batch operations?

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

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.

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.

Create Greenhouse Candidate in Greenhouse — start free