Integration
Connect Coro and openHandwerk
When New Audit Log Entry fires in Coro, your agent runs Update Customer in openHandwerk, or New Appointment in openHandwerk to Add Ticket Comment in Coro. 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 Coro 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 Coro and openHandwerk can do together
From Coro to openHandwerk
When New Audit Log Entry in Coro
then Update Customer in openHandwerk
When New Device in Coro
then Get Customer in openHandwerk
From openHandwerk to Coro
When New Appointment in openHandwerk
then Add Ticket Comment in Coro
When New Calendar Category in openHandwerk
then Perform Ticket Action in Coro
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 Coro and openHandwerk
Triggers and actions 8 triggers · 41 actions
Trigger
New Audit Log EntryTriggers when a new audit log entry is recorded in the workspace.
Trigger
New DeviceTriggers when a new device is enrolled in the workspace.
Trigger
New Protected UserTriggers when a new user appears in the workspace.
Trigger
New TicketTriggers when a new security ticket is created in the workspace.
Action
Add Portal UserInvites a user to the Coro end-user portal.
Action
Add Ticket CommentAdds a comment to a security ticket.
Action
Get Portal UserReturns one end-user portal user by ID.
Action
Get TicketReturns one security ticket by ID.
Action
Get UserReturns one user by ID.
Action
Get WorkspaceReturns the details of the connected Coro workspace.
Action
List DevicesReturns the protected devices in the workspace.
Action
List Portal UsersReturns the users of the Coro end-user portal.
Action
List Ticket ActionsReturns the actions that can be taken on a security ticket.
Action
List Ticket CommentsReturns the comments on a security ticket.
Action
List TicketsReturns security tickets in the workspace, optionally filtered by processed state and time range.
Action
List UsersReturns the users in the workspace, optionally filtered by email or name.
Action
Perform Ticket ActionRuns an action on a security ticket, such as marking it processed.
Action
Search Audit LogsReturns audit log entries for the workspace within an optional time range.
Action
Search WorkspacesReturns the child workspaces the connected workspace can access, optionally filtered by a search term.
Action
Update User ProtectionTurns Coro protection on or off for a user, identified by email.
Trigger
New AppointmentTriggers when a new appointment is created.
Trigger
New Calendar CategoryTriggers when a new calendar category is created.
Trigger
New CustomerTriggers when a new customer is created.
Trigger
New ProjectTriggers when a new order project is created.
Action
Create AppointmentCreates a calendar appointment, optionally linked to a project and with employee attendees.
Action
Create ProjectCreates a new project for a customer.
Action
Delete ProductDeletes a product.
Action
Delete SupplierDeletes a supplier.
Action
Get AppointmentReturns one appointment by its ID.
Action
Get CustomerReturns one customer by its ID.
Action
Get EmployeeReturns one employee by its ID.
Action
Get OfferReturns one offer by its ID.
Action
Get OrderReturns one order by its ID.
Action
Get ProductReturns one product by its ID.
Action
Get SupplierReturns one supplier by its ID.
Action
List AppointmentsReturns appointments, optionally filtered by title, attendee email, project or category.
Action
List Calendar CategoriesReturns the appointment calendar categories.
Action
List CustomersReturns customers, optionally filtered by company, city, email and other fields.
Action
List EmployeesReturns the account's employees, optionally filtered by name or role.
Action
List OffersReturns offers (quotes).
Action
List OrdersReturns orders (projects of type order).
Action
List ProductsReturns all products.
Action
List SuppliersReturns all suppliers.
Action
Search CustomersFinds customers matching a search term.
Action
Search ProjectsFinds a project matching a search term.
Action
Update AppointmentUpdates an existing calendar appointment.
Action
Update CustomerUpdates an existing customer.
Action
Update ProductUpdates an existing product.
Action
Update SupplierUpdates 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 Coro
Coro to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Coro to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Coro to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Coro to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Coro to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Coro to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into openHandwerk
HubSpot to openHandwerkHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to openHandwerkGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to openHandwerkGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to openHandwerkGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
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
Coro and openHandwerk, answered
What can start an automation from Coro?
Any of Coro's 4 triggers in the catalog, including New Audit Log Entry, New Device, New Protected User and New Ticket. Describe the moment in plain language and your agent picks the right one.
What can your agent do in openHandwerk when something happens in Coro?
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 Coro?
Yes. When something happens in openHandwerk, your agent can act in Coro too. This page covers both directions: openHandwerk's triggers and Coro's actions are listed here as well.
Do I have to build a connector for Coro 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 Coro 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.