Integration
Connect COR and Heropa
When Create Brand fires in COR, your agent runs Create Event in Heropa, or New Course in Heropa to Create Invoice in COR. 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 COR 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 COR and Heropa can do together
From COR to Heropa
When Create Brand in COR
then Create Event in Heropa
When Create Client in COR
then Create User in Heropa
From Heropa to COR
When New Course in Heropa
then Create Invoice in COR
When New Event Scheduled in Heropa
then Create Task in COR
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 COR and Heropa
Triggers and actions 14 triggers · 56 actions
Trigger
Create BrandTriggers when a new brand is created in COR.
Trigger
Create ClientTriggers when a new client is created in COR.
Trigger
Create HourTriggers when a new time entry is logged in COR.
Trigger
Create InvoiceTriggers when a new transaction is recorded in COR. COR has no separate invoice record, so this watches all transactions, invoices included; use the type field to tell them apart.
Trigger
Create ProductTriggers when a new product is created in COR.
Trigger
Create ProjectTriggers when a new project is created in COR.
Trigger
Create TaskTriggers when a new task is created in COR. Returns the new task's details.
Trigger
Create UserTriggers when a new user is created in COR.
Trigger
Updated ClientTriggers when an existing client is changed in COR.
Trigger
Updated ProjectTriggers when an existing project is updated in COR.
Trigger
Updated TaskTriggers when a task is changed, such as a new title, status, priority or deadline. Also fires when a new task appears.
Trigger
Updated UserTriggers when a user in COR is created or changed, such as their name, email, role, position or labels.
Action
Add brandCreates a new brand under a client in COR.
Action
Add teamCreates a new team in COR with a name and, optionally, a description and workspace. Returns the team that was created.
Action
Create ClientCreates a new client in COR with its company details and primary contact, and returns the new client's id.
Action
Create FeeCreates a fee for a client in COR, with its name, estimate and work order, and optional details such as dates, status and currency. Returns the new fee.
Action
Create HourLogs a time entry against a task in COR and returns the new entry's id.
Action
Create InvoiceCreates an invoice (a COR transaction) for the given date, total and currency, optionally linked to a client, and returns the new transaction.
Action
Create ProjectCreates a new project for a client in COR and returns the created project.
Action
Create TaskCreates a new task in COR, optionally within a project, and returns the created task.
Action
Delete ProjectDeletes a project in COR by its ID.
Action
Delete taskDeletes a task in COR by its ID.
Action
Find clients by nameReturns the clients whose name matches the specified name.
Action
Find projects by nameReturns the COR projects whose name matches the name you search for, including each project's client, project manager, status and budget details.
Action
Get clientReturns a single COR client by its id, including its business name, contact details, website and description.
Action
Get projectReturns a single COR project by its id, including its client, project manager, dates, status, budget figures and assigned labels. An error occurs if the project is not found.
Action
Get taskReturns a single COR task by its id, including its title, project, deadline, status and priority.
Action
List clientsReturns all clients in the COR account, optionally narrowed by filter criteria.
Action
List feesReturns the fees in the COR account, including each fee's name, estimate, status and dates.
Action
List hoursReturns the time entries logged in the COR account, optionally narrowed by date range, client, project, user, label or team, and sorted as you choose.
Action
List productsReturns all products in the COR account, each with its name, client and brand.
Action
List projectsReturns the company's projects, optionally narrowed by client, team, user, brand, product, dates, status, health or archived state.
Action
List tasksReturns the tasks in your COR account, optionally narrowed by project, project manager, status and other criteria, and sorted the way you choose.
Action
List teamsReturns the teams in the COR workspace, including each team's name and description.
Action
Update ClientUpdates an existing client's name, business details and contact information, and returns the updated client.
Action
Update ProjectUpdates an existing project in COR, changing only the fields you fill in, and returns the updated project.
Action
Update TaskUpdates an existing task by its id, changing its title, project, description, deadline, status, priority or archived state, and returns the updated task.
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 COR
COR to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
COR to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
COR to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
COR to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
COR to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
COR 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
COR and Heropa, answered
What can start an automation from COR?
Any of COR's 12 triggers in the catalog, including Create Brand, Create Client, Create Hour and Create Invoice. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Heropa when something happens in COR?
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 COR?
Yes. When something happens in Heropa, your agent can act in COR too. This page covers both directions: Heropa's triggers and COR's actions are listed here as well.
Do I have to build a connector for COR 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 COR 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.