Integration
Connect Cerca and openHandwerk
When Applicant Created fires in Cerca, your agent runs Update Customer in openHandwerk, or New Appointment in openHandwerk 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 openHandwerk 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 openHandwerk can do together
From Cerca to openHandwerk
When Applicant Created in Cerca
then Update Customer in openHandwerk
From openHandwerk 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 openHandwerk
Triggers and actions 8 triggers · 43 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 Appointment
Triggers when a new appointment is created.
- New Calendar Category
Triggers when a new calendar category is created.
- New Customer
Triggers when a new customer is created.
- New Project
Triggers when a new order project is created.
- Create Appointment
Creates a calendar appointment, optionally linked to a project and with employee attendees.
- Create Project
Creates a new project for a customer.
- Delete Product
Deletes a product.
- Delete Supplier
Deletes a supplier.
- Get Appointment
Returns one appointment by its ID.
- Get Customer
Returns one customer by its ID.
- Get Employee
Returns one employee by its ID.
- Get Offer
Returns one offer by its ID.
- Get Order
Returns one order by its ID.
- Get Product
Returns one product by its ID.
- Get Supplier
Returns one supplier by its ID.
- List Appointments
Returns appointments, optionally filtered by title, attendee email, project or category.
- List Calendar Categories
Returns the appointment calendar categories.
- List Customers
Returns customers, optionally filtered by company, city, email and other fields.
- List Employees
Returns the account's employees, optionally filtered by name or role.
- List Offers
Returns offers (quotes).
- List Orders
Returns orders (projects of type order).
- List Products
Returns all products.
- List Suppliers
Returns all suppliers.
- Search Customers
Finds customers matching a search term.
- Search Projects
Finds a project matching a search term.
- Update Appointment
Updates an existing calendar appointment.
- Update Customer
Updates an existing customer.
- Update Product
Updates an existing product.
- Update Supplier
Updates an existing supplier.
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 openHandwerk
Google Drive to openHandwerkGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to openHandwerkMailchimp marketing automation and email platform.
Questions
Cerca and openHandwerk, 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 openHandwerk when something happens in Cerca?
Any of openHandwerk's 25 actions, including Create Appointment, Create Project, Update Appointment and Update Customer. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from openHandwerk to Cerca?
Yes. When something happens in openHandwerk, your agent can act in Cerca too. This page covers both directions: openHandwerk's triggers and Cerca's actions are listed here as well.
Do I have to build a connector for Cerca or openHandwerk?
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 openHandwerk 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.