Integration
Connect Heropa and Qomon
When New Course fires in Heropa, your agent runs Create Contact in Qomon, or Contact Updated (Source: Any) in Qomon to Create Event in Heropa. 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 Heropa and Qomon 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 Heropa and Qomon can do together
From Heropa to Qomon
When New Course in Heropa
then Create Contact in Qomon
When New Event Scheduled in Heropa
then Create or Update Contact in Qomon
From Qomon to Heropa
When Contact Updated (Source: Any) in Qomon
then Create Event in Heropa
When New Contact Created (Source: Any) in Qomon
then Create User in Heropa
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 Heropa and Qomon
Triggers and actions 6 triggers · 52 actions
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.
Trigger
Contact Updated (Source: Any)Triggers when a Qomon contact is created or updated, from any source.
Trigger
New Contact Created (Source: Any)Triggers when a new contact is created in Qomon, from any source.
Trigger
New DonationTriggers when a new donation is recorded in Qomon.
Trigger
New TransactionTriggers when a new transaction is recorded in Qomon.
Action
Create ContactCreates a new contact in your Qomon space.
Action
Create NoteAdds a note to a contact, optionally pinned.
Action
Create or Update ContactCreates a contact, or updates the existing one that matches by email or external ID (processed asynchronously).
Action
Delete ContactDeletes a Qomon contact by its ID.
Action
Delete InteractionDeletes an interaction from a contact.
Action
Delete NoteDeletes a note from a contact.
Action
Get ContactReturns one Qomon contact by its ID.
Action
Get NoteReturns one note on a contact.
Action
Get TransactionReturns one transaction by its ID.
Action
Get Transaction BundleReturns one transaction bundle with its transactions, memberships and donations.
Action
Get UserReturns one user in your Qomon space by ID.
Action
List Contact InteractionsReturns every interaction (calls, emails, meetings...) logged on a contact.
Action
List Contact NotesReturns every note attached to a contact.
Action
List DonationsReturns donations, newest first, optionally filtered by creation date or contact.
Action
List MembershipsReturns memberships, newest first, optionally filtered by creation date.
Action
List TeamsReturns every team you can access.
Action
List TransactionsReturns transactions, newest first, optionally filtered by creation date.
Action
List UsersReturns the users in your Qomon space.
Action
Log Interaction (Advanced)Logs an interaction (call, email, meeting, letter, SMS or donation) on a contact.
Action
Search ContactsSearches contacts with a Qomon query (for example contacts updated since a date).
Action
Update ContactReplaces an existing Qomon contact's details; fields you leave out are cleared.
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 Heropa
Heropa to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Heropa to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Heropa to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Heropa to MailchimpMailchimp marketing automation and email platform.
Heropa to StripeStripe is a payment processing platform for online businesses.
Heropa to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
More into Qomon
HubSpot to QomonHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to QomonGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to QomonGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to QomonGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to QomonGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to QomonMailchimp marketing automation and email platform.
Questions
Heropa and Qomon, answered
What can start an automation from Heropa?
Any of Heropa's 2 triggers in the catalog, including New Course and New Event Scheduled. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Qomon when something happens in Heropa?
Any of Qomon's 21 actions, including Create Contact, Create Note, Create or Update Contact and Log Interaction (Advanced). Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Qomon to Heropa?
Yes. When something happens in Qomon, your agent can act in Heropa too. This page covers both directions: Qomon's triggers and Heropa's actions are listed here as well.
Do I have to build a connector for Heropa or Qomon?
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 Heropa and Qomon 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.