Integration
Connect Eventcube to Pylon
When Event Created fires in Eventcube, your agent runs Add internal note to issue in Pylon. 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 Eventcube and Pylon 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 Eventcube can start in Pylon
When Event Created in Eventcube
then Add internal note to issue in Pylon
When Event Updated in Eventcube
then Add task in Pylon
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 Eventcube and Pylon
Triggers and actions 7 triggers · 94 actions
Trigger
Event CreatedTriggers when a new event is created in the Eventcube store.
Trigger
Event UpdatedTriggers when an event in the Eventcube store is created or changed.
Trigger
Order CreatedTriggers when a new order is placed.
Trigger
Order UpdatedTriggers when an order is created or changed.
Trigger
Promoter CreatedTriggers when a new promoter is added.
Trigger
Ticket CreatedTriggers when a new ticket type is added to an event.
Trigger
Ticket UpdatedTriggers when a ticket type of an event is created or changed.
Action
Add Cart ItemAdds tickets to a cart, increasing an existing line or creating a new one.
Action
Apply Cart Discount CodeApplies a discount code to a cart.
Action
Create ArtistCreates an artist in the Eventcube store.
Action
Create CategoryCreates an event category.
Action
Create Checkout FieldCreates a custom checkout field.
Action
Create DeviceCreates a scanner or POS device.
Action
Create Device PINCreates a PIN for a device.
Action
Create DiscountCreates a discount with its scope and code type.
Action
Create EventCreates an event.
Action
Create OrderConverts a cart into an order.
Action
Create PromoterCreates a promoter.
Action
Create TicketAdds a ticket type to an event.
Action
Create VenueCreates a venue.
Action
Delete CategoryDeletes an event category.
Action
Delete Checkout FieldDeletes a custom checkout field.
Action
Delete DeviceDeletes a scanner or POS device.
Action
Delete Device PINDeletes a device PIN.
Action
Delete DiscountDeletes a discount.
Action
Delete EventDeletes an event.
Action
Delete PromoterDeletes a promoter.
Action
Delete TicketDeletes a ticket type from an event.
Action
Delete VenueDeletes a venue.
Action
Get ArtistReturns one artist by ID.
Action
Get CartReturns one cart by ID or token.
Action
Get Cart Seat SelectionsReturns the seat selections saved on a cart's seated lines.
Action
Get CategoryReturns one event category by ID.
Action
Get Checkout FieldReturns one custom checkout field.
Action
Get DeviceReturns one device by ID.
Action
Get Device PINReturns one device PIN.
Action
Get DiscountReturns one discount by ID.
Action
Get EventReturns one event by ID.
Action
Get OrderReturns one order by ID or reference.
Action
Get PromoterReturns one promoter by ID.
Action
Get TicketReturns one ticket type of an event.
Action
Get VenueReturns one venue by ID.
Action
List ArtistsReturns a page of the store's artists.
Action
List CartsReturns a page of carts.
Action
List CategoriesReturns a page of event categories.
Action
List Checkout FieldsReturns the store's custom checkout fields.
Action
List Device PINsReturns a page of a device's PINs.
Action
List DevicesReturns a page of scanner and POS devices.
Action
List Discount CodesReturns a page of a discount's promo codes.
Action
List DiscountsReturns a page of discounts.
Action
List EventsReturns a page of events ordered by start date, optionally filtered.
Action
List OrdersReturns a page of orders, optionally for one event.
Action
List PromotersReturns a page of promoters.
Action
List TicketsReturns an event's ticket types with live availability.
Action
List VenuesReturns a page of venues.
Action
Remove Cart Discount CodeRemoves the discount code from a cart.
Action
Remove Cart ItemRemoves one ticket line from a cart.
Action
Set Cart Item QuantitySets the quantity and ticket holders of one cart line.
Action
Update ArtistUpdates an artist's title.
Action
Update CartUpdates a cart's items, customer details, expiry or custom field values.
Action
Update Cart Seat SelectionsSaves seat labels for a cart's seated lines.
Action
Update CategoryUpdates an event category.
Action
Update Checkout FieldUpdates a custom checkout field.
Action
Update DeviceUpdates a scanner or POS device.
Action
Update Device PINUpdates a device PIN.
Action
Update DiscountUpdates a discount.
Action
Update EventUpdates an event.
Action
Update Order Ticket ItemUpdates the status, seat or revocation reason of one issued ticket.
Action
Update Order Ticket NamesSets ticket holder names on an order's tickets.
Action
Update PromoterUpdates a promoter.
Action
Update TicketUpdates a ticket type of an event.
Action
Update VenueUpdates a venue.
Action
Validate BarcodeChecks whether a ticket barcode belongs to a valid order.
Action
Add internal note to issueAdds an internal note to a Pylon issue. Internal notes are not visible to the requester.
Action
Add tagCreates a new tag in Pylon that can be applied to accounts, articles or issues.
Action
Add taskCreates a task in Pylon with a title and optional details such as assignee, due date, account, project and status. Returns the new task.
Action
Create AccountCreates a new customer account in Pylon with its name, domains, owner, tags and other details.
Action
Create Account ActivityCreates a custom activity on a Pylon account's timeline.
Action
Create Call RecordingCreates a call recording in Pylon from your own call recorder, including its transcript, and returns the new recording. Requires the Custom Call Recorder integration to be enabled in Pylon.
Action
Create ContactCreates a new contact in Pylon with a name and optional email, account, phone numbers and portal role.
Action
Create IssueCreates a new issue in Pylon with its first message, either as an internal note or delivered to the customer over a channel you choose. Returns the created issue.
Action
Delete accountPermanently deletes a Pylon account by its ID or external ID.
Action
Delete issuePermanently deletes an issue in Pylon.
Action
Find Account by NameFinds Pylon accounts by name, by exact or partial match, returning the matching accounts.
Action
Find contacts by criteriaReturns the contacts that match the specified search text and/or filter.
Action
Find issues by criteriaReturns Pylon issues matching a text search and/or a filter on fields such as state, assignee, account, tags or dates.
Action
Get accountReturns a single Pylon account by its ID or external ID, including its domains, owner, tags, channels and custom fields.
Action
Get contactReturns a single contact, including its emails, phone numbers, account and custom field values, by its ID or external ID.
Action
Get issueReturns a single Pylon issue by its ID or issue number, including its custom field values. An error occurs if the issue is not found.
Action
Get userReturns a single Pylon team member by ID, including their name, email addresses, status, and assigned roles.
Action
Get UsersReturns the users in your Pylon organization, optionally including deactivated users.
Action
List accountsReturns all accounts in your Pylon organization, including their domains, owner, tags and custom field values.
Action
List contactsReturns all contacts in the Pylon organization, including their emails, phone numbers, account and custom field values.
Action
List issuesReturns the issues created within a time range of up to 365 days, newest first.
Action
List tagsReturns all tags in the Pylon organization, with each tag's name, color and the type of object it applies to.
Action
List teamsReturns all teams in the Pylon organization, with their members, how each team assigns issues, and any recurring assignment schedule.
Action
Reply to issueSends a customer-facing reply on a Pylon issue, continuing an existing conversation or thread. Returns the ID of the new message and its issue.
Action
Update AccountUpdates an existing Pylon account. Only the fields you fill in are changed.
Action
Update contactUpdates an existing Pylon contact by its ID or external ID. Only the fields you fill in are changed.
Action
Update issueUpdates an existing Pylon issue — its title, state, assignee, team, account, requester, tags, type, portal visibility and custom fields. Only the fields you fill in are changed.
Action
Update Issue FollowersAdds or removes users and contacts as followers of a Pylon issue, and returns the issue's resulting followers.
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 Eventcube
Eventcube to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Eventcube to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Eventcube to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Eventcube to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Eventcube to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Eventcube to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Pylon
HubSpot to PylonHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to PylonSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to PylonSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to PylonGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to PylonGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PylonGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Eventcube and Pylon, answered
What can start an automation from Eventcube?
Any of Eventcube's 7 triggers in the catalog, including Event Created, Event Updated, Order Created and Order Updated. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Pylon when something happens in Eventcube?
Any of Pylon's 28 actions, including Create Account, Create Account Activity, Create Call Recording and Create Contact. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Pylon to Eventcube?
Pylon has no triggers in the catalog today, so automations start in Eventcube. If you need the other direction, ask: your agent reads Pylon's API documentation and adds it.
Do I have to build a connector for Eventcube or Pylon?
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 Eventcube and Pylon 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.