Connect LineBlink to Zapier

Create a dedicated connection

Availability depends on the integration release and your tenant’s current eligibility. Use the supplied private invitation during beta. A public Zapier directory listing is not required for an invited beta connection.

In API & Integrations, create a key with integrationType: zapier and only the needed scopes and resource restrictions. Paste the one-time secret into Zapier’s authentication field. Zapier tests /me and labels the connection with the tenant name. Do not reuse a general-purpose production key.

Choose an instant trigger

Available trigger definitions cover New Waitlist Entry, Entry Status Changed, Guest Ready, Guest Completed, New Booking and Booking Cancelled. Setup samples come from the immutable event feed; synthetic examples do not contain real guest contacts.

Zapier uses event.id for deduplication and exposes entryId separately. The same entry can produce several status events. Zapier creates a REST Hook subscription when a Zap is enabled and deletes it when the Zap is disconnected.

Map an action and its retry identity

Actions cover Add Guest, Create Booking, Change Entry Status and Cancel Entry or Booking. Searches find an exact entry ID or external reference and discover authorized businesses and lines.

Each action requires a stable Action Reference. Combine the source event or record ID with a unique suffix for that Zap step. Retries must reuse the same reference and input. A second legitimate action needs a new reference even if its guest fields match. Never create a fresh random reference during every retry.

Guest External Reference is separate and optional. It maps to externalReference for later exact lookup, not to the action’s retry identity. Map SMS consent only when the source collected affirmative permission, including source, time and disclosure version. Without that mapping, creation uses the permitted non-SMS workflow. Status changes require the current expectedStatus and expectedVersion.

Reconnect or disconnect safely

A 401 requires reconnecting with a valid dedicated key. A 402 requires current plan access or remaining allowance. A 409 needs review of the latest entry or the action’s reused reference. Zapier handles 429 as throttling.

Revocation affects every Zap using that key and stops its webhook deliveries. Disconnect the related Zaps before deleting an unused connection. Example workflows include completed guests to a CRM or spreadsheet, bookings to a calendar, and form submissions to a waitlist.