Clay, Zapier, Make and n8n
Push leads into GraphKit from Clay or any automation tool with a lead hook, and react to GraphKit events with signed webhooks and the REST API.
GraphKit connects to automation tools in two directions:
| Direction | Use | Where |
|---|---|---|
| Leads into GraphKit | A lead hook: a URL that creates or updates leads, adds them to a list and can enroll them in a campaign | Integrations → Lead hooks |
| Events out of GraphKit | Webhooks: signed POSTs for lead.replied, message.received, invitation.accepted and more | Integrations → Endpoints |
| Actions on GraphKit | The REST API with a workspace API key: add leads to lists, enroll, pause campaigns, send messages | Settings → API keys |
There are no native Zapier, Make or n8n apps yet. Every recipe below uses each tool's built-in webhook and HTTP steps, so it works on every plan that has them.
Lead hooks
Open Integrations → Lead hooks → New hook. Pick a name, an optional list to add leads to, and an optional campaign to enroll them in. GraphKit shows the hook URL and its secret once; copy both.
Viewing hooks needs a role that can import leads. Creating, editing, rotating and deleting them needs a role that can manage API keys (client admin or an agency role), because a hook is a credential.
Send a lead
curl -X POST 'https://app.example.com/hooks/leads/glh_…' \
-H 'Authorization: Bearer glhs_…' \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: row-1' \
-d '{"firstName":"Sam","lastName":"Lee","linkedinUrl":"https://www.linkedin.com/in/sam-lee","companyName":"Northwind","email":"sam@northwind.example"}'{"status":"created","leadId":"0193a5b2-…","results":[{"index":0,"status":"created","leadId":"0193a5b2-…","error":null}],"counts":{"created":1},"campaign":{"added":1,"error":null}}The body is one JSON object, or an array of up to 100 objects (1 MiB at most).
Authentication
Send the hook's secret in one of these ways:
| Method | Header | For |
|---|---|---|
| Bearer | Authorization: Bearer <secret> | Clay, Zapier, Make, n8n and anything with static headers |
| Header | X-GraphKit-Secret: <secret> | Tools that reserve Authorization |
| Signature | GraphKit-Signature: t=<unix seconds>,v1=<hex HMAC-SHA256(secret, "<t>.<raw body>")> | Your own code: the secret never travels |
The signature uses the same scheme as outbound webhooks: GraphKit rejects timestamps more than 5 minutes from its clock and accepts any of several v1= values. Comparisons are constant time. To change a leaked secret, use Rotate secret; New URL and secret also replaces the URL.
Fields
GraphKit recognises common keys in any spelling (first_name, First Name and firstName are the same):
| GraphKit field | Keys recognised |
|---|---|
| LinkedIn identity | linkedinUrl, linkedin, linkedinProfileUrl, profileUrl |
| Instagram, WhatsApp, Telegram, Facebook identity | instagram, whatsapp, telegram, facebook |
| First, last, full name | firstName, lastName, fullName, name |
email, workEmail, emailAddress | |
| Company, domain | company, companyName, organization; companyDomain, domain, website |
| Job title, headline | title, jobTitle, position; headline |
| Phone, location | phone, mobile; location, city |
You can also send identities ([{"channel":"telegram","value":"@sam_lee"}], as in the REST API) and customFields (an object). Any other key with a value becomes a custom field, named in snake case ("Deal size" becomes deal_size). A hook's field mapping overrides this per key, for example Person LinkedIn=linkedinUrl, Score=custom.score or Internal id=ignore.
Every lead needs at least one LinkedIn, Instagram, WhatsApp, Telegram or Facebook identity. An email address alone is stored only with an identity, because GraphKit's channels are social. Items without one are rejected with a message that says so.
What happens to each item
| Status | Meaning |
|---|---|
created | A new lead. lead.created is sent to your webhooks, as for an import. |
updated | An existing lead (matched by identity) got new data. Fields a teammate edited are kept. |
duplicate | Nothing new: the same Idempotency-Key, or the same identities with the same data, was already received. |
suppressed | The lead is on the suppression list. It is saved but never enrolled. |
rejected | The item was not usable (for example no identity). error says why. |
Created and updated leads go to the hook's list. When the hook has a campaign, they are enrolled with the campaign's usual rules (duplicates, suppression and "active in another campaign" are skipped); campaign.error explains a refusal, and the leads stay saved.
The response is 200 when every item was accepted, 207 when some items of an array were rejected, and 422 when a single object was rejected. Other answers: 401 wrong secret or signature, 404 unknown URL, 410 the hook is disabled, 429 too many requests (300 in a burst, then 10 per second per hook; see Retry-After).
Idempotency. With Idempotency-Key, a retry of the same item returns duplicate and the same leadId. In an array, item i uses <key>#<i>. Without a key, GraphKit derives one from the identities and the data, so a re-run of an unchanged row is a duplicate and a changed row is an update. A rejected item does not use up its key, so a corrected retry works.
Each hook keeps an event log of its last 100 items with the payload (truncated at 16 KB), the outcome and the lead.
Clay
Clay's HTTP API enrichment calls any URL row by row with a JSON body built from your columns (Clay docs).
-
In GraphKit, create a lead hook with the list (and campaign) the rows should go to.
-
In your Clay table, add an enrichment column: HTTP API.
-
Method POST, endpoint the hook URL.
-
Headers: add
Authorization=Bearer <secret>. Save it as an HTTP API (Headers) account so the secret is encrypted at the workspace level instead of visible in the column. -
Body: map columns with Clay's
/Columnreferences. String references need quotes:{ "firstName": "/First Name", "lastName": "/Last Name", "linkedinUrl": "/LinkedIn Profile", "companyName": "/Company Name", "email": "/Work Email", "jobTitle": "/Job Title" } -
Turn on Remove empty fields from request so a blank cell never clears a value in GraphKit.
-
Optional: in Field paths to return, add
leadIdandstatusto write them back to the table. -
Add a run condition such as "only run if LinkedIn Profile is not empty", Test on one row, then run the column.
Clay does not compute signatures, which is why hooks accept the secret as a bearer token. Clay's rate limit setting can stay at its default: a hook accepts 300 requests in a burst and 10 per second after that.
Zapier
Use Webhooks by Zapier (help).
Leads into GraphKit. Add an action Webhooks by Zapier → Custom Request: method POST, URL = the hook URL, Data = the JSON object (map fields from earlier steps), Headers: Authorization = Bearer <secret> and Content-Type = application/json. POST also works; build flat keys like firstName and linkedinUrl.
GraphKit events into a Zap. Add the trigger Webhooks by Zapier → Catch Hook and copy its URL. In GraphKit, Integrations → Add endpoint with that URL and the events you want (for example lead.replied), then Send test. Each event arrives with type, data.lead, data.message and data.campaignId (payloads). To verify signatures, use Catch Raw Hook (it includes headers and the raw body) followed by a Code by Zapier step that checks GraphKit-Signature as shown in Verifying signatures.
Act on GraphKit. Call the REST API with Custom Request and Authorization: Bearer gk_live_…, for example POST /api/v1/campaigns/{id}/pause or POST /api/v1/lists/{id}/leads with {"leadIds":["…"]}.
Make
Use the Webhooks and HTTP apps (help).
Leads into GraphKit. Add HTTP → Make a request: URL = the hook URL, method POST, header Authorization: Bearer <secret>, body type Raw, content type JSON (application/json), request content = the lead object with mapped values.
GraphKit events into a scenario. Add Webhooks → Custom webhook, create a webhook and copy its address. Register it in GraphKit as an endpoint, then Send test so Make learns the data structure. Turn on Get request headers if you verify GraphKit-Signature. Make answers 200 Accepted, which GraphKit counts as delivered; Make accepts up to 30 requests per second per webhook.
Act on GraphKit. HTTP → Make a request to /api/v1/… with your API key in Authorization.
n8n
Use the core Webhook and HTTP Request nodes (Webhook, HTTP Request).
Template. Download graphkit-n8n-workflow.json, then in n8n open a new workflow, choose ⋯ → Import from File (or paste the JSON onto the canvas). It has two flows:
- Lead in → Add lead to GraphKit: any form or tool posts a lead to the n8n webhook, and the HTTP Request node sends it to your lead hook. Replace
REPLACE_WITH_LEAD_HOOK_URLandREPLACE_WITH_LEAD_HOOK_SECRET. - GraphKit events → Add replier to list: GraphKit sends
lead.replied, and the HTTP Request node adds the lead to a list withPOST /api/v1/lists/{id}/leads. ReplaceREPLACE_WITH_API_URL,REPLACE_WITH_LIST_IDandREPLACE_WITH_API_KEY(an API key withleads:write), publish the workflow, and register the webhook's production URL in GraphKit with thelead.repliedevent only.
Both HTTP Request nodes send an Idempotency-Key (the execution id, or the GraphKit event id), so a retried execution never adds anything twice. For production, move the secrets into n8n credentials (Authentication → Generic credential type → Header Auth).
Verifying signatures in n8n. On the Webhook node turn on Raw Body. Add a Crypto node: action Hmac, type SHA256, encoding HEX, value {{ $json.headers["graphkit-timestamp"] }}.<raw body>, with the endpoint's whsec_… secret in the Crypto credentials. Compare the result with the v1= part of GraphKit-Signature in an If node.
Other tools
Pabbly Connect, Albato, RB2B, Trigify, Persana, Cargo and similar tools all have a "send HTTP request / webhook" action: point it at a lead hook with the bearer header. To receive GraphKit events, give GraphKit the tool's catch-webhook URL as an endpoint.
Security notes
- Hook URLs and secrets are random 192-bit values. GraphKit stores only a SHA-256 hash of the URL token and keeps the secret encrypted (AES-256-GCM).
- Treat the URL and the secret like an API key. Anyone with both can add leads to the workspace (never read them).
- Disable a hook to stop it at once (
410 Gone); delete it to remove it. - Every create, change, rotation and deletion is written to the workspace audit log.
CRM integrations
Sync leads, conversations and positive replies to HubSpot, Pipedrive or Salesforce, and feed GraphKit lists from HubSpot lists.
Unified inbox
Read and answer every conversation of every connected account in one inbox, with filters, assignment, labels, notes, saved replies, snooze, scheduled send, AI drafts, exports, a command menu, privacy and opt-outs.