If you host or attend Zyphoria Gatherings nights, you already know the logistics add up: invites, reminders, seating notes, and “who’s new?” follow-ups. Integrations let you connect your event calendar to the tools you already use—so updates stay consistent, communication stays respectful, and nothing important gets lost in a long email thread.
1) Decide what you’re syncing (and what you’re not)
Before you connect anything, write down the minimum data that must flow between systems. For most social-deduction game nights, these are enough:
- Event details: title, date/time, location, host contact.
- Participation: RSVP status, newcomer flag, accessibility notes (only if explicitly shared).
- Comms: confirmation, reminder, day-of updates, post-event recap link.
Rule of thumb: Sync scheduling facts widely; keep personal notes tightly scoped. If a field would feel awkward to read aloud, it probably shouldn’t sync to every tool.
2) Pick your integration pattern
Most setups fall into one of these patterns. Choose the simplest one that meets your needs.
-
One-way publish (recommended for most hosts): Zyphoria → your calendar. Guests can subscribe; you remain the source of truth.
-
Two-way sync (use carefully): edits in either system update the other. Great for small teams; risky if many people can edit calendar entries.
-
Event hub + automations: Zyphoria stays the event hub; your CRM and email tool receive structured updates (RSVP changes, attendance, follow-ups).
3) Calendar connections: Google Calendar, Outlook, Apple Calendar
Calendar integrations usually work via a subscribed feed (often an ICS calendar URL) or direct API sync. If you can, start with subscription—fewer moving parts, fewer accidental edits.
Option A: Subscribe to an ICS feed
- Best for: publishing official event dates/times.
- Pros: stable, read-only for subscribers, low maintenance.
- Watch-outs: feed refresh can be delayed (minutes to hours, depending on calendar provider).
Tip: Put critical last-minute changes (location switch, host running late) in a message channel too—don’t rely solely on calendar refresh.
Option B: Direct sync (API) to a host calendar
- Best for: a hosting team that manages events from a shared calendar.
- Pros: faster updates, richer fields.
- Watch-outs: permissions. A single “edit” mis-click can overwrite the source of truth.
4) CRM connections: tracking relationships without getting creepy
A CRM can be useful for community stewardship—especially for adults who appreciate clear communication and low-pressure re-invites. The goal isn’t surveillance; it’s making sure newcomers don’t fall through the cracks and regulars get the right level of updates.
Suggested CRM fields for gatherings
| Field | Purpose | Notes |
|---|---|---|
| Preferred name | Respectful communication | Avoid duplicating legal names unless required. |
| Contact email | Invites + confirmations | Use one canonical field to prevent mismatches. |
| Newcomer flag | Extra guidance, friendly check-in | Clear after first attended event (or after 2–3). |
| Attendance count | Know who’s active | Store counts, not detailed play outcomes. |
Simple connection approaches
- Spreadsheet as CRM-lite: export attendee list after each event, then tag newcomers and follow-ups.
- CRM via automation: when RSVP becomes “Yes,” create/update a contact; when “Attended,” increment attendance.
- Email tool integration: add “newcomer” segment for the pre-event expectations note and the post-event check-in.
5) Automation recipes that work well for game nights
Recipe: Newcomer-friendly confirmation
Trigger: RSVP = Yes → Action: send a short note with arrival time, “how to jump in,” and who to look for.
Recipe: Day-of reminder (low anxiety)
Trigger: 10–12 hours before start → Action: reminder + parking/transit + a “no worries if plans change” cancellation link.
Recipe: Post-event recap + next date
Trigger: event marked complete → Action: send recap link + optional survey + subscribe link to the upcoming calendar.
6) Consent, privacy, and retention (don’t skip this)
Integrations multiply where data travels. Make it easy for participants to understand what’s stored and why, and keep retention practical.
- Consent: be explicit when someone’s email is added to a list or CRM segment.
- Least access: give calendar/CRM permissions to a small set of hosts.
- Retention: delete or anonymize old RSVP exports after a set period unless you have a clear reason to keep them.
For broader site guidance, see the resources list on blog.html#blog-list.
7) Troubleshooting checklist
- Duplicate events: confirm you’re not both importing and manually creating the same event.
- Wrong time zone: set one canonical event time zone; avoid “floating time” where possible.
- Missing updates: ICS feeds can refresh slowly—verify the provider’s refresh interval.
- CRM mismatch: standardize on one unique identifier (usually email) and normalize formatting.
Quick start: a clean, newcomer-friendly setup
- Publish events from Zyphoria and share a read-only calendar subscription link.
- Use a single RSVP export or automation to update a small contact list.
- Send two messages only: confirmation (with expectations) and day-of reminder.
- Track just enough CRM data to follow up respectfully—nothing more.
Want to see how this fits into your overall hosting routine? Start at index.html#newcomer-notes for participation notes and an easy on-ramp for first-timers.