Connect Fareply to Zapier, Make or n8n
Fareply can tell your other tools what happens in your conversations, within seconds: a new lead, a quote sent or accepted, a payment, a booking, a lost lead. Your tool then adds a row to a sheet, a deal to your CRM or a task for your team, without anyone typing it again. An owner sets this up under Integrations. Pro, Agency and DMC plans.
1. Get an address from your tool
- Zapier: create a Zap. As the trigger choose Webhooks by Zapier, event Catch Hook, and copy the webhook URL.
- Make: create a scenario. Add the module Webhooks, Custom webhook, click Add, and copy the address.
- n8n: add a Webhook node, set the method to POST, and copy the production URL (activate the workflow so it listens).
- Your own system or CRM: ask your developer for an https address that accepts a JSON POST. The details are at the bottom of the Integrations page.
2. Connect it in Fareply
- Open Integrations (under Setup) and click Add connection.
- Paste the address, give it a name you will recognise, for example "Zapier: leads to Google Sheets".
- Choose the events. The usual ones are already ticked.
- Click Connect. Fareply shows a signing secret once. You only need it if your developer checks that events really come from Fareply; Zapier, Make and n8n users can skip it.
- Click Send test. Your tool receives a test event, so it knows the fields. In Zapier, click Test trigger after this; in Make, the webhook module shows "successfully determined".
3. Build the rest in your tool
Add the action you want after the trigger, for example Google Sheets: Create row or HubSpot: Create
deal, and map the fields: the traveller's name and phone, the channel, the quote total, the booking reference, the
link back to the conversation in Fareply. Use a filter on type if one scenario handles several events.
The events
| Event | When |
|---|---|
New lead lead.created | A traveller writes to you for the first time, on any channel. With the first message and, for ads, which ad. |
Message received message.received | Every message a traveller sends. Can be many: choose it only if your tool needs every message. |
Quote sent quote.sent | A priced reply, a quote PDF or a quote page link was sent, with the total and currency. |
Quote accepted quote.accepted | The traveller accepted a quote on the quote page. |
Payment link sent payment.requested | A deposit, balance or full payment was asked for, with the amount and the payment page. |
Payment marked paid payment.paid | Your team marked a payment link as paid. |
Booking reference saved booking.updated | A booking reference was added, or its status changed (confirmed, on request, cancelled). |
Lead booked lead.booked | The conversation was marked booked, with its value. |
Lead lost lead.lost | A lead was marked lost, with the reason. |
Every event carries the conversation: the traveller's name, phone or email, the channel, who it is assigned to, the ad it came from, the booking reference, and a link that opens it in Fareply.
When something goes wrong
- Delivery log shows every event sent to a connection in the last 30 days, your tool's answer, and the event itself (View). Send again sends one event once more.
- If your tool does not answer, Fareply tries again after 1, 5 and 15 minutes, then 1, 3, 6, 12 and 24 hours.
- If a connection keeps failing for more than a day, Fareply pauses it and emails the owners. New events are kept. Fix the address in your tool (a Zap that was switched off, a deleted scenario), click Send test, then Switch on: the waiting events are sent.
- "HTTP 404" or "HTTP 410" usually means the address no longer exists in your tool. "HTTP 3xx" means the address redirects: use the final address. Fareply only calls public https addresses.
- Lost the signing secret? Click New secret and update it in your system. The old one stops working at once.
Good to know
- Up to 5 connections per agency, each with its own events.
- An event is sent only when the change is saved in Fareply: an undone action sends nothing.
- Each event has an
id. If your tool might receive the same event twice (after a retry), use it to skip repeats. - To send bookings into Fareply from your booking system, see Booking references and confirmations.