Onboarding Guide

Get started with Happenings Backoffice

Connect Claude to your Happenings pages to manage events, tickets, members, and analytics through natural conversation.

Overview

To use the Happenings Backoffice connector you need three things in place, in this order:

1. Claude.ai account→

2. Happenings Backoffice connector→

3. Authorize your pages→

Ready to use

The entire setup takes about 5 minutes. You only need to do it once per user.

How does it work?

When you ask Claude a question about your events or pages, Claude calls the Happenings Backoffice connector which fetches live data from the Happenings backend. Responses are always based on real-time data from your account.

You→

Claude.ai→

Happenings Backoffice→

Happenings data

Create a Claude.ai account

Go to claude.ai and click Sign up (or use Google login).

Create the account with your work email.

Confirm your email via the link Claude sends to your inbox.

Which plan? Start with Claude Pro. It gives you plenty of capacity for daily use of the backoffice connector.

Add the Happenings Backoffice connector

The connector is the link between Claude and your Happenings data. It must be added before you can use any of the tools.

In Claude.ai, click Customize in the left sidebar, then select Connectors.

Click the plus icon (+) in the top right, then choose Add custom connector.

Enter the URL:

https://api.happenings.social/mcp

Set the name to Happenings Backoffice.

Click Add / Save.

Important: the connector must be named exactly "Happenings Backoffice". If the name is different, skills that reference the connector by name will not be able to call its tools.

First-time authorization

The first time Claude uses the connector, you will need to log in with your Happenings account and grant access to specific pages.

Open a new conversation in Claude.ai (click New chat).

Click the tools icon at the bottom of the chat box and enable Happenings Backoffice.

Send a test message, e.g. "show me my pages".

A login window will appear from Happenings. Sign in with your Happenings account.

Select which pages Claude should have access to, then confirm.

Enable connector→

First message→

Connected

Login happens once per user. After that, Claude stores a bearer token so you will not need to log in again until the token expires or is revoked.

Test that everything works

Open a new conversation and try some of these:

“Show me upcoming events for my page”

“How are ticket sales going for my next event?”

“Give me a membership growth review”

If Claude responds with live data from your Happenings account, you are all set.

Troubleshooting

Connector shows as offline

Check that the URL is entered correctly and that you are signed in to Claude.ai.

Claude cannot call tools

Confirm the connector is named exactly "Happenings Backoffice". Rename it via Customize → Connectors if needed.

Try disabling and re-enabling Happenings Backoffice in the tools menu, or start a new conversation.

Available scopes

During authorization, you grant access to specific capabilities. Read scopes allow Claude to view data; propose scopes allow Claude to suggest changes that you review before applying.

Scope	Description
`pages:read`	View your pages and settings
`events:read`	View events and event details
`tickets:read`	View ticket types and check-in stats
`orders:read`	View recent orders and sales summaries
`members:read`	View members and membership plans
`analytics:read`	View page analytics and insights
`tasks:read`	View page tasks and assignees
`events:propose`	Propose event changes (create, update, publish)
`tickets:propose`	Propose ticket type changes
`commerce:propose`	Propose commerce changes (coupons, refunds)
`members:propose`	Propose member changes (roles, titles)
`tasks:propose`	Propose task changes (create, assign, complete)
`page_profile:propose`	Propose page profile updates
`page_settings:propose`	Propose page settings and automation updates
`communications:propose`	Propose notifications and announcements
`support:propose`	Propose support ticket updates
`team:propose`	Propose team role changes
`finance:propose`	Propose finance changes (refunds, payouts, bank accounts, fees)
`media:propose`	Propose page media assignments
`page_admin:propose`	Propose admin page metadata updates

Built-in prompts

Claude automatically discovers the available tools when it connects. Tools cover reading page overviews, listing events, checking sales, viewing membership stats, and proposing changes. All propose tools generate a diff that you review before anything is applied.

page_operator_briefing—Full overview of a page's current state

event_readiness_review—Pre-event checklist for an upcoming event

sales_health_check—Revenue and ticket sales analysis

membership_growth_review—Membership growth and retention review

Security

OAuth 2.0 with PKCE — your credentials are never shared with Claude.

Access is scoped to the specific pages you authorize. Claude cannot see pages you haven't granted access to.

You can revoke access at any time from your account settings.

Propose tools never make changes directly — they generate a diff for your review.