Send new contacts to your CRM, a spreadsheet or Slack with Zapier or Make

When someone taps your card and shares their details, they land in your contact book in NoBrandCards. If you live in a CRM, a spreadsheet or a shared inbox, you probably want them there too, without copying anything by hand.

That's what webhooks are for. A webhook is a web address that NoBrandCards calls the moment something happens, such as a new contact, with all the details. Zapier and Make can give you that address, and then pass each contact on to almost any app.

This guide covers both. Pick the one you already use.

What you need

• NoBrandCards Pro (or Teams). Webhooks are part of Pro. In a team, the owner or an admin sets them up.
• A Zapier or Make account. Zapier's "Webhooks by Zapier" app needs a paid Zapier plan. Make's webhooks work on its free plan.
• About ten minutes.

With Zapier

1. Get an address from Zapier

1. In Zapier, click Create, then Zaps.
2. For the trigger, choose Webhooks by Zapier, and for the event, Catch Hook. Click Continue (you can leave "Pick off a child key" empty).
3. Zapier shows a webhook URL that starts with https://hooks.zapier.com/. Copy it.

2. Add the webhook in NoBrandCards

1. In the NoBrandCards app, go to Settings › API and webhooks.
2. Under Webhooks, click Add a webhook.
3. Paste Zapier's address into Address.
4. Under Events to send, keep New contact. Tick Contact changed too if you also want status and tag changes (most people don't).
5. Click Add webhook.

NoBrandCards then shows a signing secret once. Zapier doesn't use it, but keep it somewhere safe in case you ever switch to your own server (see the end of this guide).

3. Show Zapier a real contact

Zapier learns the fields from the first delivery it sees, so give it a real one:

1. In NoBrandCards, go to Contacts and click Add contact. Add a test person with a name, an email and a company. (Or share your details on your own card from your phone.)
2. Back in Zapier, click Test trigger. You'll see the delivery, with the contact's details under Data › Contact.

You can also use Send a test in the webhook's menu in NoBrandCards. It sends a short test message (its type is ping) to check the connection, but it has no contact fields to map.

4. Send the contact where you want it

Click + to add an action. For example:

• HubSpot, Create or Update Contact
• Salesforce, Create Record (Lead)
• Google Sheets, Create Spreadsheet Row
• Mailchimp, Add/Update Subscriber
• Slack, Send Channel Message ("New lead from my card: …")

Map the fields: Zapier lists them as Data Contact Name, Data Contact Email, Data Contact Phone, Data Contact Company and so on. (The full list is below.)

If you ticked more than one event, add a Filter step before the action: continue only if Type exactly matches contact.created. That also keeps test messages out.

5. Turn it on

Click Publish. From now on, each new contact reaches your app within a few seconds of being shared.

With Make

1. Get an address from Make

1. In Make, click Create a new scenario.
2. Click the big +, search for Webhooks, and choose Custom webhook.
3. Click Add, give it a name like "NoBrandCards contacts", and click Save.
4. Make shows an address that starts with https://hook. and ends in make.com/…. Click Copy address to clipboard.

2. Add the webhook in NoBrandCards

Same as for Zapier: Settings › API and webhooks › Add a webhook, paste the address, keep New contact, then Add webhook.

3. Show Make a real contact

1. In Make, the webhook module says it's waiting for data. Leave the page open.
2. In NoBrandCards, add a test contact (Contacts › Add contact), or share your details on your own card.
3. Make shows Successfully determined. It now knows the fields.

4. Send the contact where you want it

Add the next module after the webhook: HubSpot CRM › Create a Contact, Google Sheets › Add a Row, Slack › Create a Message, or whatever you use. Map the fields from data › contact › email, data › contact › name and so on.

If you ticked more than one event, click the line between the two modules, choose Set up a filter, and continue only when type equals contact.created.

5. Turn it on

Click Save, then switch the scenario ON and keep Immediately as data arrives for its schedule. Make's free plan includes a monthly number of operations; each new contact uses a couple.

The fields you get

Every delivery has a type (contact.created for a new contact) and the contact under data.contact:

Field	What it is
name, email, phone	What they shared (email and phone can be empty)
company, title	Their company and job title, if they gave them
note	The note they left, or yours for a contact you added
answers	Their answers to your own questions on the exchange form (Pro), each with its label and value
tags, status, eventTag	Your tags, new / followed_up / closed, and the event they were tagged with
source, card.name	How they arrived (exchange when they shared from a card) and which card
metAt, metPlace, place.city	When you met, the place you typed, and an approximate city
assignedTo.name	On a team: who follows up
consentText	The consent line they agreed to when they shared their details

data.via says whether the contact came from a card (exchange) or was added by hand (manual).

Checking that it works

In NoBrandCards, open the webhook's menu and choose Deliveries. Each delivery shows whether it got through and what Zapier or Make answered. If one fails, for example because a scenario was off, NoBrandCards tries again for up to 24 hours (after 1 minute, 5 minutes, 30 minutes and so on), so a short outage doesn't lose a contact.

Each delivery has an id that stays the same on every retry. If your CRM ever shows a duplicate, match on that id or on the contact's email to skip repeats.

Keep the address private

Anyone who has your Zapier or Make address can send made-up data to it, so treat it like a password: don't post it or share screenshots of it. If it leaks, make a new address in Zapier or Make, edit the webhook in NoBrandCards to use it, and delete the old one.

Using your own server instead

If you'd rather receive the webhooks yourself, every delivery is signed with your webhook's signing secret: the X-NoBrandCards-Signature header is an HMAC-SHA256 of the request body. The API reference has the details and short examples, and the same contacts are available from the API with a Pro token.

Questions, or an app you'd like a step-by-step guide for? Get in touch from the help page.