Integrations

Summarygenerating…

Overview

Because Table Bookings, Wi-Fi, PayOS, Loyalty, Reviews, and Analytics all write to the same guest profile, there is no integration work to do. Enable the modules you have, and their events appear as triggers, conditions, and attribution points.

How it works

Each module emits typed events onto the guest profile (booking.created, bill.closed, review.received, etc.). Workflows and audiences subscribe to those events or query the derived state.

Core concepts

Native integration

modules share a single data layer, not an API bridge.

Event trigger

real-time enrolment of guests into workflows as events arrive.

Usage & workflows

Turn on the modules you use; every new signal becomes available in audiences and workflows immediately.

Example

Switching on PayOS instantly adds "guests who spent over £50 in the last 30 days" as a possible audience — no separate ETL, no field mapping.

Note

Where to find it

Configure this in the Stampede admin app under Admin → Marketing. Permissions are role-gated — contact your account owner to request access if you don't see it.

Tip

API reference

The Stampede API exposes guest, booking, and campaign data programmatically. See developer.stampede.ai for authentication, base URL, rate limits, and endpoint reference.

Note

Need help?

Contact support via the Stampede admin app or your account manager. The knowledge base at help.stampede.ai has guided walkthroughs for common tasks.

Want to see it live?

Book a 20-minute walkthrough and we'll show you the feature in your own admin.

Book a demo