Bevy connects your community to tools your team already uses: a public API and webhooks for custom work, plus CRM, marketing automation, calendar, Slack, Meetup, and sign-on integrations.
Bevy is built so your community can work with the systems your team already runs. Some teams call Bevy from their own code. Others turn on a ready-made connection so members, events, and attendance show up in a CRM, a marketing tool, a calendar, Slack, or Meetup. Sign-on options let people use a company identity provider or a social account instead of a separate Bevy password.
Use this overview to choose a connection style, then open the how-to for that tool when you are ready to connect. For the rest of the platform, see Bevy introduction.
What this is for
- See which connection styles Bevy offers before you pick a how-to.
- Match a question (CRM, marketing, calendar, Slack, custom code, sign-on) to the right starting article.
- Know where connect and setup steps live — they are in the linked how-tos, not on this page.
How the landscape fits together
| Area | What it is for | Start here |
|---|---|---|
| Developer tools | Call Bevy yourself, or receive a push when something changes. | Using public Bevy APIs; Introduction to webhooks in Bevy; Choose the public API or webhooks |
| CRM | Keep Salesforce or HubSpot current with community activity. | Salesforce integration - Introduction; HubSpot integration - Connect Bevy to HubSpot |
| Marketing automation | Send community activity into Marketo or Eloqua. | Marketo integration - Introduction; Eloqua integration - Introduction |
| Calendar and messaging | Put events on Google Calendar, or surface them in Slack. | Google Calendar integration - Introduction; Slack integration - Introduction |
| Sign-on | Let people sign in with your identity provider or a social account. | Introduction to single sign-on; Introduction to social sign-on |
| Meetup | Publish chapter events to Meetup Pro when that product is in use. | Meetup Pro integration |
Note: Which cards and connections appear for your community depends on what Bevy has enabled. If a card is missing, ask your Customer Success Manager.
Developer tools
Use the public API when your system needs to ask Bevy for data, or make a change, on its own schedule. Use webhooks when Bevy should tell your system that something just changed. Many teams use both.
- Using public Bevy APIs — what the public API is for, and how teams typically start.
- Introduction to webhooks in Bevy — how a push from Bevy works at a high level.
- Choose the public API or webhooks — when to pull, when to receive a push, and when to combine them.
- About the Community Assistant (MCP) — connect an AI assistant your team already uses so it can look up Bevy data or take action with that person's permissions. That product is separate from the public API and webhooks.
CRM
CRM integrations send selected community records into Salesforce or HubSpot so sales and success teams see members and event activity where they already work. Sync is one-way from Bevy into the CRM unless a how-to says otherwise.
- Salesforce integration - Introduction — what syncs, and which connection path your community uses.
- HubSpot integration - Connect Bevy to HubSpot — turn on the HubSpot connection and map fields.
Marketing automation
Marketing automation integrations send community activity into Marketo or Eloqua so campaigns and lead programs can use chapter and event data.
- Marketo integration - Introduction — what the Marketo connection covers.
- Eloqua integration - Introduction — what the Eloqua connection covers.
Calendar and messaging
Calendar and messaging integrations help people find Bevy events in tools they already open every day.
- Google Calendar integration - Introduction — how Bevy events can appear on Google Calendar.
- Slack integration - Introduction — how Bevy can surface community events in Slack.
Sign-on
Sign-on integrations change how people enter the community site. Single sign-on uses your organization's identity provider. Social sign-on lets people use a Google, LinkedIn, Facebook, or X account.
- Introduction to single sign-on — when SSO fits, and how it differs from a Bevy-only password.
- Introduction to social sign-on — when social sign-on fits, and which providers Bevy supports.
Meetup and other services
Some communities also publish chapter events to Meetup Pro, or connect tracking and partner tools such as analytics pixels or partner platforms. Those jobs have their own how-tos.
- Meetup Pro integration — connect a chapter to Meetup and keep events in sync when Meetup Pro is in use.
Where to go next
- Choose the public API or webhooks — decide between pull and push for a custom integration.
- Salesforce integration - Introduction or HubSpot integration - Connect Bevy to HubSpot — CRM sync.
- Marketo integration - Introduction or Eloqua integration - Introduction — marketing automation.
- Google Calendar integration - Introduction or Slack integration - Introduction — calendar and messaging.
- Introduction to single sign-on or Introduction to social sign-on — how members sign in.
- Bevy introduction — how the rest of the products fit together.