Send contacts to your CRM (Zapier, Make, webhooks)

With Pro, Linq can send every new contact straight to your CRM or automation tool. Each one goes out as soon as someone shares their details from your card, or as soon as you add or scan someone yourself.

Linq sends contacts with webhooks, which most tools accept: a Catch Hook trigger in Zapier, a custom webhook in Make, a HubSpot workflow that starts from a webhook, or your own server.

Connect a tool

1. In your tool, create a webhook trigger and copy its URL. It starts with https://, for example https://hooks.zapier.com/hooks/catch/….
2. In Linq, open Settings → Integrations.
3. Paste the URL under Add a webhook and select Add webhook.
4. Select Send test. Your tool receives a sample contact, and the result shows under Last delivery a few seconds later.

From then on, new contacts are sent automatically. Use the Send new contacts switch to pause a webhook without deleting it.

You can add up to 5 webhooks, for example one for your CRM and one for a spreadsheet. The URL must be a public https address; local and private network addresses can’t receive webhooks.

What’s sent

Each contact is a JSON POST with these fields. Empty ones are null.

Field	What it holds
event	Always contact.created.
test	true for Send test, false for real contacts.
id	The contact’s ID, to recognize repeats.
name, email, phone	How to reach them.
company, title, website	Their company, job title and website or LinkedIn.
metAt, tags	Where you met and your tags, when you’ve added them.
source	How they arrived: shared from your card, added by you, or scanned.
cardName	Which of your cards the contact is on.
createdAt	When the contact was added (ISO 8601).

Context you add later, such as tags or a follow-up, isn’t sent again: webhooks send each contact once, when they’re added.

If a delivery fails

Last delivery shows whether your tool accepted the contact, or why it didn’t: your tool answered with an error, the URL redirects (use the final URL), the server didn’t answer within 10 seconds, or its security certificate isn’t valid.

If your tool doesn’t answer, Linq tries again 3 times over about half an hour (after 1, 5 and 30 minutes).

On the Free plan

Adding a webhook needs Pro. If you go back to Free, your webhooks are kept but paused, and nothing is sent until you upgrade again. You can still turn webhooks off or delete them.

Verify requests (for developers)

Each request is signed with the webhook’s signing secret (select Copy next to it in Integrations) and carries these headers:

Header	Value
X-Linq-Event	contact.created
X-Linq-Delivery	An ID that stays the same when a delivery is retried, so you can skip repeats.
X-Linq-Timestamp	Unix time in seconds.
X-Linq-Signature	sha256= followed by the hex HMAC-SHA256 of <timestamp>.<raw body>, using the signing secret.

To verify a request, compute the HMAC-SHA256 of the timestamp, a dot and the raw body with your secret, and compare it with the signature.