Using Hi.Events with Claude and ChatGPT
You can connect Hi.Events to an AI assistant such as Claude or ChatGPT and ask it to do things in your account: “How many tickets did we sell last week?”, “Find Dave Okafor and resend their ticket”, “Add Tuesday and Thursday classes through to March”. The assistant reads your events, orders and attendees, and can make changes for you, with the same access you have in Hi.Events.
There’s nothing to install. You add Hi.Events once in your assistant’s settings, sign in to approve it, and from then on it’s there in every chat.
What You Can Ask
Ask in plain English. Some examples:
| You ask | What happens |
|---|---|
| ”Look up attendee Dave at the conference and resend their ticket” | Finds every Dave on the event, asks which one if there’s more than one, and emails the ticket again to the address already on their order |
| ”How many tickets did we sell last week?” | Totals tickets, orders and sales across your events, and can break them down by event or by day |
| ”Give me a report on last weekend’s events” | Runs the same reports as the Reports page: sales by ticket, promo code use, check-ins and more |
| ”Who still hasn’t paid for their bank transfer orders?” | Lists the orders awaiting offline payment, with the buyer and amount |
| ”Check in Aoife Byrne for tonight” | Checks them in on the event’s check-in list, as door staff would |
| ”Add Tuesday and Thursday 7am classes for the next 12 weeks, 20 places each” | Generates the dates on a recurring event |
| ”Make a code for 15% off, 50 uses, ending Sunday at midnight” | Creates the promo code on the event |
| ”Add a dietary requirements question, with a follow-up asking about allergies” | Adds the registration question and its follow-up |
| ”Give me a Get tickets button for our website, in our brand green” | Creates a website widget and hands you the embed code |
Assistants can also combine Hi.Events with the other apps you’ve connected to them. With email connected, “find anyone in my inbox saying they didn’t get their ticket and sort them out” becomes one request.
Everything It Can Work With
- Events: list, create and edit events, set the venue, cover image and page colours, change checkout settings, and publish or unpublish
- Dates: add single dates, or generate a repeating schedule for a recurring event
- Tickets: create and edit tickets, tiered prices, add-ons, categories and shared capacity
- Promo codes and questions: create and edit promo codes and registration questions
- Lineup and schedule: add speakers or performers, stages or rooms, and schedule slots
- Attendees and orders: search and view them, add complimentary attendees, check people in, and resend tickets and order confirmations
- Sales and reports: totals for an event or across an organizer, and every report on the Reports page
- Your website: create widgets and get their embed code
What It Can’t Do
Some things stay in the Hi.Events dashboard, so an assistant can’t do them even with full access:
- Refund, cancel or mark orders as paid
- Message attendees, other than resending a ticket or order confirmation they already have
- Change an attendee’s or buyer’s email address
- Touch payouts, Stripe, payment settings, your team, or your account and security settings
- Add attendees to seated tickets
Connecting Claude
You need a Claude account. Adding your own connectors may need a paid Claude plan.
- In Hi.Events, click your profile icon, choose My Profile, then click API keys. Copy the address under Connected apps
- In Claude, open Settings, then Connectors
- Click Add custom connector, name it “Hi.Events” and paste the address
- Click Connect. Claude opens a Hi.Events page to approve it (see Approving the Connection)
Once it’s connected, mention your events in any chat and Claude uses Hi.Events when it needs to.
Connecting ChatGPT
You need a ChatGPT plan that allows custom apps, and you may need to turn on developer mode in ChatGPT’s settings first.
- Copy the address under Connected apps in Hi.Events, as in step 1 above
- In ChatGPT, open Settings, then Apps, and create a new app
- Name it “Hi.Events”, paste the address, and choose OAuth for authentication. This is the option that has you sign in to Hi.Events
- ChatGPT opens a Hi.Events page to approve it
The menus in Claude and ChatGPT change from time to time. If a label above doesn’t match, look for Connectors or Apps in your assistant’s settings.
Other AI Tools
Any AI tool that supports MCP, the standard Claude and ChatGPT use for connectors, can connect the same way, including Claude Code, Cursor and VS Code. Give it the address from Connected apps. If a tool asks for a header instead of opening a sign-in page, create an API key and enter it as Authorization: Bearer hie_your_key, with your key in place of hie_your_key.
Approving the Connection
When you connect, Hi.Events opens a Connect page. Sign in if you need to, then check what it says:
- Returns you to shows where you’ll be sent after approving. Claude and ChatGPT show a green Verified badge. For anything else, only continue if you started connecting it yourself
- Access: choose Read and write to let the assistant create and change things, or Read only to let it look but change nothing. Viewers can only choose Read only
- Confirm it’s you with your Current password (or sign in again if you use single sign-on), then click Connect
Your email address needs to be confirmed before you can connect an app. Hi.Events emails you every time an app is connected to your account.
What the Assistant Can See
The assistant acts as you. It has your role and your event access, never more:
- If you can only see certain organizers or events, so can the assistant
- If you can’t see financials, it gets ticket counts but no revenue, and can’t run money reports
- If you connected it as Read only, it can’t change anything. Your assistant isn’t even given the options for making changes
What you type and what the assistant reads from Hi.Events, including attendee names and emails, goes to the AI company you’re using, under their terms. Use Read only if you only want answers, and think about your attendees’ privacy before pasting their details into a chat.
Built-In Limits
These limits apply whatever the assistant is asked to do:
- A ticket or order confirmation can be resent at most once every 10 minutes, and only to the email address already on record
- One email address gets at most 5 emails from the assistant every 10 minutes, even across several attendees
- The assistant can make up to 60 changes a minute. Setting up a whole event from scratch takes about 35
Anything it does goes through the same checks as the dashboard, so it can’t oversell a ticket or publish without a confirmed email address.
Managing Connected Apps
Every app you’ve connected is listed under Connected apps on the API keys page, with its access, when you connected it and when it was Last active. Click the bin icon to Disconnect it. It stops working straight away.
Connections also stop working when:
- The app hasn’t been used for 90 days. Connect it again to carry on
- Your password is reset through Forgot password, or you’re removed from the account
You can connect up to 25 apps per account.
Tips
- Start with Read only while you get a feel for it. You can disconnect and connect again with Read and write at any time
- Name the event in your request (“for Saltwater Sound”) when you run several at once, so the assistant doesn’t have to guess
- For anything with a lot of changes, ask the assistant to tell you its plan before it starts
- Check money figures that matter against the Reports page before you send them on. The assistant reads the same numbers, but it can still misread a question
- If something goes wrong, email [email protected] and tell us what you asked and what the assistant did
Last updated