Skip to content
Recued
Menu
← Back to recipes

Create a Greenhouse candidate intake

by recued-core v1

Approval-gated Greenhouse candidate creation. It optionally reads target jobs for context, then creates one candidate profile through recued-core.greenhouse.candidate.create with explicit name, contact, tags, and optional nested application payload. It does not update existing candidates, merge, anonymize, delete, move applications, hire/reject applicants, create offers, upload attachments, or call arbitrary Greenhouse endpoints.

How it works 8 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (8 steps)
first_name trim
Trim whitespace from setting first name
last_name trim
Trim whitespace from setting last name
context_jobs ?
has_first_name compare
Check if first name has data
has_last_name compare
Check if last name has data
ready all
Check if all conditions are true
create_candidate ?
skip: step.ready not_equal true
card to_summary
Format results as a summary card
Settings 10 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

tags setting =
title setting =
company setting =
last name setting =
first name setting =
greenhouse setting =
application setting = [object Object]
phone numbers setting =
context job ids setting =
email addresses setting =

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Where it runs

Device + server Runs on your device (browser) or your server.

Permissions it requires

Read your Greenhouse connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

About

Tags

greenhouse greenhousecandidateintakerecruitingapprovalpack:greenhouse

Details

8 steps 10 configurable settings recipe_id: create-greenhouse-candidate-intake