tufu
Start free

Webhooks, with Zapier and Make

Leads from the chat, in the tools you already use. Your CRM, your list, your sheet.

When a visitor leaves their details, tufu posts them to an address you choose within seconds, so nobody copies a lead out of the inbox by hand.

Free US$0 · Starter US$19 · Team US$49 · Scale US$249 a month. One price for the whole team. No seats, ever.

What to know

  • What it sends

    Two events: lead.created the first time someone leaves their details, and lead.updated when they do it again, a teammate edits them, or the status moves between New and Followed up.

  • What it needs

    An https address on the public internet that answers with a 2xx within ten seconds: a Catch Hook in Zapier, a Custom webhook in Make, or a route on your own server.

  • Which plan

    Webhooks come with Team. Any admin adds them under Settings, and there's no extra charge per event.

How it works

Wire it up in three steps.

  1. 01In Zapier start a Zap with Webhooks by Zapier and Catch Hook, or in Make a scenario with Custom webhook, and copy the address it gives you.
  2. 02In tufu open Settings, then Webhooks, then Add a webhook. Paste the address and keep A visitor leaves their details ticked.
  3. 03Press Send test. A sample lead arrives, so you can map lead.email and lead.name onto HubSpot, Mailchimp, a Google Sheet or anything else on the other side.
Read the guide
The tufu inbox with a conversation open: the visitor's details beside it, the same details a webhook sends on.

Questions

Before you start.

Does a webhook send the conversation?

No. The body carries the lead (name, email, phone, your custom fields and consent), the bot, the team and a link to the conversation in your inbox. A conversation's words are never sent.

How do I know a request is really from tufu?

Each webhook gets a signing secret, shown once. Every request has a Tufu-Signature header, an HMAC-SHA256 of the time and the raw body; refuse one more than five minutes off your clock.

What if my server is down?

tufu tries again, five tries in all over about two and a half hours, and every try shows on the webhook's card. After fifteen failures in a row it pauses the webhook and emails your admins.

Could the same lead arrive twice?

A retry keeps the event's id, so your code can skip one it already handled. Zapier and Make simply run again with the same fields.

Set it up before your next support email.

Free to start, no card needed. Point it at your site and it's answering in about ten minutes.

tufu is not affiliated with or endorsed by Zapier. Zapier is a trademark of its owner.