Integration
Connect Clockify to Daytona
When New Client fires in Clockify, your agent runs Add sandbox in Daytona. 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 Daytona 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 can start in Daytona
When New Client in Clockify
then Add sandbox in Daytona
When New Project in Clockify
then Add snapshot in Daytona
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 Daytona
Triggers and actions 7 triggers · 40 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.
Action
Add sandboxCreates a new Daytona sandbox from a snapshot or build definition, with optional resources, labels, environment variables and network settings.
Action
Add snapshotCreates a new snapshot from a container image or Dockerfile, which sandboxes can then be started from.
Action
Add volumeCreates a new storage volume in your Daytona organization that sandboxes can mount.
Action
Archive sandboxArchives a stopped sandbox, moving its filesystem to cheaper storage until it is started again.
Action
Delete sandboxDeletes a Daytona sandbox by its ID or name and returns the sandbox record as it is being destroyed.
Action
Delete snapshotDeletes a snapshot from your Daytona organization.
Action
Delete volumeDeletes a Daytona volume. The volume must not be in use by any sandbox.
Action
Get sandboxReturns the details of a sandbox, including its state, resources, labels and settings.
Action
Get snapshotReturns a snapshot's details, including its state, image, resources and regions, looked up by ID or name.
Action
Get volumeReturns the details of a volume, including its name, state and timestamps.
Action
List sandboxesReturns the sandboxes in your Daytona organization, optionally filtered by name, ID, labels, state, snapshot, region, class, resources, public status and dates, and sorted.
Action
List snapshotsReturns the snapshots in your Daytona organization, optionally filtered by name or by the sandbox they were created from.
Action
List volumesReturns all volumes in your Daytona organization, optionally including deleted ones.
Action
Start sandboxStarts a stopped or archived sandbox, or resumes a paused one, and returns the sandbox.
Action
Stop sandboxStops a running sandbox, optionally forcing it to shut down immediately. Returns the sandbox record.
Action
Update sandbox labelsReplaces all labels on a Daytona sandbox with the key-value pairs you supply.
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 Daytona
HubSpot to DaytonaHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to DaytonaSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to DaytonaSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to DaytonaGoogle Sheets
Gmail to DaytonaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to DaytonaGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Clockify and Daytona, 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 Daytona when something happens in Clockify?
Any of Daytona's 16 actions, including Update sandbox labels, Add sandbox, Add snapshot and Add volume. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Daytona to Clockify?
Daytona has no triggers in the catalog today, so automations start in Clockify. If you need the other direction, ask: your agent reads Daytona's API documentation and adds it.
Do I have to build a connector for Clockify or Daytona?
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.