Integration
Connect Clientify and Heropa
When New Contact fires in Clientify, your agent runs Create Event in Heropa, or New Course in Heropa to Add task in Clientify. 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 Clientify 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 Clientify and Heropa can do together
From Clientify to Heropa
When New Contact in Clientify
then Create Event in Heropa
When New Deal in Clientify
then Create User in Heropa
From Heropa to Clientify
When New Course in Heropa
then Add task in Clientify
When New Event Scheduled in Heropa
then Create Contact in Clientify
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 Clientify and Heropa
Triggers and actions 5 triggers · 46 actions
Trigger
New ContactTriggers when a new contact is created in Clientify.
Trigger
New DealTriggers when a new deal is created in Clientify.
Trigger
New TaskTriggers when a new task is created in Clientify.
Action
Add companyCreates a company in Clientify with its contact details, address, tags and custom field values.
Action
Add taskCreates a task in Clientify, optionally assigned to a user and linked to contacts, companies and deals.
Action
Create Abandoned CartCreates an abandoned shopping cart for a Clientify contact, with the cart's items, shop and currency.
Action
Create ContactCreates a contact in Clientify. If a contact with the same email or phone already exists it is updated instead, unless forced insert is turned on.
Action
Create DealCreates a deal in Clientify, optionally linked to a contact and company and placed in a pipeline stage.
Action
Create OrderCreates an order in Clientify for a contact, with its line items.
Action
Delete contactDeletes a contact from Clientify.
Action
Find ContactFinds contacts by name, surname or email, optionally narrowed by phone, source, type or dates, and returns the matches.
Action
Get companyReturns the full details of a Clientify company by its id, including contact info, tags, custom fields and employees.
Action
Get contactReturns a Clientify contact's full details, including emails, phones, addresses, tags and custom fields.
Action
Get dealReturns a Clientify deal by its id, including amount, stage, pipeline, involved contacts and companies, tasks and custom fields.
Action
List contactsReturns the contacts in your Clientify account, optionally filtered by name/email, phone, source, type, or created/modified dates.
Action
Update companyUpdates an existing company in Clientify and returns the updated record.
Action
Update contactUpdates an existing Clientify contact's name, title, company, status and notes. Fields left blank keep their current values.
Action
Update dealUpdates an existing Clientify deal, changing only the fields you fill in.
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 Clientify
Clientify to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Clientify to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Clientify to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Clientify to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Clientify to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Clientify 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
Clientify and Heropa, answered
What can start an automation from Clientify?
Any of Clientify's 3 triggers in the catalog, including New Contact, New Deal and New Task. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Heropa when something happens in Clientify?
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 Clientify?
Yes. When something happens in Heropa, your agent can act in Clientify too. This page covers both directions: Heropa's triggers and Clientify's actions are listed here as well.
Do I have to build a connector for Clientify 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 Clientify 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.