How to Sync Asana Sprints to Slack with n8n

n8n Canvas > + Node > Trigger > Webhook

Create a new n8n workflow and add the Webhook node

Open n8n and click the orange '+ New Workflow' button in the top right. On the blank canvas, click the '+' node icon and search for 'Webhook'. Select the Webhook node — this will be your trigger. n8n generates a unique webhook URL immediately. Copy that URL; you'll paste it into Asana in the next step.

1. 1Click '+ New Workflow' in the top right of the n8n dashboard
2. 2Click the '+' node placeholder on the canvas
3. 3Search for 'Webhook' in the node search bar
4. 4Select 'Webhook' under Trigger nodes
5. 5Copy the generated webhook URL from the node panel

Asana Developer Console > Personal Access Tokens > Copy Token

Register the webhook in Asana

Asana doesn't have a UI-based webhook setup — you have to call their API directly. Use Asana's Webhooks API (POST to https://app.asana.com/api/1.0/webhooks) with your personal access token in the Authorization header. Set the 'resource' to your Asana project GID and the 'target' to the n8n webhook URL you copied. Asana will send a handshake request immediately to verify the endpoint.

1. 1Go to https://app.asana.com/0/developer-console and create a Personal Access Token
2. 2Open a terminal or Postman and POST to https://app.asana.com/api/1.0/webhooks
3. 3Set Authorization header to: Bearer YOUR_ASANA_TOKEN
4. 4Set body: { "data": { "resource": "YOUR_PROJECT_GID", "target": "YOUR_N8N_WEBHOOK_URL" } }
5. 5Check the response for a 201 status and note the webhook GID

n8n Canvas > + Node > Flow > Switch

Add a Switch node to route by event type

Asana webhooks fire for many event types — task creation, section changes, due date updates, and more. You only want three: sprint start (a section named 'In Progress' gets a task), sprint completion (milestone task marked complete), and blockers (a tag named 'Blocker' is added). Add an n8n Switch node after the Webhook node to filter these three paths. Each route will lead to a different Slack message format.

1. 1Click '+' after the Webhook node and search for 'Switch'
2. 2Set the Switch mode to 'Rules'
3. 3Add Rule 1: field = {{ $json.events[0].action }}, equals 'changed', AND {{ $json.events[0].change.field }} equals 'completed'
4. 4Add Rule 2: field = {{ $json.events[0].resource.resource_type }} equals 'tag' AND action equals 'added'
5. 5Add Rule 3: {{ $json.events[0].change.new_value.name }} contains 'In Progress'

n8n Canvas > + Node > Core > HTTP Request

Fetch full task details from Asana API

The Asana webhook payload gives you minimal data — just the resource GID and event type. To build a meaningful Slack message, you need task name, assignee, due date, and custom fields like story points. Add an HTTP Request node on each branch to call GET https://app.asana.com/api/1.0/tasks/{task_gid}?opt_fields=name,assignee.name,due_on,custom_fields,completed. Connect one HTTP Request node per Switch branch.

1. 1Click '+' on Switch output 0 and add an HTTP Request node
2. 2Set Method to GET
3. 3Set URL to: https://app.asana.com/api/1.0/tasks/{{ $json.events[0].resource.gid }}?opt_fields=name,assignee.name,due_on,custom_fields,completed
4. 4Under Authentication, choose 'Header Auth', set Name to 'Authorization', Value to 'Bearer YOUR_ASANA_TOKEN'
5. 5Duplicate this node and connect copies to Switch outputs 1 and 2

n8n Canvas > + Node > Core > Code

Add a Code node to parse sprint data and build message payloads

Asana custom fields come back as an array of objects, each with a gid and display_value. You need to find the right custom field by name (e.g. 'Story Points', 'Capacity %') rather than by index. Add a Code node after each HTTP Request node to extract these values and construct a clean object for the Slack message. This is where n8n's code node earns its place — no other node handles Asana's custom_fields array cleanly.

1. 1Click '+' after the HTTP Request node on the sprint completion branch
2. 2Select the 'Code' node
3. 3Set language to JavaScript
4. 4Paste the transformation code from the Pro Tip section below
5. 5Run the node and verify the output shows storyPoints, capacity, taskName, and assignee fields

This Code node runs after the Asana HTTP Request node on any branch. It extracts story points and capacity from Asana's custom_fields array (which comes back as unordered objects), computes sprint summary counts, and returns a clean payload the Slack node can reference directly. Paste it into the Code node on each branch, adjusting the custom field names to match what your Asana project uses.

// n8n Code Node — Asana Sprint Data Parser
// Runs after HTTP Request node fetching full task details
// $input.all() returns array of items from upstream node

// n8n Code Node — Asana Sprint Data Parser
// Runs after HTTP Request node fetching full task details
// $input.all() returns array of items from upstream node

const items = $input.all();
const results = [];

for (const item of items) {
  const task = item.json.data;

  // Asana custom_fields is an unordered array — find by name, not index
  const customFields = task.custom_fields || [];

  const storyPointsField = customFields.find(
    f => f.name === 'Story Points'
  );
  const capacityField = customFields.find(
    f => f.name === 'Capacity %'
  );

  const storyPoints = storyPointsField
    ? parseInt(storyPointsField.display_value, 10) || 0
    : 0;

  const capacity = capacityField
    ? capacityField.display_value || 'N/A'
    : 'N/A';

  // Format due date from YYYY-MM-DD to human-readable
  const rawDue = task.due_on || null;
  const formattedDue = rawDue
    ? new Date(rawDue + 'T00:00:00').toLocaleDateString('en-US', {
        month: 'short',
        day: 'numeric',
        year: 'numeric'
      })
    : 'No due date';

  // Pre-build Slack message text so the Slack node stays simple
  const isCompleted = task.completed === true;
  const emoji = isCompleted ? '✅' : '🚀';
  const status = isCompleted ? 'Sprint complete' : 'Sprint started';

  const slackText =
    `${emoji} ${status}: ${task.name}\n` +
    `Owner: ${task.assignee ? task.assignee.name : 'Unassigned'}\n` +
    `Due: ${formattedDue}\n` +
    `Story Points: ${storyPoints}\n` +
    `Team Capacity: ${capacity}`;

  results.push({
    json: {
      taskName: task.name,
      assigneeName: task.assignee ? task.assignee.name : 'Unassigned',
      dueOn: formattedDue,
      storyPoints,
      capacity,
      isCompleted,
      slackText
    }
  });
}

return results;

n8n Canvas > + Node > Core > HTTP Request

Fetch sprint-level summary from the Asana project

For sprint completion summaries, you need project-level stats — total tasks, completed count, incomplete count. Add another HTTP Request node calling GET https://app.asana.com/api/1.0/projects/{project_gid}/tasks?opt_fields=completed,name&completed_since=now. This returns only incomplete tasks. Run a second call without the filter to get total count. Wire both calls after the Code node on the completion branch.

1. 1Add HTTP Request node after Code node on the 'completed' branch
2. 2GET https://app.asana.com/api/1.0/projects/YOUR_PROJECT_GID/tasks?opt_fields=completed,name
3. 3Add a second HTTP Request node with the same URL plus &completed_since=now to fetch only incomplete tasks
4. 4Connect both nodes into a Merge node set to 'Combine > Merge By Position'
5. 5Use an expression in the next Code node to calculate: total - incomplete = completed count

n8n Canvas > + Node > Apps > Slack > Post Message

Configure the Slack node for sprint start announcements

Connect a Slack node to Switch branch 2 (the 'In Progress' section trigger). In n8n, search for the Slack node and select 'Post Message' as the operation. Choose the OAuth2 credential you'll set up in the credentials panel. Set the channel to your sprint channel ID (not the name — use the ID from Slack's channel settings). Build the message text using n8n expressions referencing your Code node output.

