When new task in Project.co, sync it to Spike.sh.

When a new task is added in Project.co, trigger an alert or sync it as an incident in Spike.sh.

Try:

See all Spike.sh + Project.co integrations or talk to a human

Trusted by teams already building on Knit·

4.9/5 on G2·

Google for Startups Accelerator

How Knit builds this workflow

The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.

Spike.sh Explore Spike.sh →

Triggers

New alert

Fires when a monitor or check in Spike.sh raises an alert.

New or updated incident

Fires when an incident is opened or updated in Spike.sh.

Monitor state changed

Fires when a monitored site, service or alarm in Spike.sh changes state.

Actions

Create incident

Opens a new incident or alert in Spike.sh.

Acknowledge incident

Acknowledges an open incident in Spike.sh.

Resolve incident

Resolves an incident in Spike.sh.

Project.co Explore Project.co →

Triggers

New task created

Fires when a new task, job or item is created in Project.co.

Task completed

Fires when a task in Project.co is marked complete.

Due date approaching

Fires when a task's due date in Project.co is coming up.

Status changed

Fires when a task, job or project changes status in Project.co.

Actions

Create task

Creates a new task, job or item in Project.co.

Update task

Updates a task's status or assignee in Project.co.

Add comment

Posts a comment on a task in Project.co.

Assign task

Assigns a task in Project.co to a team member.

Create a task for each incident When an incident is opened in Spike.sh, create a task in Project.co and assign it to the owning team. See details

Schedule the post-incident review When an incident is resolved in Spike.sh, add a review task with a due date in Project.co. See details

Track recurring alerts When the same monitor alerts again in Spike.sh, add a comment to its existing task in Project.co. See details

See all Spike.sh + Project.co integrations → · Browse the full workflow library →

Enterprise-grade security

Visit our Security Center Review the DPA

FAQ

Common questions

Can Knit build “When new task in Project.co, sync it to Spike.sh.” between Spike.sh and Project.co?

Yes — describe it in the box above and Knit's Integrations Agent researches Spike.sh and Project.co's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.

How long does it take to build?

Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.

Why send incidents to a project management tool?

The alert is handled in Spike.sh, but the follow-up work lives in Project.co. Creating tasks automatically keeps that work visible and assigned.

Can I track action items from each incident?

Yes. When an incident is resolved in Spike.sh, create a task in Project.co for the review and any follow-up actions.