Integration
Connect Clockify and Request Tracker (RT)
When New Client fires in Clockify, your agent runs Create Ticket in Request Tracker (RT), or Ticket Created in Request Tracker (RT) to Create Task in Clockify. 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 Clockify and Request Tracker (RT) 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 Request Tracker (RT) can do together
From Clockify to Request Tracker (RT)
When New Client in Clockify
then Create Ticket in Request Tracker (RT)
When New Project in Clockify
then Update ticket in Request Tracker (RT)
From Request Tracker (RT) to Clockify
When Ticket Created in Request Tracker (RT)
then Create Task in Clockify
When Ticket Status Changed in Request Tracker (RT)
then Create Client 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 Request Tracker (RT)
Triggers and actions 10 triggers · 43 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
Ticket CorrespondenceTriggers when a ticket is replied to (that is, corresponded with).
Trigger
Ticket CreatedTriggers when a new Request Tracker ticket is created.
Trigger
Ticket Status ChangedTriggers when a Request Tracker ticket changes status. Can watch for any status change or only for changes to a specific status.
Action
Add assetCreate an asset.
Action
Add userCreate a user.
Action
Comment on a TicketAdd an internal comment to a ticket and send to any internal watchers.
Action
Create TicketCreate a new ticket in Request Tracker.
Action
Find AttachmentLocate an attachment by ID.
Action
Find TicketLocate a ticket by ID.
Action
Find TicketsIssue a query to find matching tickets.
Action
Find TransactionFind a transaction by ID
Action
Get assetRetrieves one asset by ID: name, description, status, catalog, owner, held by, contact, custom fields.
Action
Get queueGet a queue by id or name.
Action
Get userGet a user by id or name.
Action
List queuesList all queues visible to user.
Action
List ticket historyList transactions of a ticket.
Action
Reply to a TicketReply to the requestor and any internal or external watchers of a ticket.
Action
Update ticketGeneral ticket update (Owner, Priority, Queue, custom fields).
Action
Update Ticket Due DateUpdate the due date of a ticket.
Action
Update Ticket StatusUpdate the status of a ticket.
Action
Update Ticket SubjectUpdate the subject of a ticket.
Action
Update userUpdate a user.
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 KimaiTime-tracking platform for project-driven teams, with invoicing, expense tracking, and reporting.
Clockify to NvidiaAPI platform for deploying GPU-accelerated AI models, including inference microservices and a container...
Clockify to PostmanPostman is a platform for building and testing APIs.
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
More into Request Tracker (RT)
HubSpot to Request Tracker (RT)HubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to Request Tracker (RT)Google Sheets
Gmail to Request Tracker (RT)Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Request Tracker (RT)Google Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to Request Tracker (RT)Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to Request Tracker (RT)Mailchimp marketing automation and email platform.
Questions
Clockify and Request Tracker (RT), 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 Request Tracker (RT) when something happens in Clockify?
Any of Request Tracker (RT)'s 19 actions, including Create Ticket, Update ticket, Update Ticket Due Date and Update Ticket Status. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Request Tracker (RT) to Clockify?
Yes. When something happens in Request Tracker (RT), your agent can act in Clockify too. This page covers both directions: Request Tracker (RT)'s triggers and Clockify's actions are listed here as well.
Do I have to build a connector for Clockify or Request Tracker (RT)?
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.