Short answer: Drop the "Ashby → Create Candidate" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Full Name name | string | Required | — |
Email email | string | Optional | The email address. Used as the recipient or identifier depending on context. |
Phone phone_number | string | Optional | Phone number in E.164 format (with country code, no spaces). |
LinkedIn URL linkedin_url | string | Optional | A fully qualified URL (https://...) for the linkedin url. |
Credit-to User ID credit_to_user_id | string | Optional | — |
{"name": "{{trigger.name}}","email": "e.g. user@example.com","phone_number": "e.g. +14155551234","linkedin_url": "e.g. https://example.com/path","credit_to_user_id": "{{trigger.credit_to_user_id}}"}
{"results": {"id": "cand_abc","name": "Jane Doe"}}
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.
Triggered by anything in the catalog. Free tier available. No credit card.