Integrations

Choose how Waitlyze connects to email, notifications, event receivers, and automation tools.

Connect the part of your launch workflow that needs to leave Waitlyze. Some connections are configured in workspace or waitlist settings; others are event-based recipes rather than native apps. Each guide calls out the setup path and its current limits.

Email delivery

Use Resend for opted-in broadcasts and marketing automations. Cloudflare Email Sending is available for transactional signup confirmations; it does not support marketing or bulk sends. Workspace connections are managed in Settings → Integrations.

Notifications

Slack and Discord receive a best-effort milestone message when a waitlist reaches a signup milestone. They are separate destinations; neither is a general-purpose event stream.

Event delivery

Use Waitlyze webhooks when another system needs a signed, retryable event for signup, verification, referral, or milestone activity. The payload contains IDs rather than subscriber email addresses.

Automation recipes

Zapier is not a native Waitlyze app. Connect it through Webhooks by Zapier with the Catch Raw Hook trigger, then use a Code step and the Waitlyze signing secret to verify each event's raw body and x-waitlyze-signature header before the Zap acts on it. Mirroring signups into an email provider (Klaviyo, Mailchimp, Kit) follows the same webhook-first pattern: consume signup.verified in a function you own and call the ESP's subscribe API.

API or webhook?

Use the API when your server needs to create a signup, retrieve its status, or award points. Use a webhook when Waitlyze should tell your system that something happened. Slack and Discord are simple milestone notifications; Zapier is a recipe that consumes the same webhooks.

On this page