Integration
Connect awork and Coro
When New Client fires in awork, your agent runs Add Ticket Comment in Coro, or New Audit Log Entry in Coro to Create Time Entry in awork. 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 awork and Coro 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 awork and Coro can do together
From awork to Coro
When New Client in awork
then Add Ticket Comment in Coro
When New Project in awork
then Perform Ticket Action in Coro
From Coro to awork
When New Audit Log Entry in Coro
then Create Time Entry in awork
When New Device in Coro
then Create Project Task in awork
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 awork and Coro
Triggers and actions 12 triggers · 37 actions
Trigger
New ClientFires when a new company/client is created in awork. Poll/webhook on companies resource creation event.
Trigger
New ProjectTriggers when a new project is created.
Trigger
New TaskTriggers when a new task is created. The trigger only fires for tasks with a project assigned, not for private tasks.
Trigger
New Time EntryTriggers when a new time entry is created.
Trigger
Updated ClientFires when an existing company/client is updated in awork. Poll/webhook on companies resource update event.
Trigger
Updated ProjectFires when a project is updated in the awork workspace.
Trigger
Updated TaskTriggers when a task is updated. The trigger only fires for tasks with a project assigned, not for private tasks.
Trigger
Updated Time EntryTriggers when a time entry is updated.
Action
Create ClientCreates a client (company) in awork and returns the created company.
Action
Create ProjectCreates a new project.
Action
Create Project TaskCreates a task in an awork project.
Action
Create Time EntryCreates a time entry for a user, optionally against a project/task, using startDateUtc+duration or startDateUtc+endDateUtc.
Action
Delete ClientDeletes a client (company) in awork, optionally moving, detaching or deleting its linked projects and tasks.
Action
Delete ProjectDeletes an awork project and its tasks, optionally deleting its time entries too.
Action
Delete Project TaskDeletes an awork task by id.
Action
Delete Time EntryDeletes a time entry in awork.
Action
Find Project Tasks by criteriaReturns up to 100 tasks of a project that match the specified filter criteria.
Action
Find Time Entries by criteriaReturns up to 100 time entries in the workspace that match the specified filter criteria.
Action
Get Client by IDFinds a client by id
Action
Get Project by IDFinds a project by id
Action
Get Task by IDReturns a single awork task (project or private task) by its id, including status, assignees, project, tags, lists and custom field values.
Action
Get Time EntryReturns a single awork time entry by its id, including its task, project, user, type of work and breaks.
Action
Search ClientsReturns up to 100 clients (companies) whose name contains the specified text.
Action
Search ProjectsReturns up to 100 projects whose name contains the specified text, optionally narrowed by an additional filter.
Action
Search Users by EmailReturns the awork users whose contact information includes the specified email address.
Action
Update ClientUpdates an existing client (company) by ID. Fields left blank keep their current values.
Action
Update ProjectUpdates fields (name, status, workflow, etc) on an existing awork project.
Action
Update Project TaskUpdates fields (name, status, assignee, due date, etc) on an existing awork task.
Action
Update Time EntryUpdates an existing awork time entry: its times or duration, type of work, project, task, note and billing flags.
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.
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 awork
awork to agiliteLow-code platform providing BPM, business rules, roles, and API-key managed services for workflow automation.
awork to ShareFileSecurely send, store, and share files – plus discover document workflows designed to improve your client...
awork to Vouchery.ioVouchery is an all-in-one promotional suite to help you orchestrate & deliver the right incentive at every...
awork to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
awork to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
awork to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
More into Coro
ActiveCampaign to CoroActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to CoroOrganize anything with Airtable, a modern database created for everyone.
Asana to CoroAsana is a collaborative information manager for workspace.
ClickUp to CoroClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Brevo to CoroBrevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...
Calendly to CoroCalendly is a scheduling automation platform for eliminating the back-and-forth emails to find the perfect...
Questions
awork and Coro, answered
What can start an automation from awork?
Any of awork's 8 triggers in the catalog, including New Client, New Project, New Task and New Time Entry. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Coro when something happens in awork?
Any of Coro's 16 actions, including Update User Protection, Add Portal User, Add Ticket Comment and Get Portal User. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Coro to awork?
Yes. When something happens in Coro, your agent can act in awork too. This page covers both directions: Coro's triggers and awork's actions are listed here as well.
Do I have to build a connector for awork or Coro?
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 awork and Coro 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.