Integrations

The problem

Every event generates data your CRM never gets.

RSVPs, attendance, dietary preferences, conversation notes. Most of it stays in your event tool until someone exports a CSV and manually updates the CRM. By then, the follow-up window has closed.

What Gatsby does differently

Native CRM Integrations

RSVP status, attendance, and guest data sync to Affinity, Salesforce, and Altvia as it happens. Check in a guest at the door. Your CRM reflects it before they sit down.

API, Webhooks, and MCP

For tools without a native integration, webhooks push event data through Zapier, Make, or n8n. The REST API gives your developers read and write access to everything Gatsby captures. Teams are also building MCP servers for AI-powered workflows on top of Gatsby data.

Integrations

Your CRM, connected

RSVPs, attendance, and contact updates sync as they happen.

Affinity

Bidirectional sync. Build guest lists from Affinity contacts and push attendance back automatically.

Salesforce

Map RSVPs to campaigns. Push attendance, first-party data updates, and custom fields in real time.

Altvia

Built on Salesforce for fund managers. Sync LP event participation to Functions automatically.

Attio

Event activity flows through Google sync. Webhooks push structured attendance data for reporting.

Zoom

Create or connect Zoom meetings from Gatsby. Links appear in calendar invites automatically.

Webhooks & Zapier

Push event data to HubSpot, Attio, Airtable, Slack, or any app through Zapier, Make, or n8n. No code required.

CRM integrations and API access are available on select plans. We’ll walk through what’s included for your team during a demo.

Beyond CRM Sync

Native integrations cover the CRMs most of our customers use. For everything else, the API and webhooks put event data wherever your team needs it.

Your event data, on demand

Gatsby exposes a REST API with read and write access to events, guests, RSVPs, attendance, and contact data. Pull guest history into your CRM, feed a BI tool, or build custom workflows. Teams use it for everything from internal dashboards to fully custom registration flows.

What the API exposes

+

• Events, guest lists, and RSVP status
• Attendance records and check-in data
• Custom field values stored in contact profiles
• Read and write access (pull guest data in, push updates out)
• Webhook subscriptions for real-time event triggers

Common use cases

+

• Internal dashboards that aggregate attendance across your full event calendar
• Custom registration workflows for complex event series with conditional routing
• Data warehouse pipelines feeding BI and reporting tools
• CRM enrichment for platforms without a native Gatsby integration

AI and MCP

The same structured data that feeds your CRM feeds AI workflows. Teams have built MCP servers and custom agents on the Gatsby API, giving AI tools direct access to event history, guest preferences, and attendance patterns.

What teams are building

+

• MCP servers that surface event history and guest context inside AI assistants
• Custom applications combining Gatsby data with internal deal and relationship systems
• Automated guest list curation based on CRM signals and past attendance
• Post-event reporting generated from structured attendance and survey data

Not sure which integrations you need?

We’ll map your current stack and show you how data flows.

Book a demoGet support