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.

Triggers send data from Tobachat to Zapier; actions let Zapier do things in Tobachat.

• Triggers: a new contact, an opt-out, an incoming message, a completed campaign, a completed automation, an assigned conversation, and a template status change.
• Actions: 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, canceled, 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

LetsBook reservations come in as contacts. We create or update the contact, add a label, and use the answer to the WhatsApp question on 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 there's no ready-made integration for your system, you can send us contacts yourself. Under Integrations, create a key and get a URL that accepts a phone number, a name, and a label. Send the key 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.

A call times out after 60 seconds.

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.