Integration
Connect Cerca and Postman
When Applicant Created fires in Cerca, your agent runs Create Collection in Postman, or New Collection in Postman 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 Postman 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 Postman can do together
From Cerca to Postman
When Applicant Created in Cerca
then Create Collection in Postman
From Postman to 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 Postman
Triggers and actions 9 triggers · 44 actions
- Applicant Archived
Triggers when a Cerca applicant is archived.
- Applicant Created
Triggers when a new applicant (franchise candidate) is created in Cerca.
- Applicant Progressed
Triggers when a Cerca applicant moves to a different step.
- New Agency
Triggers when a new agency is added to your Cerca network.
- Approve user
Approves a user awaiting moderation, taking them out of moderation and activating their account.
- Create Agency
Creates a Cerca agency (a location in the network) and returns it.
- Create Applicant Request
Creates an applicant request (a new franchise candidate lead) on one of your Cerca applicant sources.
- Create User
Creates a user in the Cerca extranet and returns it.
- Delete Agency
Deletes a Cerca agency.
- Delete user
Deletes a user from your Cerca extranet.
- Demote applicant
Moves an applicant back to the previous step of their recruitment scenario and returns the updated applicant.
- Find Applicant
Finds Cerca applicants whose name, email or phone matches the search text, and returns the first match.
- Find users
Searches users by name or email and returns the matching users.
- Get Agency
Returns one Cerca agency (a location in the network) by its ID.
- Get Current User
Returns the Cerca user the access token acts as, with their name, email and agencies.
- Get user
Returns a single user of your Cerca extranet, including profile details, groups, agencies and custom fields.
- List Agencies
Returns a page of Cerca agencies, optionally filtered by a search term.
- List applicant scenarios
Returns every applicant scenario (recruitment funnel) in the extranet, the default one first.
- List Users
Returns a page of users in the Cerca extranet, optionally filtered by a search term.
- Promote Applicant
Advances a Cerca applicant to the next step of their recruitment scenario.
- Update Agency
Updates a Cerca agency's details; only the fields you fill in are changed.
- Update user
Updates an existing user's profile, contact details, address, groups, agencies and custom fields. Only the fields you fill in are changed.
- New Collection
Triggered when a new collection is created.
- New Environment
Triggers when you need to list environments. Optionally filter by workspace.
- New Mock Server
Triggers when you need to list mock servers. Optionally filter by workspace.
- New Monitor
Triggered when a new monitor is created in Postman.
- New Workspace
Triggered when a new workspace is created.
- Create Collection
Creates a new Postman collection.
- Create Environment
Creates a new Postman environment with optional variables.
- Create Folder
Creates a folder inside a collection.
- Create Mock Server
Creates a new mock server from a collection.
- Create Monitor
Creates a new Postman monitor for a collection.
- Create Request
Creates a new request in a Postman collection.
- Create Workspace
Creates a new Postman workspace.
- Delete Collection
Delete a collection by ID.
- Delete Environment
Delete an environment by ID.
- Delete Mock Server
Delete a mock server by ID.
- Delete Monitor
Delete a monitor by ID.
- Delete Workspace
Delete a workspace by ID.
- Find Collection by ID
Returns a single collection by ID.
- Find Environment by ID
Returns a single environment by ID.
- Find Mock Server by ID
Returns a single mock server by ID.
- Find Monitor by ID
Returns a single monitor by ID.
- Find Workspace by ID
Returns a single workspace by ID.
- List Collections
List all collections accessible to the API key, optionally filtered by workspace.
- List Environments
List all environments accessible to the API key, optionally filtered by workspace.
- List Workspaces
List all workspaces accessible to the API key.
- Run Monitor
Runs a Postman monitor and returns the run results.
- Update Collection
Replaces an existing collection with the name, requests and settings you supply.
- Update Environment
Updates an existing environment.
- Update Mock Server
Update a mock server's config.
- Update Monitor
Updates an existing monitor.
- Update Workspace
Updates an existing workspace.
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 Postman
Beanstalk to PostmanBeanstalk is a code hosting and deployment workflow tool for Git and Subversion.
Clockify to PostmanClockify is a completely free time tracking software for teams.
crates.io to PostmanSearch Rust crates and read crate metadata, versions, owners and download counts from the crates.io package...
Grist to PostmanGrist combines the flexibility of a spreadsheet with the robustness of a database to organize your data...
Langfuse to PostmanLangfuse is an open-source LLM engineering platform (GitHub) that helps teams collaboratively debug...
Questions
Cerca and Postman, 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 Postman when something happens in Cerca?
Any of Postman's 26 actions, including Create Collection, Create Environment, Create Folder and Create Mock Server. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Postman to Cerca?
Yes. When something happens in Postman, your agent can act in Cerca too. This page covers both directions: Postman's triggers and Cerca's actions are listed here as well.
Do I have to build a connector for Cerca or Postman?
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 Postman 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.