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.
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 | – |
{"first_name": "e.g. Jane","last_name": "e.g. Doe","email": "e.g. user@example.com","phone": "e.g. +14155551234","company": "{{trigger.company}}"}
{"id": 12345,"last_name": "Doe","first_name": "Jane","applications": [{"id": 999}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.