CurviatexAshby

Send candidate replies from LinkedIn to Ashby. Connect the two with Curviate’s webhooks and API, then build the flow you need.

Start for free See the setup

No card required

What is Ashby?

Ashby is a recruiting platform that combines an applicant tracking system, sourcing, scheduling and analytics. In-house talent teams, often at startups and tech companies, use it.

Visit ashbyhq.com

How Ashby works with Curviate

Curviate keeps Ashby in step with your LinkedIn sourcing: candidate replies land on the candidate, accepted invitations become prospects and Motion outcomes move stages. Connect the two through n8n, Make or Zapier, or with your own code.

Events outmessage.receivedconnection.acceptedenrollment.finished

Actions inadd contactsstart a Motion

What you can build

Three flows teams set up first. Each one takes a few minutes.

Replies on the candidate

Each LinkedIn reply is added to the matching candidate in Ashby, so the hiring team sees it.

message.received

Accepted invites become prospects

When a candidate accepts your invitation, they are added to Ashby as a prospect for the right role.

connection.accepted

Outcomes move the stage

When a candidate finishes a Motion with a reply, Ashby moves them to the next stage.

enrollment.finished

Set up Ashby with Curviate

Everything runs on two things Curviate gives every account: signed webhooks out and a REST API in.

1
Copy your Curviate API key
In the Curviate dashboard, open Settings, then API & Webhooks, and copy your key.
# keep it in your tool's credentials, never in plain text
CURVIATE_API_KEY=cvt_live_••••3f9a
2
Connect Ashby to your automation
Sign in to Ashby inside n8n, Make or Zapier, or create an API key in Ashby if you write your own code.
3
Send Curviate events to it
Point a Curviate webhook at an n8n, Make or Zapier webhook trigger, or at your own endpoint. Each webhook covers one source: messaging for replies, user for accepted invitations, motion for Motion outcomes, account_status for account alerts.
curl https://api.curviate.com/v1/webhooks \
  -H "Authorization: Bearer $CURVIATE_API_KEY" \
  -d '{
    "source": "messaging",
    "events": ["message.received"],
    "account_ids": ["acc_…"],
    "request_url": "https://hooks.zapier.com/hooks/catch/…"
  }'
4
Write to Ashby
Add the Ashby step your tool offers, such as creating or updating a candidate, and map the fields from the Curviate event.
# what your tool receives
{ "event": "connection.accepted",
"data": { "account_id": "acc_…", "occurred_at": "2026-10-17T09:12:00Z", … } }
5
Send Ashby candidates into a Motion
Trigger on a change in Ashby, then add each person to Curviate and start your Motion.
# add the person as a contact
POST https://api.curviate.com/v1/contacts
{ "linkedin_url": "linkedin.com/in/lenaweber", "first_name": "Lena" }

# start your Motion for them
POST https://api.curviate.com/v1/motions/mot_…/contacts
{ "contact_ids": ["con_…"] }