AActionAshbyUpdated May 2026

How do I add a candidate to Ashby?

Short answer: Drop the "Ashby → Create Candidate" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 3 Ashby actions

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
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	—

Sample request

{
  "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}}"
}

Returns

{
  "results": {
    "id": "cand_abc",
    "name": "Jane Doe"
  }
}

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

Triggered by

Apps that pair well as the trigger for Create Candidate.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Ashby

2 Google Sheets triggers

HubSpot → Ashby

18 HubSpot triggers

FAQ

Questions about Create Candidate.

What does the Create Candidate action do in Ashby?

Creates a new candidate with name, email, optional initial application against a job, and source attribution. The standard hook for "sourced via LinkedIn or Sales Navigator → push to Ashby with the right source for sourcing-analytics rollup".

What inputs does Create Candidate require?

Required: Full Name. 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 Ashby 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 Candidate support batch operations?

Yes. Run Create Candidate inside a Loop node to process arrays. Tiny Command handles Ashby's rate limits automatically so you don't have to throttle manually.

More actions