Curviate x Make

Build Make scenarios around LinkedIn replies and invites. 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 Make?

Make is a visual automation platform where users build workflows, called scenarios, that connect apps and services. Operations, marketing and sales teams use it to automate tasks without much code.

Visit make.com

How Make works with Curviate

A Make scenario starts with the Webhooks app’s Custom webhook module, and Curviate posts LinkedIn events to its URL. The HTTP app’s Make a request module calls Curviate back. Make learns the event’s fields from the first delivery, so send a test event before you map anything.

Events outmessage.receivedconnection.acceptedenrollment.finished

Actions inadd contactsstart a Motionsend a message

What you can build

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

Every reply in Google Sheets

Each LinkedIn reply adds a row with the sender, the Account, the Motion and the time.

message.received

Accepted invites become Pipedrive deals

When someone accepts your invitation, the scenario creates the person and an open deal in Pipedrive.

connection.accepted

Outcomes on the HubSpot contact

When an Enrollment finishes, its finish reason is written to a property on the matching HubSpot contact.

enrollment.finished

Set up Make 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
Start with the Webhooks › Custom webhook module
Create a new flow in Make, start it with the Webhooks › Custom webhook module and copy the URL it gives you.
# the URL your Webhooks › Custom webhook module gives you
https://your-make-webhook-url
3
Send Curviate events to it
Create a webhook in Curviate for the events you need, then send a test event so Make can read the fields. You can do the same in the dashboard under Settings, then API & Webhooks. 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://your-make-webhook-url"
  }'
4
Call Curviate from Make
Add the HTTP › Make a request module with the headers Authorization: Bearer plus your key and Content-Type: application/json, and call any Curviate action. This one adds a person and starts a 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_…"] }
5
Check the signature
Every delivery carries a Curviate-Signature header: an HMAC-SHA256 of the timestamp and the raw body, made with your webhook’s secret. Compare it before you act, and drop anything older than five minutes.
Curviate-Signature: t=1792230000,v1=5f2c9a…e81b

# expected = HMAC_SHA256(secret, t + "." + raw_body)

Make details that matter

What Make’s webhook docs and Curviate’s delivery rules mean together.

1
Let Make learn the fields
Run the scenario once so the Custom webhook listens, then send curviate webhook test. Make determines the data structure from that delivery, a made-up Contact at example.com, and every later module can map its fields.
2
Keep the queue from filling
Each Make webhook has its own queue: 667 items per 10,000 credits a month, at most 10,000. A full queue answers 400, which Curviate doesn’t retry, so events that arrive once it is full are lost unless you redeliver them within 24 hours.
curviate webhook deliveries whk_… --failed
curviate webhook redeliver whk_… wdl_…
3
Idle webhooks answer 410
A Make webhook that no scenario uses for 5 days is deactivated and answers 410 Gone. Curviate doesn’t retry a 4xx, and switches a webhook off after 72 hours of failures, with one email to its creator.
4
Mind the rate
Make accepts up to 300 webhook requests per 10 seconds and answers 429 above that. Curviate retries a 429 on its schedule and honours Retry-After, so a burst slows down rather than drops.

Events you can use

message.receivedA LinkedIn message or InMail arrived

connection.acceptedSomeone accepted an invitation you sent through Curviate

enrollment.finishedA contact finished a Motion, with the reason

enrollment.repliedA contact replied to a Motion, with the reply text

motion.custom_eventA Motion ran a step you marked to notify you

post.publishedA scheduled post went live

account.reconnect_neededAn account needs to sign in again

All webhook events

Actions you can call

POST /v1/contactsAdd or update a contact

POST /v1/motions/{id}/contactsStart a Motion for contacts

POST /v1/{account_id}/chats/{chat_id}/messagesSend a message

POST /v1/enrollments/{id}/eventsTell a waiting Motion to continue

GET /v1/{account_id}/companies/{identifier}Read a company page

API reference

Questions about Curviate x Make

Which LinkedIn events can start a Make flow?

Messages, accepted invitations, published posts, account status changes and every step of a Motion, from a contact starting it to a reply that ends it.

Can Make act on LinkedIn too?

Yes. Every Curviate action is a plain HTTPS call, so Make can search, message, invite or start a Motion, inside the limits you set for each account.

Do I need to write code?

No. A webhook trigger and an HTTP request are all it takes, and Make maps the fields for you.

Is there a Curviate app in Make?

No. The Webhooks and HTTP apps that ship with Make are all it takes: one listens for Curviate’s events, the other calls Curviate’s REST API with your key.