Get phone and SMS alerts fromAsana
Asana is where many teams track the work that keeps production healthy. Spike turns a task that signals a problem into an on-call alert: a phone call, SMS, Slack message or email to whoever is on call, escalating until someone answers. Marking the task complete resolves the incident.
Set up with AI
I use Asana for monitoring and Spike for on-call and incident management. Walk me through connecting them: create a Asana integration in Spike, copy its webhook URL, and add that webhook to Asana alert settings. Then help me send a test alert to confirm incidents show up in Spike.
What is Asana?
Asana is a work management platform. Teams use it to track the tasks, projects and requests behind their product, including the ones raised when something is wrong in production: a customer-reported bug, a failed deploy, an expiring certificate. A task in a project is easy to miss, though, and nothing about it wakes anyone up.
Spike closes that gap. Asana doesn’t deliver events to Spike directly, so the task is forwarded through a tool such as Zapier or Make, or a small script of your own, as a JSON body to your Spike webhook URL. From there the task becomes a page: the on-call engineer is called and texted within seconds, and a task nobody acknowledges climbs the escalation policy until someone answers. The incident’s title is the task’s name, for example “Checkout returns HTTP 500 for EU customers after the 14:05 deploy”, so whoever is paged knows what is wrong before opening Asana. The project, assignee and a link to the task ride along on the incident.
Every task carries a gid, and Spike uses it to keep things together. A repeat for a task that is already open is added to the same incident rather than paging the team a second time, and two different tasks stay two separate incidents. Who gets paged is decided in Spike: alert routing rules read the fields each task arrives with, so a routine chore doesn’t wake the same people as a production outage.
When the task is marked complete, send it to Spike again with completed set to true. Spike matches it back to the open incident by gid and resolves it; the completion shows on the incident as an event titled with the task name followed by “marked complete”.
How to set up Asana alerts
Every Spike integration is a unique webhook URL. Paste it into Asana and alerts start flowing — no agents, no code.
Step 1: Create an Asana integration in Spike
In your Spike dashboard, open Integrations and choose Asana. Spike generates a unique webhook URL for this integration. Copy it, and attach the integration to the service and escalation policy that should answer these tasks.
Step 2: Forward tasks from Zapier, Make or a script
Asana's own webhooks can't be pointed at Spike, so forward the task yourself. In Zapier, trigger on Asana New Task and Completed Task and send it with Webhooks by Zapier POST, Payload Type json. In Make, trigger on Asana Watch New Tasks and Watch Tasks or Subtasks and send it with HTTP Make a request, Body input method Data structure. Both tools encode the values for you, so quotes and line breaks in a task can't break the JSON.
Step 3: Send the task fields Spike reads
Map the task's gid, its name, its notes and whether it is completed as fields, never pasted into hand-written JSON. Send gid as a string, because Asana ids are too long to survive as JSON numbers. The project, assignee and link can ride along for the people who respond.
Step 4: Watch a task become an incident
When a task arrives, Spike opens an incident titled with the task name. If the name is empty, the title is "Asana task in" followed by the project, or "Asana task with no details" when there is no project. A repeat for the same gid joins that incident instead of paging again, and when you send the task again with completed set to true, the incident resolves itself.
That's it — Asana alerts now page whoever is on call.
