Integration
Connect Cerca and Redmine
When Applicant Created fires in Cerca, your agent runs Update Issue in Redmine, or New tracker in Redmine 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 Redmine 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 Redmine can do together
From Cerca to Redmine
When Applicant Created in Cerca
then Update Issue in Redmine
From Redmine 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 Redmine
Triggers and actions 5 triggers · 33 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 tracker
Triggered every time a new tracker is created.
- Create Project
Creates a new project.
- Create Time Entry
Logs a time entry against an issue or project.
- Delete time entry
Deletes a time entry from Redmine.
- Delete user
Permanently deletes a Redmine user account. Requires administrator privileges.
- Get Issue
Retrieves a single issue by ID, including journals and attachments.
- Get Project
Retrieves a single project by ID or identifier.
- Get time entry
Returns a single Redmine time entry by its id, including project, issue, user, activity, hours, comments, date and custom field values.
- Get user
Returns a Redmine user's details, optionally with their project memberships, groups and authentication source.
- List Project Memberships
Lists the memberships (users and roles) of a project.
- List Projects
Lists all projects visible to the authenticated user.
- List Time Entries
Lists time entries, optionally filtered by project, issue, or user.
- List Users
Lists users (admin only), optionally filtered by status or name.
- Update Issue
Updates an existing issue by ID.
- Update time entry
Updates an existing Redmine time entry's hours, date, activity, comments, issue, project, user or custom fields.
- Update user
Updates an existing Redmine user's login, name, email, status, notification preferences, groups and custom fields. Requires administrator rights.
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 Redmine
Google Drive to RedmineGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to RedmineMailchimp marketing automation and email platform.
Questions
Cerca and Redmine, 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 Redmine when something happens in Cerca?
Any of Redmine's 15 actions, including Create Project, Create Time Entry, Update Issue and Update time entry. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Redmine to Cerca?
Yes. When something happens in Redmine, your agent can act in Cerca too. This page covers both directions: Redmine's triggers and Cerca's actions are listed here as well.
Do I have to build a connector for Cerca or Redmine?
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 Redmine 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.