Integration
Connect Cerca and Keplars
When Applicant Created fires in Cerca, your agent runs Add Contact to Audience in Keplars, or New Audience in Keplars to Create User in Cerca. 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 Cerca and Keplars 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 Cerca and Keplars can do together
From Cerca to Keplars
When Applicant Created in Cerca
then Add Contact to Audience in Keplars
When New Agency in Cerca
then Send Email in Keplars
From Keplars to Cerca
When New Audience in Keplars
then Create User in Cerca
When New Contact in Audience in Keplars
then Update user in Cerca
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 Cerca and Keplars
Triggers and actions 6 triggers · 38 actions
Trigger
Applicant ArchivedTriggers when a Cerca applicant is archived.
Trigger
Applicant CreatedTriggers when a new applicant (franchise candidate) is created in Cerca.
Trigger
Applicant ProgressedTriggers when a Cerca applicant moves to a different step.
Trigger
New AgencyTriggers when a new agency is added to your Cerca network.
Action
Approve userApproves a user awaiting moderation, taking them out of moderation and activating their account.
Action
Create AgencyCreates a Cerca agency (a location in the network) and returns it.
Action
Create Applicant RequestCreates an applicant request (a new franchise candidate lead) on one of your Cerca applicant sources.
Action
Create UserCreates a user in the Cerca extranet and returns it.
Action
Delete AgencyDeletes a Cerca agency.
Action
Delete userDeletes a user from your Cerca extranet.
Action
Demote applicantMoves an applicant back to the previous step of their recruitment scenario and returns the updated applicant.
Action
Find ApplicantFinds Cerca applicants whose name, email or phone matches the search text, and returns the first match.
Action
Find usersSearches users by name or email and returns the matching users.
Action
Get AgencyReturns one Cerca agency (a location in the network) by its ID.
Action
Get Current UserReturns the Cerca user the access token acts as, with their name, email and agencies.
Action
Get userReturns a single user of your Cerca extranet, including profile details, groups, agencies and custom fields.
Action
List AgenciesReturns a page of Cerca agencies, optionally filtered by a search term.
Action
List applicant scenariosReturns every applicant scenario (recruitment funnel) in the extranet, the default one first.
Action
List UsersReturns a page of users in the Cerca extranet, optionally filtered by a search term.
Action
Promote ApplicantAdvances a Cerca applicant to the next step of their recruitment scenario.
Action
Update AgencyUpdates a Cerca agency's details; only the fields you fill in are changed.
Action
Update userUpdates an existing user's profile, contact details, address, groups, agencies and custom fields. Only the fields you fill in are changed.
Trigger
New AudienceTriggers when a new audience is created.
Trigger
New Contact in AudienceTriggers when a contact is added to an audience.
Action
Add Contact to AudienceAdds a contact to an audience, reusing an existing contact with the same email.
Action
Add DomainAdds a sending domain and returns the DNS records to publish.
Action
Create AudienceCreates a new audience (contact list).
Action
Delete AudienceDeletes an audience.
Action
Delete ContactDeletes a contact.
Action
Delete DomainDeletes a sending domain.
Action
Enroll Contact in AutomationEnrolls a contact, by email, in a Keplars automation.
Action
Get AudienceReturns one audience by its ID.
Action
Get AutomationReturns one automation by its ID.
Action
Get ContactReturns one contact, looked up by ID or email.
Action
List AudiencesReturns the workspace's audiences.
Action
List AutomationsReturns the workspace's automations.
Action
List Contacts in AudienceReturns the contacts in an audience.
Action
List DomainsReturns the workspace's sending domains.
Action
Remove Contact from AutomationRemoves a contact, by email, from a Keplars automation.
Action
Schedule EmailSchedules a transactional email to be sent at a future date and time.
Action
Send EmailQueues a transactional email for delivery through Keplars.
Action
Track EventRecords a custom event for a contact, which can start event-triggered Keplars automations.
Action
Update ContactUpdates a contact's details.
Action
Verify DomainChecks a sending domain's DNS records and returns its verification result.
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 Cerca
Cerca to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Cerca to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Cerca to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Cerca to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Cerca to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Cerca to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Keplars
HubSpot to KeplarsHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to KeplarsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to KeplarsGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to KeplarsGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to KeplarsGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to KeplarsActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
Cerca and Keplars, answered
What can start an automation from Cerca?
Any of Cerca's 4 triggers in the catalog, including Applicant Created, New Agency, Applicant Progressed and Applicant Archived. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Keplars when something happens in Cerca?
Any of Keplars's 20 actions, including Create Audience, Send Email, Update Contact and Add Contact to Audience. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Keplars to Cerca?
Yes. When something happens in Keplars, your agent can act in Cerca too. This page covers both directions: Keplars's triggers and Cerca's actions are listed here as well.
Do I have to build a connector for Cerca or Keplars?
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 Cerca and Keplars 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.