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 the contacts, events, and guest list data Gatsby captures. Gatsby also has a first-party MCP server for AI-powered workflows on top of the same data.

Integrations

Your CRM, connected

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

Affinity

Build guest lists from Affinity contacts and push RSVP status, attendance, and event history 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

Not a native integration. Event activity flows through Google account sync, and webhooks push structured attendance data through Zapier or Make 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 — limited release, enabled per org — with read and write access to contacts, events, guest lists, custom fields, and webhook subscriptions. Pull guest history into your CRM, feed a BI tool, or build custom workflows. See the Gatsby API page for the current setup path and endpoint coverage.

What the API exposes

+

• Contacts, with search and event-history lookups
• Events, guest lists, and RSVP status
• Attendance records and check-in data
• Custom field values stored in contact profiles
• 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. Gatsby has a first-party MCP server — limited release, enabled per org — that lets any MCP-compatible AI tool query your contacts, events, and RSVPs in natural language. Building a custom MCP server or agent directly on the Gatsby API is also an option for teams with more specific requirements.

What teams are building

+

• The Gatsby MCP server, connected to Claude, ChatGPT, Cursor, or another MCP-compatible client, for natural-language questions over event history and guest context
• Custom MCP servers or agents built on the Gatsby API for more specialized workflows
• 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