Integration
Connect Cerca and MetaLocator
When Applicant Created fires in Cerca, your agent runs Create Record in MetaLocator, or New Lead in MetaLocator 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 MetaLocator 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 MetaLocator can do together
From Cerca to MetaLocator
When Applicant Created in Cerca
then Create Record in MetaLocator
When New Agency in Cerca
then Update Record in MetaLocator
From MetaLocator to Cerca
When New Lead in MetaLocator
then Create User in Cerca
When New Record in MetaLocator
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 MetaLocator
Triggers and actions 7 triggers · 30 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 LeadTriggers when a new lead (an inquiry sent to a location) is received in MetaLocator.
Trigger
New RecordTriggers when a new record (such as a location) is added to MetaLocator.
Trigger
New ReviewTriggers when a new review is submitted for one of your locations.
Action
Create CategoryCreates a category (tag) that records can be assigned to.
Action
Create RecordCreates a record (such as a location) in MetaLocator. Passing an existing record ID updates that record instead.
Action
Delete CategoryDeletes a category by its ID.
Action
Delete LeadDeletes a lead by its ID.
Action
Delete RecordDeletes a MetaLocator record by its ID.
Action
Find RecordFinds MetaLocator records matching a keyword and optional state, country or published filters, and returns the first match.
Action
Geocode AddressTurns an address into latitude and longitude using MetaLocator's geocoder.
Action
Get LeadReturns one lead (an inquiry sent to a location) by its ID.
Action
Get RecordReturns one MetaLocator record (a location or other table row) by its ID.
Action
List CategoriesReturns the account's categories (tags), one page at a time.
Action
Search InterfaceSearches published locations through a MetaLocator Interface, applying that Interface's filters and ordering.
Action
Update RecordUpdates an existing MetaLocator record. Only the fields you fill in are changed.
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 MetaLocator
HubSpot to MetaLocatorHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to MetaLocatorGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to MetaLocatorGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to MetaLocatorGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to MetaLocatorGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to MetaLocatorMailchimp marketing automation and email platform.
Questions
Cerca and MetaLocator, 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 MetaLocator when something happens in Cerca?
Any of MetaLocator's 12 actions, including Create Category, Create Record, Update Record and Find Record. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from MetaLocator to Cerca?
Yes. When something happens in MetaLocator, your agent can act in Cerca too. This page covers both directions: MetaLocator's triggers and Cerca's actions are listed here as well.
Do I have to build a connector for Cerca or MetaLocator?
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 MetaLocator 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.