Zapier integration for Flipbooker

Why bother connecting a flipbook to Zapier?

A flipbook that captures a lead is only half a workflow. The lead still has to reach the person who will act on it. Exporting a CSV once a week is how good leads go cold.

The same is true of reader behaviour. Knowing that a prospect opened your proposal twice and spent four minutes on the pricing page is useful on the day it happens, not at the end of the month. A Zap moves both to wherever your team already works.

Two things you can send

Which reader events can you send?

Nine event types are available. Subscribe only to the ones you will act on, because every extra event is another delivery your Zap has to absorb and another task against your Zapier quota.

How do you connect Flipbooker to Zapier?

Both paths start the same way, with a catch hook in Zapier.

1. 1

   Create a Zap with a webhook trigger

   In Zapier, start a new Zap and pick Webhooks by Zapier as the trigger, then Catch Hook. Zapier gives you a URL. Copy it.

2. 2

   Paste the URL into Flipbooker

   For lead forms, open the flipbook's lead form settings and paste the URL into the Zapier webhook field. For reader events, create a webhook subscription with the URL as the target and pick the event types you want.

3. 3

   Send a test delivery

   Submit the lead form yourself, or fire a test delivery against the subscription. Zapier needs one real payload before it can show you the fields.

4. 4

   Map the fields

   Zapier now lists the fields from the payload. Map them to whatever comes next: a CRM contact, a Slack message, a row in a sheet.

5. 5

   Turn the Zap on

   Check the delivery history in Flipbooker if events stop arriving. It records each attempt with the status your endpoint returned, so you can tell a Flipbooker problem from a Zapier one.

What does a lead form payload look like?

A lead form delivery carries the submitted fields and the flipbook they came from. Empty optional fields are still present, so your Zap can rely on the shape.

{
  "book_id": 4821,
  "fullname": "Dana Whitfield",
  "email": "[email protected]",
  "company_name": "Whitfield Interiors",
  "phone_number": "+44 20 7946 0958",
  "website": "https://example.com",
  "address": "",
  "message": "Interested in the spring catalogue."
}

Reader event deliveries carry an event_type instead, along with the page number, active time in milliseconds, source host, tracked link, referrer, UTM fields, and country or region where those are known.

How do you know a delivery really came from Flipbooker?

Every delivery is signed. Zapier catch hooks accept anything posted to the URL, so if the data drives anything that matters, check the signature before you trust it.

• Three headers arrive with each request: X-Webhook-Signature, X-Webhook-Timestamp and X-Webhook-Event.
• The signature is an HMAC-SHA256 of the timestamp, a full stop, and the request body, keyed with the signing secret you set when you created the subscription.
• Reject anything whose timestamp is more than five minutes old. That is the window Flipbooker itself enforces, and it is what stops an old delivery being replayed at you.
• Compare with a constant-time function rather than a plain equality check.

What do people actually build with this?

Common questions

Related