1. 1Click '+' on the sprint start branch and search for 'Slack'
2. 2Select operation 'Post a Message'
3. 3Click 'Create New Credential' and authenticate with Slack OAuth2
4. 4Set Channel to the Slack channel ID (e.g. C04XXXXXXX)
5. 5Set Text to: 🚀 Sprint started: {{ $node['Code'].json.taskName }} | Assignee: {{ $node['Code'].json.assigneeName }} | Due: {{ $node['Code'].json.dueOn }}

n8n Canvas > + Node > Apps > Slack > Post Message

Configure Slack nodes for sprint completion and blocker alerts

Add two more Slack 'Post Message' nodes — one for each remaining Switch branch. For sprint completion, use Slack's Block Kit format to post a structured summary card with task counts, story points completed, and team capacity. For blocker alerts, post to a separate #blockers channel (or the same sprint channel with a 🚧 emoji prefix). Each node references its own upstream Code node output.

1. 1Add Slack node to the 'completed' branch, operation 'Post a Message'
2. 2Set message body using JSON Blocks field with a Block Kit section block
3. 3Add Slack node to the 'blocker' branch, set Channel to #blockers channel ID
4. 4Set Text to: 🚧 Blocker flagged: {{ $node['Code'].json.taskName }} | Owner: {{ $node['Code'].json.assigneeName }}
5. 5Test each branch independently by manually sending a matching Asana event

n8n Settings > Error Workflow > + New Error Workflow

Add error handling with an Error Trigger node

Sprint notifications that silently fail are worse than no automation. Add an Error Trigger workflow in n8n: go to Settings > Error Workflow and create a separate workflow that catches failures from this one. The Error Trigger node captures the error message, the node name that failed, and the execution ID. Wire it to a Slack node that posts to a #dev-alerts channel so someone knows immediately when the Asana webhook or API call breaks.

1. 1Click the workflow name at the top of your canvas to open workflow settings
2. 2Scroll to 'Error Workflow' and click 'Create Error Workflow'
3. 3On the new canvas, add an Error Trigger node
4. 4Add a Slack node after it: Text = '❌ Sprint sync failed at node: {{ $json.failedNode }} | Error: {{ $json.errorMessage }}'
5. 5Save and link this workflow back to the main workflow's Error Workflow setting

n8n Canvas > Workflow Active Toggle (top right)

Activate the workflow and switch to the Production webhook URL

During testing you used the Test webhook URL. Now click the toggle in the top right of n8n to activate the workflow. Once activated, n8n switches to the Production webhook URL automatically — but Asana is still pointed at the Test URL. Go back to the Asana Webhooks API, delete the old webhook using DELETE https://app.asana.com/api/1.0/webhooks/{webhook_gid}, and re-register using the Production URL from n8n's Webhook node settings.

1. 1Click the 'Inactive' toggle in the top right to set workflow to 'Active'
2. 2Open the Webhook node and copy the Production URL (not the Test URL)
3. 3DELETE the old Asana webhook via API: DELETE https://app.asana.com/api/1.0/webhooks/OLD_GID
4. 4Re-register a new Asana webhook with the Production URL
5. 5Trigger a real Asana event (mark a task complete) and confirm the Slack message arrives