---
title: "Connect timelink to Spike.sh - APIANT.ai"
description: "When \"New Time Entry\" fires in timelink, your agent runs \"Add alert rule\" in Spike.sh."
canonical: "https://apiant.ai/connect/timelink-to-spike-sh"
---

# Connect timelink to Spike.sh

When **New Time Entry** fires in [timelink](https://apiant.ai/connections/timelink), 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.

timelink **3** triggers timelink **24** 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 timelink 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 timelink can start in Spike.sh

- When **New Time Entry** in timelink then **Add alert rule** in Spike.sh
- When **Updated Time Entry** in timelink 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 timelink and Spike.sh

## Triggers and actions 3 triggers · 49 actions

- Trigger

**Deleted Time Entry**

Triggers when a time entry is deleted.

- Trigger

**New Time Entry**

Triggers when a new time entry is created.

- Trigger

**Updated Time Entry**

Triggers when a time entry is updated.

- Action

**Create Client**

Creates a new client in timelink.

- Action

**Create Project**

Creates a new project in timelink, optionally assigned to a client.

- Action

**Create Service**

Creates a new service (a type of work you track time against) in timelink.

- Action

**Create Time Entry**

Creates a time entry for a user in timelink, optionally linked to a client, project and service.

- Action

**Delete client**

Deletes a client in timelink.

- Action

**Delete project**

Deletes a project in timelink.

- Action

**Delete service**

Deletes a service in timelink.

- Action

**Delete time entry**

Deletes a time entry from timelink.

- Action

**Find Client**

Finds clients whose details match the search text, optionally filtered by active status or ids.

- Action

**Find Project**

Searches projects by name or other text and returns the matching projects, optionally narrowed to one client or to active/inactive projects.

- Action

**Find Service**

Searches your timelink services by text, for example part of the service name, and returns the matching services.

- Action

**Find Time Entry**

Searches time entries by text and optional filters such as date range, client, project, service, user and billing status, returning the matching entries.

- Action

**Get client**

Returns a single client by its ID.

- Action

**Get project**

Returns a single timelink project by its ID, including its client, color, acronym and active/billable flags.

- Action

**Get service**

Returns a single service (activity type) by its ID, including name, color, acronym and billable/active status.

- Action

**Get time entry**

Returns a single time entry by its ID, including its client, project, service, description, billing flags and start/end times.

- Action

**Get user**

Returns a single timelink user by ID, including name, email, active status, timezone and language.

- Action

**List clients**

Returns the clients in your timelink account, optionally filtered by search text or active status.

- Action

**List services**

Returns the services (billable activities) in your timelink account, optionally filtered by text, active status or specific ids.

- Action

**List users**

Returns the users in your timelink company, optionally filtered by search text, active status or specific user ids.

- Action

**Update Client**

Updates an existing client in timelink. Only the fields you fill in are changed.

- Action

**Update Project**

Updates an existing project's name, client, color, billing and other details. Only the fields you fill in are changed.

- Action

**Update Service**

Updates an existing service in timelink, such as its name, color, billable or active status.

- Action

**Update Time Entry**

Updates an existing time entry in timelink, changing only the details you fill in, such as its times, description, client, project or service.

- 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

- [ **timelink** timelink is a time recording tool that optionally uses a physical touch display as an input device.](https://apiant.ai/connections/timelink)
- [ **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 timelink

- [ **timelink to Trello** Trello is a visual collaboration tool that organizes projects into boards, lists, and cards.](https://apiant.ai/connect/timelink-to-trello)
- [ **timelink to Zoom** Zoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...](https://apiant.ai/connect/timelink-to-zoom)
- [ **timelink to Twilio** Cloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...](https://apiant.ai/connect/timelink-to-twilio)
- [ **timelink to Typeform** Build and publish online forms, surveys, and quizzes with Typeform.](https://apiant.ai/connect/timelink-to-typeform)
- [ **timelink to Webflow** Webflow is a professional website builder and CMS for designing, building, and launching responsive...](https://apiant.ai/connect/timelink-to-webflow)
- [ **timelink to Wix** The Wix website builder gives businesses of any size the tools to create, manage and grow a fully integrated...](https://apiant.ai/connect/timelink-to-wix)

## 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](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

## timelink and Spike.sh, answered

###

### What can start an automation from timelink?

Any of timelink's 3 triggers in the catalog, including New Time Entry, Updated Time Entry and Deleted 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 timelink?

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 timelink?

Spike.sh has no triggers in the catalog today, so automations start in timelink. 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 timelink 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 timelink 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.
