QueueUp / docs

Integrations overview

Outbound destinations for waitlist events. Webhooks for any HTTPS endpoint, Resend for transactional email.

Integrations are the outbound destinations QueueUp sends events to when something happens on a waitlist. Two types ship today:

  • Webhook. Any HTTPS endpoint. QueueUp signs deliveries with HMAC-SHA256 and retries on failure. Use this for any custom logic on your side: piping signups into your CRM, kicking off provisioning, paging your team.
  • Resend. Outbound transactional email through your own Resend account. QueueUp renders the email body and posts it to Resend with the API key you supplied.

You can have as many of each type as you want. Each integration is scoped to your organisation, so it’s reusable across every waitlist in the org.

Integrations are a Pro and Team feature. On Free, any integrations carried over from a paid plan stay in the list but stop firing until you upgrade. See Pausing and deleting for details.

How it fits together

signup → event (subscriber.joined, subscriber.confirmed)
       → binding (matches event_types on a waitlist)
       → integration (webhook or Resend)
       → delivery (HTTP POST or email send, with retries)

Integrations don’t do anything on their own. To make them fire, you bind them to one or more waitlists. Each binding is its own routing rule with its own event scope, so the same integration can power different events on different waitlists.

Where things live in the panel

PageWhat you do here
Integrations (top nav, admin only)List every integration in the org, create new ones, jump into deliveries / settings
Integrations → Add integrationPick a type and fill in the type-specific form
Integrations → <integration>Recent deliveries, Send test button, jump to settings
Integrations → <integration> → SettingsIdentity, configuration, pause toggle, rotate / replace secret, delete
Waitlist setup → IntegrationsBind / unbind integrations to a waitlist, scope events per binding