Integrations

Zapier

Zapier connects Tobachat to the rest of your stack without writing code. Our Zapier app is available by invitation. Under Integrations you'll find the invite link and generate an API key; you paste that key into Zapier when you connect your account. The key is shown once, so save it there and then.

There are 7 moments where Tobachat pushes something to Zapier, and 6 things Zapier can ask us to do.

• Tobachat reports: a new contact, an opt-out, an incoming message, a finished campaign, a finished automation, an assigned conversation, and a template changing status.
• Zapier can trigger: create or update a contact, add a label, remove a label, send a template, send a text message, and start an automation.
• A text message through Zapier only works inside the 24-hour window. Outside it, use the action that sends a template.

FareHarbor

Bookings from FareHarbor can start a flow. On every change FareHarbor forwards the booking to us, and we turn it into 1 of 4 events: created, changed, cancelled, or rebooked.

Switching it on takes two steps. Under Integrations you click connect and get a webhook address. You email that address to FareHarbor support and ask them to enable the webhook for bookings. FareHarbor has no screen where you can do this yourself.

Then you build a flow with the booking trigger. You can filter on a specific tour and time the flow relative to the start or the end of the activity.

• A booking does not create a contact. A booking is a transaction, not marketing consent, so the flow runs on the phone number from the booking.
• The same tab keeps a log of what FareHarbor has sent recently.

LetsBook

Reservations from LetsBook arrive as contacts. We create or update the contact, apply a label, and read the WhatsApp question from the booking form as consent.

You connect under Integrations. You get a webhook address and can add a shared secret that LetsBook uses to sign its requests.

A webhook into Tobachat

If your system has no ready-made integration, you can deliver contacts yourself. Under Integrations you generate a key and get an address that accepts a phone number, a name, and a label. The key travels as a header.

A second kind of webhook lives in the automation builder. The incoming-webhook trigger gives each flow an address of its own. Whatever you post is available inside the flow as a variable, as long as a phone number is in there.

From Tobachat to another system

An automation can include a step that calls another API. You choose the method, set your own headers and body, and can store fields from the response as variables to branch on afterwards.

Addresses on a private network are refused, a call stops after 60 seconds at the latest, and the response is capped at 1 MB.

If your system isn't listed

Under Integrations there's a button to request one. Tell us which system you use and what you want it to do, and we'll look at what's possible.