Integration
Connect Clockify and Trengo
When something happens in Clockify or Trengo, your agent does the next thing in the other. Describe it 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 Clockify and Trengo to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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)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 Clockify and Trengo can do together
From Clockify to Trengo
When New Client in Clockify
then Add internal note to ticket in Trengo
When New Project in Clockify
then Add ticket in Trengo
From Trengo to Clockify
When New Internal Note in Trengo
then Create Client in Clockify
When New Outbound Message in Trengo
then Create Project in Clockify
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 Clockify and Trengo
Triggers and actions 10 triggers · 39 actions
Trigger
New ClientTriggers when a new client is added to a workspace.
Trigger
New ProjectTriggers when a new project is added to a workspace.
Trigger
New TagTriggers when a new tag is added to a workspace.
Trigger
New TaskTriggers when a new task is added to a project on a specified workspace.
Trigger
New Time EntryTriggers when a new time entry is added.
Trigger
New Timer StartedTriggers when a new entry is started and running.
Trigger
New WorkspaceTriggers when a new workspace is created.
Action
Create ClientCreates a client on a specified workspace.
Action
Create ProjectCreates a project on a specified workspace.
Action
Create TagCreates a tag on a specified workspace.
Action
Create TaskCreates a task on a specified project.
Action
Create Time EntryCreates a new time entry on a specified workspace.
Action
Delete ClientDelete a client from a workspace.
Action
Delete ProjectDelete a project from a workspace.
Action
Delete TagDelete a tag from a workspace.
Action
Delete TaskDelete a task from a project.
Action
Delete Time EntryDelete a time entry from a workspace.
Action
Find ClientFinds a client by name on a specified workspace.
Action
Find ProjectFinds a project by name on a specified workspace.
Action
Find Running TimerFinds a currently running time entry on a specified workspace.
Action
Find TagFinds a tag on a specified workspace.
Action
Find TaskFinds a task by name on a specified project and workspace.
Action
Find Time EntryFinds a time entry by description, start datetime or end datetime.
Action
List WorkspacesList all workspaces the authenticated user belongs to.
Action
Start TimerStarts a new time entry.
Action
Stop TimerStops currently running time entry on a specified workspace.
Action
Update ClientUpdate a client's name/note/archived status.
Action
Update ProjectUpdate a project's name/color/client/billable status/dates.
Action
Update TagUpdate a tag's name/archived status on a workspace.
Action
Update TaskUpdate a task's name/status/assignee/estimate on a project.
Action
Update Time EntryUpdate a time entry's start/end/description/project/task/billable/tags on a workspace.
Trigger
New Internal NoteFires when an internal note is added to a Trengo ticket.
Trigger
New Outbound MessageTriggers when an outbound message is created.
Trigger
Ticket Label AddedTriggers when a label is added to a conversation.
Action
Add internal note to ticketAdds an internal note (visible only to agents) to a Trengo ticket.
Action
Add ticketCreate a new support ticket.
Action
Add ticket labelAttaches an existing label to a Trengo ticket.
Action
Create a ContactCreates a contact on a Trengo channel. If a contact with the same identifier already exists on that channel, Trengo returns the existing contact instead of creating a duplicate.
Action
Create webhookSubscribes a URL to one Trengo webhook event type. Used by Trengo instant triggers to register their delivery URL on activation.
Action
Delete contactDelete a contact by id.
Action
Delete ticketDelete a ticket by id.
Action
Find a ContactReturns the Trengo contacts that match the search term.
Action
Get contactRetrieve a single Trengo contact by its id.
Action
Get webhookFetches a webhook by ID, including the event it listens for, the address it sends to and its signing secret. An error occurs if the webhook is not found.
Action
List contactsList all contacts.
Action
List labelsLists the ticket labels defined in the Trengo account (first page).
Action
List ticketsReturns all tickets the connected user is authorized to see, optionally filtered by status, contact, users, channels, labels, last message type or update time.
Action
Send a MessageSends a reply message on an existing Trengo ticket, over the ticket's own channel.
Action
Update contactUpdate an existing contact by id.
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 Clockify
Clockify to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Clockify to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Clockify to Google SheetsGoogle Sheets
Clockify to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Clockify to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Clockify to Google DriveGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
More into Trengo
HubSpot to TrengoHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to TrengoSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to TrengoSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to TrengoGoogle Sheets
Gmail to TrengoGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to TrengoGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Clockify and Trengo, answered
What can start an automation from Clockify?
Any of Clockify's 7 triggers in the catalog, including New Client, New Project, New Tag and New Task. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Trengo when something happens in Clockify?
Any of Trengo's 15 actions, including Create a Contact, Create webhook, Send a Message and Update contact. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Trengo to Clockify?
Yes. When something happens in Trengo, your agent can act in Clockify too. This page covers both directions: Trengo's triggers and Clockify's actions are listed here as well.
Do I have to build a connector for Clockify or Trengo?
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.
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.