Integration
Connect Enchant and Heropa
When New Customer fires in Enchant, your agent runs Create Event in Heropa, or New Course in Heropa to Add Labels to Ticket in Enchant. 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 Enchant and Heropa 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 Enchant and Heropa can do together
From Enchant to Heropa
When New Customer in Enchant
then Create Event in Heropa
When New or Updated Ticket in Enchant
then Create User in Heropa
From Heropa to Enchant
When New Course in Heropa
then Add Labels to Ticket in Enchant
When New Event Scheduled in Heropa
then Create Contact in Enchant
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 Enchant and Heropa
Triggers and actions 5 triggers · 48 actions
Trigger
New CustomerTriggers when a new customer is added to the help desk.
Trigger
New or Updated TicketTriggers when a ticket is created or changes (new message, state, assignee, labels).
Trigger
New Ticket CreatedTriggers when a new ticket is created, optionally only in the inboxes you choose.
Action
Add Labels to TicketAdds one or more labels to a ticket, keeping its existing labels.
Action
Create AttachmentUploads a file as an attachment so its id can be added to a note or reply.
Action
Create ContactAdds an email address, phone number or Twitter handle to a customer.
Action
Create CustomerCreates a customer in your Enchant help desk, optionally with an email address.
Action
Create TicketCreates an email ticket for a customer, matched or created by email, with the customer's first message.
Action
Delete ContactDeletes one contact (email, phone or Twitter handle) from a customer.
Action
Find Customer by EmailFinds the customer with a given email address.
Action
Get AttachmentReturns an attachment's file name, MIME type and size.
Action
Get CustomerReturns one customer with their name, summary and contacts.
Action
Get TicketReturns one ticket by its id.
Action
List customersReturns customers from your Enchant help desk, optionally filtered by contact or creation date.
Action
List messagesReturns all replies and notes on a ticket, oldest to newest as Enchant lists them.
Action
List TicketsReturns up to 100 tickets, newest first, optionally filtered by state, inbox or assigned user.
Action
List UsersReturns the help desk's users (agents) with their names and email addresses.
Action
Remove Labels from TicketRemoves one or more labels from a ticket.
Action
Update CustomerUpdates a customer's name or summary. Only the fields you fill in change.
Action
Update TicketUpdates a ticket's state, assigned user, inbox or subject. Only the fields you fill in change.
Trigger
New CourseTriggers when a new course is created in Heropa.
Trigger
New Event ScheduledTriggers when a new event is created in Heropa.
Action
Add environmentCreates a lab environment for a user from a template, either standard or backed by a dedicated cloud account pool.
Action
Archive courseArchives a course so it is hidden from all views and no longer accepts new enrollments. Returns the archived course.
Action
Assign an event host seat to a userAssigns a user to a host seat on an event and returns the event.
Action
Assign an Event Seat to a UserAssigns a seat in a Heropa event to a user, identified by id, external id or name and email.
Action
Create EventCreates a scheduled Heropa event (a hosted lab session) with its participant templates.
Action
Create UserCreates a Heropa user, optionally enrolling them in a course.
Action
Delete courseDeletes a single course from Heropa.
Action
Delete eventDeletes an event, optionally also deleting its environments and participants.
Action
Delete userDeletes a user from your Heropa account.
Action
Enroll a User in a CourseEnrolls an existing Heropa user in a course and returns their workspace link.
Action
Find Course by External IdFinds a Heropa course by its external id.
Action
Find Event by External IdFinds a Heropa event by its external id.
Action
Find Template by External IdFinds a Heropa template by its external id.
Action
Find users by name or emailReturns the users whose email, first name, last name or username contains the search text.
Action
Get CourseReturns one Heropa course by its id.
Action
Get environmentReturns the details of a single Heropa environment, including its state, owner, course, event and workspace URL.
Action
Get templateReturns the details of a single Heropa template, including its title, code, labels, region and virtual machines.
Action
Get UserReturns one Heropa user by their id.
Action
Get User by Email AddressReturns the Heropa user with the given email address.
Action
Invite userInvites a person to Heropa by email, optionally assigning a manager and enrolling them in a course. Returns the new user and their access token.
Action
Launch environmentLaunches a Heropa environment that has not been provisioned yet. Provisioning continues in the background after the launch is accepted.
Action
List coursesReturns the courses in your Heropa account, optionally filtered by name. Archived courses are not included.
Action
List environmentsReturns the environments in your Heropa account, optionally filtered by owner, event, region, company or persistence.
Action
List eventsReturns all events in your Heropa company, with their names, times, hosts and codes.
Action
List templatesReturns the templates in your Heropa company, optionally filtered by name.
Action
List usersReturns the users in your Heropa company, optionally filtered by role or email address.
Action
Start eventStarts a Heropa event, optionally launching its environments that have not been provisioned yet.
Action
Unassign Event SeatsRemoves the users from the given seats of a Heropa event.
Action
Update courseUpdates an existing Heropa course's name, description, template, policy, owner, content, thumbnail, code or usage type.
Action
Update EventUpdates the settings of an existing Heropa event; only the fields you supply change.
Action
Update userUpdates an existing Heropa user's name, email, password, manager, company, role or custom properties.
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 Enchant
Enchant to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Enchant to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Enchant to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Enchant to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Enchant to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Enchant to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Heropa
Google Sheets to HeropaGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to HeropaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to HeropaGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to HeropaGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to HeropaActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to HeropaOrganize anything with Airtable, a modern database created for everyone.
Questions
Enchant and Heropa, answered
What can start an automation from Enchant?
Any of Enchant's 3 triggers in the catalog, including New Customer, New or Updated Ticket and New Ticket Created. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Heropa when something happens in Enchant?
Any of Heropa's 31 actions, including Create Event, Create User, Update course and Update Event. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Heropa to Enchant?
Yes. When something happens in Heropa, your agent can act in Enchant too. This page covers both directions: Heropa's triggers and Enchant's actions are listed here as well.
Do I have to build a connector for Enchant or Heropa?
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 Enchant and Heropa 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.