---
title: "Connect Timely Time Tracking to Spike.sh - APIANT.ai"
description: "When \"New Client\" fires in Timely Time Tracking, your agent runs \"Add alert rule\" in Spike.sh."
canonical: "https://apiant.ai/connect/timely-time-tracking-to-spike-sh"
---

# Connect Timely Time Tracking to Spike.sh

When **New Client** fires in [Timely Time Tracking](https://apiant.ai/connections/timely-time-tracking), your agent runs **Add alert rule** in [Spike.sh](https://apiant.ai/connections/spike-sh). Describe the whole flow and it is built, tested on every scenario and kept running.

Timely Time Tracking **8** triggers Timely Time Tracking **19** actions Spike.sh **25** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want Timely Time Tracking and Spike.sh to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One 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.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

Example flows

## What Timely Time Tracking can start in Spike.sh

- When **New Client** in Timely Time Tracking then **Add alert rule** in Spike.sh
- When **New or Updated Person** in Timely Time Tracking then **Add escalation** in Spike.sh

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 Timely Time Tracking and Spike.sh

## Triggers and actions 8 triggers · 44 actions

- Trigger

**New Client**

Triggered when a new client is created

- Trigger

**New or Updated Person**

Triggered when a person is created or updated in Timely

- Trigger

**New or Updated Project**

Triggers when a project is created or updated.

- Trigger

**New or Updated Time Entry**

Triggers when time entries are created or updated.

- Trigger

**New Project**

Triggered when a new project is created

- Trigger

**New Time Entry**

Triggered when a new time entry is created

- Trigger

**New Workspace**

Triggers when a workspace is created.

- Trigger

**Project Updated (Only Admin Users)**

Triggers when any project is updated in Timely. Fires for ALL project changes (name, budget, rate, archive, labels, users, etc. Can only be used by Timely Admin users. WARNING: avoid chaining this trigger to actions that write back to the same project (e. g. via "Update Project Name") in the source system without a guard — that can create an infinite update loop.

- Action

**Add tag**

Create a tag.

- Action

**Create Client**

Creates a Client

- Action

**Create Person**

Creates a new person in the workspace.

- Action

**Create Project**

Creates a project.

- Action

**Create Task**

Creates a task.

- Action

**Delete project**

Delete a project.

- Action

**Delete time entry**

Delete a time entry.

- Action

**Find Client**

Returns the clients in a Timely workspace whose name matches the given text.

- Action

**Find Project**

Returns the projects whose name contains the specified text.

- Action

**Find Tag List and Tag**

Finds a tag list and a specific tag if specified.

- Action

**Find time entries by criteria**

Search time entries by date range, user, project.

- Action

**Find User**

Finds a User

- Action

**Get Task**

Retrieves a single task (forecast) by its id.

- Action

**Log Time Entry**

Logs a new time entry against a project.

- Action

**Start timer**

Start the timer on a time entry.

- Action

**Stop timer**

Stop the running timer on a time entry.

- Action

**Update client**

Update a client.

- Action

**Update Project Name**

Updates only the name of an existing project. Look up the project by Timely Project ID or by External ID (recommended when the source-of-truth system stores the Timely external_id, e.g. NetSuite).

- Action

**Update time entry**

Update a logged time entry.

- Action

**Acknowledge incident**

Acknowledge one or more Spike.sh incidents by counter id or incident id.

- Action

**Add alert rule**

Create a new alert routing/automation rule with conditions and actions.

- Action

**Add escalation**

Creates a new escalation policy for a Spike.sh team, defining who is notified, through which channel, and how long to wait between steps.

- Action

**Add integration**

Create a new integration for a team (source system that sends alerts into Spike).

- Action

**Add on-call**

Create a new on-call schedule for a team.

- Action

**Add service**

Create a new service in a team, with name and description.

- Action

**Create Incident**

Creates a Spike incident through one of your integrations and sends alerts. The integration decides which service and escalation policy the incident is routed to.

- Action

**Delete alert rule**

Archives (soft-deletes) a Spike alert rule so it no longer applies to incoming incidents.

- Action

**Delete escalation**

Archives (soft-deletes) a Spike escalation policy by its ID.

- Action

**Escalate incident**

Escalates one or more Spike incidents to the next step of their escalation policy.

- Action

**Get escalation**

Get escalation policy details by id.

- Action

**Get incident**

Fetch a single incident by counter id.

- Action

**Get integration**

Fetches an integration by its token, including its name, type, service, escalation settings and webhook URL. An error occurs if the integration is not found.

- Action

**Get service**

Get a Spike service's details, along with its incidents and open-incident count.

- Action

**List alert rules**

Lists all alert rules (enabled and disabled) configured for a Spike team.

- Action

**List escalations**

Lists the escalation policies that belong to a Spike team.

- Action

**List incidents**

Lists the incidents for a Spike.sh team.

- Action

**List on-calls**

Lists the on-call schedules for a team.

- Action

**List services**

Lists the services in a Spike team.

- Action

**List teams**

Lists every team in your Spike organisation. Use a team's ID from here wherever other Spike actions ask for a team.

- Action

**Resolve incident**

Resolve one or more incidents by counter id array.

- Action

**Update alert rule**

Replace an existing Spike alert rule's name, conditions and actions.

- Action

**Update escalation**

Replaces an existing escalation policy's name, steps and start delay. The whole policy is replaced, so send every step you want to keep.

- Action

**Update on-call**

Updates an on-call schedule's name and/or moves it to another team. Rotations and layers are not changed by this action.

- Action

**Update service**

Updates the name and/or description of an existing Spike.sh service.

## Each app on its own

- [ **Timely Time Tracking** Timely Time Tracking automates company time tracking, so everyone can focus on the work that matters.](https://apiant.ai/connections/timely-time-tracking)
- [ **Spike.sh** Spike is an incident management system with unlimited alerts and on-call schedules](https://apiant.ai/connections/spike-sh)

Reviews

## What our customers say

## More from Timely Time Tracking

- [ **Timely Time Tracking to Zelothorn** Zelothorn publishes plain-English explanations of US public companies built from SEC filings and earnings...](https://apiant.ai/connect/timely-time-tracking-to-zelothorn)
- [ **Timely Time Tracking to Trello** Trello is a visual collaboration tool that organizes projects into boards, lists, and cards.](https://apiant.ai/connect/timely-time-tracking-to-trello)
- [ **Timely Time Tracking to Zoom** Zoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...](https://apiant.ai/connect/timely-time-tracking-to-zoom)
- [ **Timely Time Tracking to Twilio** Cloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...](https://apiant.ai/connect/timely-time-tracking-to-twilio)
- [ **Timely Time Tracking to Typeform** Build and publish online forms, surveys, and quizzes with Typeform.](https://apiant.ai/connect/timely-time-tracking-to-typeform)
- [ **Timely Time Tracking to Webflow** Webflow is a professional website builder and CMS for designing, building, and launching responsive...](https://apiant.ai/connect/timely-time-tracking-to-webflow)

## More into Spike.sh

- [ **HubSpot to Spike.sh** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-spike-sh)
- [ **Salesforce to Spike.sh** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-spike-sh)
- [ **Slack to Spike.sh** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-spike-sh)
- [ **Google Sheets to Spike.sh** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-spike-sh)
- [ **Gmail to Spike.sh** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-spike-sh)
- [ **Google Calendar to Spike.sh** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-spike-sh)

Questions

## Timely Time Tracking and Spike.sh, answered

###

### What can start an automation from Timely Time Tracking?

Any of Timely Time Tracking's 8 triggers in the catalog, including New Client, New or Updated Person, New or Updated Project and New or Updated Time Entry. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in Spike.sh when something happens in Timely Time Tracking?

Any of Spike.sh's 25 actions, including Create Incident, Update alert rule, Update escalation and Update on-call. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Spike.sh to Timely Time Tracking?

Spike.sh has no triggers in the catalog today, so automations start in Timely Time Tracking. If you need the other direction, ask: your agent reads Spike.sh's API documentation and adds it.

###

### Do I have to build a connector for Timely Time Tracking or Spike.sh?

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 Timely Time Tracking and Spike.sh 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.
