System of record
1
Withinstay dashboard
Host console
Backend dashboard for operators and integration setup.
Build the backend workspace for universal arrival links, channel message templates, guest records, add-on orders and fulfilment inside Withinstay.
System of record
1
Withinstay dashboard
Universal entry
1
Hosted arrival form
Email flows
3
Resend lifecycle emails
Backup outputs
1
Optional Google Sheets
Message channels
3
WhatsApp and OTA links
Start with the Withinstay dashboard as the system of record, then add delivery and backup connections around it.
Withinstay dashboard data
Native tenant database with role-controlled dashboard access
Withinstay is the canonical database. External services deliver guests into the flow, send messages or receive optional backups; they do not become the operating database.
Hosted pre-arrival forms
Withinstay hosted branded links
This becomes the universal layer: every host gets a branded arrival form link that can be sent through any platform message, email, WhatsApp or PMS template.
Resend
Server-side API key with verified sending domain
Resend becomes the hosted transactional email layer for Withinstay, with optional hosted template IDs and webhooks for sent, delivered, bounced, complained and suppressed events.
Google Sheets
Google OAuth 2.0 or service account for host-owned backup sheets
Sheets is an optional one-way backup/export for hosts who want their own copy. Withinstay remains the dashboard and system of record.
Airbnb message templates
Host-managed Airbnb scheduled quick replies
This avoids restricted Airbnb APIs: the host uses Airbnb’s own automated guest messaging to deliver a Withinstay form link.
Booking.com message templates
Host-managed Booking.com extranet/Pulse messaging
This avoids needing full Connectivity API access on day one while still reaching Booking.com guests through supported messaging surfaces.
These are the objects Withinstay owns before any optional Google Sheets backup export is created.
The dashboard separates owned Withinstay data from message delivery, optional backup exports and PMS enrichment.
| Provider | Use | Access | Next step |
|---|---|---|---|
| Withinstay dashboard data | Keep guest profiles, arrival details, add-on requests, fulfilment status, consent and email events inside Withinstay. | System of record | Configure |
| Hosted pre-arrival forms | Collect guest details, wellness preferences, arrival times, add-ons and consent from any booking channel. | Native core | Configure |
| Resend | Own the guest email lifecycle after a guest enters a Withinstay flow: confirmations, add-on order emails, host alerts and delivery tracking. | Email backbone | Configure |
| Airtable | Potential internal research or one-off import/export support, not the live Withinstay guest database. | Not primary | Configure |
| Google Sheets | Export a host-owned copy of guest rows and add-on requests for backup access outside Withinstay. | Optional backup | Configure |
| Gmail | Optional mailbox handoff for hosts who want Gmail drafts, labels or reply capture outside the Resend lifecycle flow. | OAuth app needed | Configure |
| Send pre-arrival form links, receive guest replies and alert operators on high-intent requests. | Business setup | Configure | |
| Airbnb message templates | Paste the Withinstay arrival form link into Airbnb quick replies or scheduled quick replies. | Template delivery | Configure |
| Booking.com message templates | Send Withinstay pre-arrival links through Booking.com guest messaging, Pulse or partner messaging flows. | Template delivery | Configure |
| Hostaway | Optional PMS sync for hosts that already use Hostaway; not required for the universal form flow. | Credential-ready | Configure |
Google sign-in is ready in the codebase, but the production credentials need to be added before hosts can create accounts.
Add Google OAuth credentials, then hosts can sign in and complete setup.
Google auth setup
Create a Google OAuth web client, add the redirect URI below, then set the client ID and secret in Vercel.