Integration
Connect Event Tickets and Vitally
When New Order fires in Event Tickets, your agent runs Create Task in Vitally, or Customer Created in Vitally to Find Tickets and RSVPs in Event Tickets. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Event Tickets and Vitally to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Event Tickets and Vitally can do together
From Event Tickets to Vitally
When New Order in Event Tickets
then Create Task in Vitally
When Updated Attendees in Event Tickets
then Update Customer Traits in Vitally
From Vitally to Event Tickets
When Customer Created in Vitally
then Find Tickets and RSVPs in Event Tickets
When Custom Object Instance Created in Vitally
then Get ticket in Event Tickets
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Event Tickets and Vitally
Triggers and actions 12 triggers · 23 actions
Trigger
AttendeesTriggers when a new attendee is registered for a ticket or RSVP on your events.
Trigger
Check InTriggers when an attendee is checked in to an event.
Trigger
New OrderTriggers when a new ticket order is placed, returning the order's attendee record (one per order).
Trigger
Updated AttendeesTriggers when an attendee is added or any of an attendee's details change, such as check-in status.
Action
Find AttendeesFinds ticket attendees by name, email, event, ticket, order status, check-in status and more.
Action
Find Tickets and RSVPsSearches the tickets and RSVPs on your site by text, optionally limited to an event, provider or availability.
Action
Get attendeeReturns a single attendee by ID, including their ticket, event and check-in status.
Action
Get ticketReturns a single ticket or RSVP by its ID, including its event, price, capacity and availability.
Trigger
Customer CreatedTriggers when a new account (customer) is created in Vitally.
Trigger
Custom Object Instance CreatedTriggers when a new instance of a custom object is created.
Trigger
Custom Object Instance UpdatedTriggers when an instance of a custom object is created or updated.
Trigger
Note CreatedTriggers when a new note is created in Vitally.
Trigger
NPS Response CreatedTriggers when a new NPS response is recorded in Vitally.
Trigger
Organization CreatedTriggers when a new organization is created in Vitally.
Trigger
Project CreatedTriggers when a new project is created in Vitally.
Trigger
Task CreatedTriggers when a new task is created in Vitally.
Action
Create AccountCreates an account (customer) in Vitally, identified by your own external ID.
Action
Create NoteCreates a note on an account or organization in Vitally.
Action
Create NPS ResponseRecords an NPS survey response from a user in Vitally.
Action
Create OrganizationCreates an organization in Vitally, identified by your own external ID.
Action
Create Project From TemplateCreates a project for an account or organization from a project template.
Action
Create TaskCreates a task on an account or organization in Vitally.
Action
Find a CustomerReturns a account by its Vitally ID or external ID.
Action
Find a Custom Object InstanceFinds a custom object instance by ID, external ID, linked account or a custom field value.
Action
Find a NoteReturns a note by its Vitally ID or external ID.
Action
Find a OrganizationReturns a organization by its Vitally ID or external ID.
Action
Find a TaskReturns a task by its Vitally ID or external ID.
Action
Find a TeammateFinds a Vitally team member by email address.
Action
Find a UserFinds a user by email address, external ID or email domain.
Action
Get Account Health ScoresReturns an account's health score and its breakdown.
Action
Update Customer TraitsUpdates the name or traits of a account in Vitally; traits are merged with existing ones.
Action
Update Organization TraitsUpdates the name or traits of a organization in Vitally; traits are merged with existing ones.
Action
Update Project StatusChanges a project's status in Vitally.
Action
Update TaskUpdates a task in Vitally, for example to reassign or complete it.
Action
Update User TraitsUpdates the name or traits of a user in Vitally; traits are merged with existing ones.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Event Tickets
Event Tickets to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Event Tickets to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Event Tickets to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Event Tickets to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Event Tickets to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Event Tickets to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Vitally
HubSpot to VitallyHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to VitallySalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to VitallySlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to VitallyGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to VitallyGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to VitallyGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Event Tickets and Vitally, answered
What can start an automation from Event Tickets?
Any of Event Tickets's 4 triggers in the catalog, including New Order, Updated Attendees, Attendees and Check In. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Vitally when something happens in Event Tickets?
Any of Vitally's 19 actions, including Create Account, Create Note, Create NPS Response and Create Organization. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Vitally to Event Tickets?
Yes. When something happens in Vitally, your agent can act in Event Tickets too. This page covers both directions: Vitally's triggers and Event Tickets's actions are listed here as well.
Do I have to build a connector for Event Tickets or Vitally?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use Event Tickets and Vitally without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.