Integrations
Get started with integrations
Send guest details and finished photos to Slack or to your own systems. Integrations are enabled per account on request.
On this page
Connect Slack without application code, or ask a developer to connect your own app or display. Choose a guide below. If you do not see Integrations in your team navigation, request access first.
Choose a path
Post new leads to a Slack channel with no code: Connect Slack lead notifications, then Send leads to a connected destination.
Receive every lead or finished photo in a system you run: Receive signed webhooks at your own endpoint.
Feed only host-approved photos to a display you built: Send approved photos to your own display.
Read submissions on demand, send photos in, or hide media from your own tools: Partner API reference.
Ask Snapbar to enable integrations
Email ops@thesnapbar.com with your team name and what you want to connect. Integrations are switched on per account by Snapbar, so they are hidden until that step is done.
Once enabled, Integrations appears in your team navigation and every experience you can edit gains a Destinations tab. If a teammate does not see them, they are signed into a different team or the account is not enabled yet.
Team owners and admins manage destinations, API keys, and endpoints. Other roles see a Manager access required notice on Destinations and Developer and can still read Activity; replaying a delivery needs permission to edit experiences.
Know the three sections
Destinations lists the external accounts Snapbar can deliver to. Today that is Slack. Each experience then chooses when and what to send in its own Destinations tab.
Activity is the delivery record for every destination and webhook endpoint: what was sent, what was skipped and why, and what needs attention. See Fix failed deliveries.
Developer creates and revokes API keys and lists the webhook endpoints registered through the API, with the health of each one. See Create API keys.
What to know
- Consent controls what leaves Snapbar.Every destination and endpoint carries a policy. Guests who agreed to marketing is the default and only sends leads with marketing consent. All guests with contact details requires a written confirmation in the dashboard. Webhook endpoints can also use a photos-only policy that sends no guest details at all.
- Other tools are on request.CRM connections, Zapier, and attendee directory imports are not self-serve yet, and none of them appears as a card under Destinations. Tell ops@thesnapbar.com which tool you need and what should be sent, and we will confirm what is available for your account.
Tips
- Name one technical owner for each endpoint or destination before an event so a reconnect or a replay does not wait on a search for the right person.
- Use a test channel or receiver first. Follow the setup guide to connect and verify the production destination before the event.