---
title: "Connect Productive.io to Spike.sh - APIANT.ai"
description: "When \"New time entry\" fires in Productive.io, your agent runs \"Add alert rule\" in Spike.sh."
canonical: "https://apiant.ai/connect/productive-io-to-spike-sh"
---

# Connect Productive.io to Spike.sh

When **New time entry** fires in [Productive.io](https://apiant.ai/connections/productive-io), 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.

Productive.io **1** trigger Productive.io **34** 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 Productive.io 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 Productive.io can start in Spike.sh

- When **New time entry** in Productive.io then **Add alert rule** in Spike.sh
- When **New time entry** in Productive.io 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 Productive.io and Spike.sh

## Triggers and actions 1 trigger · 59 actions

- Trigger

**New time entry**

Triggers when a new time entry is tracked in Productive.

- Action

**Add Comment to Deal**

Adds a comment to a deal in Productive.

- Action

**Add comment to task**

Adds a comment to a task in Productive.

- Action

**Add expense**

Creates a new expense in Productive, optionally allocated to a budget service.

- Action

**Add invoice**

Creates a new invoice for a client company in Productive.

- Action

**Add time entry**

Creates a time entry in Productive, logging minutes a person worked on a service (and optionally a task) on a given date.

- Action

**Create Booking**

Creates a booking that schedules a person's time on a service or an absence event over a date range in Productive.

- Action

**Create Company**

Creates a new company (client) in Productive with its billing, invoicing and contact details.

- Action

**Create Contact**

Creates a contact (person) in Productive, linked to a client company.

- Action

**Create Deal**

Creates a new deal in Productive with a name, owner, deal type and date, plus optional value, company, contact and other deal details.

- Action

**Create Project**

Creates a new project in Productive with a name, type, project manager and workflow, optionally linked to a client company.

- Action

**Create Service**

Creates a service (a billable line of work) on a Productive deal or budget.

- Action

**Create Task**

Creates a task in a Productive project task list, with optional assignee, dates, estimates, tags and recurrence.

- Action

**Create Task List**

Creates a task list inside a project folder in Productive.

- Action

**Delete task**

Permanently deletes a task in Productive.

- Action

**Find Company**

Finds companies in Productive by name or company code and returns the matches.

- Action

**Find Contact**

Finds contacts (client people) in Productive by search text, email or company, returning the matches and the first one.

- Action

**Find Deal**

Finds deals in Productive by name, number or company and returns the matches.

- Action

**Find invoices by criteria**

Returns invoices matching an invoice number and/or company, with the first match and a count.

- Action

**Find projects by criteria**

Finds projects matching a name, client company, project manager or status, returning the matches and the first one.

- Action

**Find Task**

Finds tasks matching a title, number, search text, project, task list, assignee or status, and returns the first match plus the full list.

- Action

**Find time entries by criteria**

Returns time entries matching the criteria you give, such as person, service, task or date range.

- Action

**Find User**

Finds users (team members) in your Productive organization by name or email and returns the matches.

- Action

**Get Booking**

Returns a single booking (resource-planning allocation of a person to a service or event) by its ID, including dates, hours and custom fields.

- Action

**Get Comment**

Returns a single comment by its ID, including its body, timestamps and the task, deal or other record it was posted on.

- Action

**Get Expense**

Returns a single expense by its ID, including amounts, dates, approval status, custom fields and related records.

- Action

**Get Service**

Returns a single service (a budget or deal line item) by its ID, including its attributes and custom field values.

- Action

**Get Task List**

Returns a single task list by its ID, including its name, position, archive status and its project, board and folder.

- Action

**Update booking**

Updates an existing booking in Productive, such as its dates, booked time, note or assigned service. Fields left blank are not changed.

- Action

**Update company**

Updates an existing company in Productive. Only the fields you fill in are changed.

- Action

**Update Contact**

Updates an existing contact (person) in Productive. Only the fields you fill in are changed.

- Action

**Update Deal**

Updates an existing deal or budget in Productive, changing only the fields you fill in.

- Action

**Update project**

Updates an existing project in Productive. Only the values you fill in are changed.

- Action

**Update Task**

Updates an existing task in Productive. Only the values you fill in are changed.

- Action

**Update time entry**

Updates an existing time entry in Productive, changing only the fields you fill in.

- 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

- [ **Productive.io** Productive is a project management tool that includes everything you need to run a profitable agency.](https://apiant.ai/connections/productive-io)
- [ **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 Productive.io

- [ **Productive.io to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/productive-io-to-salesforce)
- [ **Productive.io to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/productive-io-to-slack)
- [ **Productive.io to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/productive-io-to-stripe)
- [ **Productive.io to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/productive-io-to-shopify)
- [ **Productive.io to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/productive-io-to-quickbooks-online)
- [ **Productive.io to Trello** Trello is a visual collaboration tool that organizes projects into boards, lists, and cards.](https://apiant.ai/connect/productive-io-to-trello)

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

## Productive.io and Spike.sh, answered

###

### What can start an automation from Productive.io?

Any of Productive.io's 1 trigger in the catalog, including New 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 Productive.io?

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 Productive.io?

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