Integration
Connect Cerca and Truss
When Applicant Created fires in Cerca, your agent runs Add Contact to Entity in Truss, or New Comment in Truss 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 Truss 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 Truss can do together
From Cerca to Truss
When Applicant Created in Cerca
then Add Contact to Entity in Truss
From Truss 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 Truss
Triggers and actions 13 triggers · 30 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.
- Contact Modified
Triggers when a contact's details change.
- New Comment
Triggers when a new comment is added to a task.
- New Contact
Triggers when a new contact is created.
- New Entity
Triggers when a new entity is created.
- New Project Created
Triggers when a new project is created in the firm.
- New Task
Triggers when a new task is added to a project.
- Project Modified
Triggers when a project is created or changed.
- Project Status Change
Triggers when a project's status changes.
- Project Task Modified
Triggers when a task in a project is added or changed (name, description, status or due date).
- Add Contact to Entity
Links an existing contact to an existing entity and returns the entity.
- Add Project to Entity
Links an existing project to an existing entity and returns the entity.
- Change Project Status
Changes a project's status to the status you choose.
- Create Assignee by Contact ID
Assigns an existing contact to a project.
- Create Contact
Creates a client contact with a name and primary email.
- Create Entity
Creates an entity (a business or individual taxpayer) in the firm.
- Get All Projects in Firm
Returns every project in the firm.
- Get All Tasks in Project
Returns every task in a project.
- Get Contact by ID
Returns a contact by its ID.
- Get Entity by ID
Returns an entity by its ID, with its linked contacts and projects.
- Get One Task From Project
Returns one task of a project, with its attached files.
- Update Project Name or Metadata
Updates a project's name, due date or metadata.
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 Truss
Questions
Cerca and Truss, 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 Truss when something happens in Cerca?
Any of Truss's 12 actions, including Create Assignee by Contact ID, Create Contact, Create Entity and Update Project Name or Metadata. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Truss to Cerca?
Yes. When something happens in Truss, your agent can act in Cerca too. This page covers both directions: Truss's triggers and Cerca's actions are listed here as well.
Do I have to build a connector for Cerca or Truss?
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 Truss 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.