Build & deploy · 9 min read
Integration setup: IDs, keys & webhooks
Where to get the credentials and which redirect URI / webhook to register for Google, Microsoft, Apple, Twenty, Zoom, Stripe, Twilio, Telegram and Resend.
Every integration is optional and env-gated - a provider stays inert until you set its keys, so you only wire up what you need. This guide tells you, per provider, where to get the credentials, which redirect URI or webhook to register, and which environment variable each value goes into.
Two things everything depends on. First, APP_URL: your deployment's public base URL (e.g. https://braveday.work) - every redirect URI and webhook below is APP_URL plus a fixed path, and it must be the exact public HTTPS origin with no trailing slash. Second: after editing env vars, rebuild/redeploy (some are read at build time). Redirect URIs and webhook URLs must be registered EXACTLY in each provider's console or the callback is rejected.
Google Calendar (and Google sign-in)
- Google Cloud Console → create/select a project → enable the Google Calendar API.
- Configure the OAuth consent screen and add your account as a test user (or publish).
- Credentials → Create OAuth client ID → Web application. Authorized redirect URI: APP_URL/api/calendars/connect/google/callback
- Set GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET (and NEXT_PUBLIC_GOOGLE_AUTH=1 to show the Google sign-in button).
- Scopes: calendar.events, calendar.readonly, openid, email, profile.
- Real-time push sync auto-registers at APP_URL/api/webhooks/google - Google requires a verified domain over HTTPS; if unavailable it's non-fatal (falls back to polling).
Microsoft 365 / Outlook
- Azure Portal → Microsoft Entra ID → App registrations → New registration.
- Redirect URI (Web): APP_URL/api/calendars/connect/microsoft/callback
- Certificates & secrets → New client secret → copy the VALUE.
- API permissions → Microsoft Graph → Delegated: Calendars.ReadWrite, User.Read, offline_access, openid, email, profile.
- Set MICROSOFT_CLIENT_ID (the Application/client ID) and MICROSOFT_CLIENT_SECRET (the secret value).
Apple iCloud
No developer setup or env vars. Apple calendars connect over CalDAV with a per-user app-specific password: each user generates one at appleid.apple.com (Sign-In & Security → App-Specific Passwords) and pastes it in Settings → Calendars → Apple - never their real Apple ID password.
Twenty (self-hosted CRM sync)
- Deploy Twenty at a public HTTPS origin such as https://crm.ravefox.dev.
- Register a public OAuth client with callback APP_URL/api/integrations/crm/twenty/callback and grants authorization_code plus refresh_token.
- Set TWENTY_BASE_URL and TWENTY_CLIENT_ID. The dynamically registered client uses PKCE and has no client secret.
- Users connect from Settings → CRM in one click; bookings create or match a Person and keep a linked Task in sync.
Zoom (video links)
- Zoom App Marketplace → Develop → Build App → OAuth (user-managed).
- Redirect / OAuth allow-list URL: APP_URL/api/integrations/zoom/callback, with the scope to create meetings.
- Set ZOOM_CLIENT_ID and ZOOM_CLIENT_SECRET (the connect button is hidden without them).
- Google Meet needs no setup - it comes with the Google Calendar connection; Teams links come with the Microsoft connection.
Stripe (Pro billing - cloud edition only)
- Developers → API keys → copy the Secret key → STRIPE_SECRET_KEY.
- Products → add a Product with a RECURRING price ($9/seat/mo). Open the price and copy its API ID (starts with price_) → STRIPE_PRICE_PRO. It MUST be the price_ ID, not a number.
- Developers → Webhooks → Add endpoint: APP_URL/api/webhooks/stripe. Events: checkout.session.completed, customer.subscription.created / updated / deleted. Copy the signing secret → STRIPE_WEBHOOK_SECRET.
Note
The webhook flips an org to Pro after payment and tracks seat/cancel changes. BraveDay also reconciles the plan on the checkout-success redirect, so a single missed webhook won't leave you stuck - but configure the webhook for ongoing changes.
Twilio (SMS / WhatsApp reminders)
- Twilio Console → copy Account SID + Auth Token.
- Set TWILIO_ACCOUNT_SID, TWILIO_AUTH_TOKEN, TWILIO_SMS_FROM (E.164 number), and TWILIO_WHATSAPP_FROM (whatsapp:+…).
- For inbound replies, set the number's / Messaging Service's incoming-message webhook to APP_URL/api/webhooks/twilio.
Resend (email) - the #1 setup mistake
- Resend → API Keys → create one → RESEND_API_KEY.
- Domains → Add domain, add the DNS records, and wait for Verified.
- Set EMAIL_FROM to an address ON that verified domain, e.g. "BraveDay <no-reply@yourdomain.com>".
Heads up
An unverified/placeholder domain (like example.com) makes EVERY email bounce with 550 domain is not verified - confirmations and reminders silently fail. Alternative to Resend: any SMTP server via SMTP_URL.
Tip
Full reference with the exact table of env vars, redirect URIs and webhooks lives in docs/INTEGRATIONS.md in the repo. Every failure is logged with a structured event (billing_checkout_failed, confirmation_email_failed, sync_watch_failed) you can grep in your container logs.
Related guides
Running your own deployment
How a BraveDay instance is deployed on your own cloud server, and what it runs.
Connect a calendar
Link Google, Outlook, iCloud, or any feed so you're never offered a time you're busy.
CRM sync (Twenty)
Log every booking to your CRM automatically - person plus a linked task.
Developer: API, webhooks & embed
Keys and REST endpoints, signed booking events, and the embeddable widget.
Ready to try it? Get started free, or browse all guides.