Send new contacts to other apps
Each new contact reaches a Google Sheet, your CRM or your own server within seconds, through Zapier or Make. Free on every plan.
Every new contact on your Kard can go straight to another app as it arrives: a row in a Google Sheet, a new lead in your CRM, a message to your team, or your own server. You give the Kard one web address, a "webhook", and from then on each new contact is sent there within seconds. It's free on every eKard plan.
Zapier and Make are the easiest way in: they turn the contact into a row, a lead or a message without any code. Zapier counts its "Webhooks by Zapier" app among its premium apps, which its free plan doesn't include; Make's webhooks work on its free plan. Check their current plans before you start.
What's sent, and when
- Every new contact, however they came: the form on your Kard, a Kard shared back, a booking, or someone you typed in or scanned with the app. Editing a contact sends nothing.
- What each one carries: their name, email, phone, message, company, job title and card notes, any answers to your form, the event they came from, how they came ("Sent their details from your Kard", "Read off their paper card"…), and the Kard's name and link.
- An
idthat never changes for one contact, even if it's sent twice, so your app can skip repeats.
Set it up with Zapier
- In Zapier, make a new Zap. For the trigger, choose Webhooks by Zapier, then the event Catch Hook, and continue. Leave "Pick off a child key" empty.
- Copy the webhook URL Zapier shows. It starts with
https://hooks.zapier.com/. - In eKard, open Kards, pick the card, open its Settings tab and, under "Send new contacts to other apps", press "Set up a webhook". Paste the address into "Address (https)" and press "Start sending".
- The page shows a signing secret once. Zapier doesn't need it; copy it only if your own server will check signatures.
- Press "Send test". Back in Zapier, press "Test trigger": it finds a sample contact called "Sample contact", with made-up details.
- Add the action. For a spreadsheet, choose Google Sheets, "Create Spreadsheet Row", and match your columns to the fields Zapier lists: "Data Contact Name", "Data Contact Email", "Data Contact Phone Number", "Data Contact Card Details Company", "Data Contact Card Details Job Title", "Data Source Label", "Data Kard Name" and "Data Contact Created At". For a CRM, choose its "Create contact" or "Create lead" action and match the same fields.
- Publish the Zap. The next person who leaves their details reaches it within seconds.
Set it up with Make
- In Make, create a new scenario. Add the Webhooks module and choose Custom webhook. Press "Add", give it a name such as "New Kard contacts", and save.
- Copy the address Make shows. It starts with
https://hook.and ends inmake.com/and a code. - In eKard, open the card's Settings tab, press "Set up a webhook", paste the address and press "Start sending".
- Make's module now waits to learn what the data looks like. Press "Send test" in eKard: Make says it determined the data structure.
- Add the next module. For a spreadsheet, Google Sheets, "Add a Row"; for a CRM, its "Create a contact". Map the fields from
data→contact:name,email,phone_number,card_details→companyandjob_title, and fromdata:source_labelandkard→name. - Save, and switch the scenario on with "Immediately as data arrives".
Keep tests out of your sheet
A test carries "test": true; a real contact doesn't carry test at all. To keep tests out, add a filter before the action. In Zapier, a "Filter by Zapier" step: only continue if "Test" does not exist. In Make, click the line between the two modules and set up a filter: test, "Does not exist".
Watch it work
The webhook page shows where contacts go, whether it's working, and the recent deliveries: each new contact and each test, with what the other app answered. A contact that has to wait its turn says when it goes: a Kard sends up to 60 a minute, after the first 30 at once, and the rest wait rather than being dropped.
If the other app doesn't answer, a contact is tried again 5 more times over about 15 minutes. After 10 new contacts in a row fail, the webhook pauses itself and you get an email. Your contacts are always kept in the Kard's Contacts either way, and contacts from while it was paused aren't sent later: the recent deliveries list them as "Not sent", and you can export them as a spreadsheet to fill the gap. To start again, fix the other side (in Zapier or Make, check the Zap or scenario is on), press "Send test", then "Turn back on".
The same people who can see the Kard's contacts: you for your own Kard; for a team Kard, the person who holds it and the organization's admins. Each Kard has one address. To use another, remove it and add the new one: it gets a new signing secret.
Your own server
Any https:// address that's reachable on the internet works; private and local networks are never called. Each contact is a JSON POST signed to the Standard Webhooks spec, so its libraries can check the webhook-signature header with your signing secret. Answer with any 2xx status within 10 seconds. The JSON, the headers and how to check a signature are in the API reference.
Each delivery carries people's names, emails and phone numbers. Send them only to services you trust, and share the sheet or CRM they land in only with people who should see your contacts.