How to Post Todoist Standups to Slack with n8n

n8n Dashboard > Workflows > + New Workflow

Create a new n8n workflow

Open your n8n instance and click the '+ New Workflow' button in the top right of the Workflows dashboard. Give it a descriptive name like 'Daily Todoist Standup to Slack'. You'll land on the canvas with an empty workflow and a prompt to add your first node. This is where the scheduled trigger goes.

1. 1Click '+ New Workflow' in the top right corner
2. 2Click the workflow title at the top and rename it to 'Daily Todoist Standup to Slack'
3. 3Click '+ Add first step' in the center of the canvas

Canvas > Node Picker > Schedule Trigger

Add a Schedule trigger node

Search for 'Schedule Trigger' in the node picker and select it. In the node configuration panel, set the trigger interval to 'Cron Expression' for precise control. Enter the cron expression for your standup time — for 9:00 AM Monday through Friday, use '0 9 * * 1-5'. Click 'Save' on the node.

1. 1Type 'Schedule' in the node search box
2. 2Click 'Schedule Trigger' from the results
3. 3Set 'Trigger Interval' dropdown to 'Custom (Cron)'
4. 4Enter '0 9 * * 1-5' in the Cron Expression field
5. 5Click 'Save' to close the node panel

Canvas > + Node > Todoist > Task > Get Many

Connect Todoist and fetch today's tasks

Add a Todoist node after the Schedule Trigger. In the node picker, search 'Todoist' and select the Todoist node. Set the operation to 'Get Many' under the Task resource. You need to create a Todoist credential first — click 'Create New Credential', which opens an OAuth2 flow. Authorize n8n in the Todoist browser window that pops up. Once connected, set the Filter to 'Today' to pull only tasks due today.

1. 1Click the '+' connector on the Schedule Trigger node
2. 2Search 'Todoist' in the node picker and select it
3. 3Set Resource to 'Task' and Operation to 'Get Many'
4. 4Click 'Credential for Todoist API' > 'Create New Credential'
5. 5Complete the Todoist OAuth2 authorization in the popup window
6. 6Under Filters, set 'Filter' to 'Today'

Canvas > + Node > Code

Add a Code node to group tasks by assignee

The Todoist node returns a flat array of tasks. You need to group them by assignee so each person's tasks appear together in the Slack message. Add a Code node after Todoist. Paste the JavaScript from the Pro Tip section below into the code editor. This node outputs one item per team member with their tasks bundled, which the Slack node will iterate over.

1. 1Click '+' after the Todoist node
2. 2Search 'Code' in the node picker and select it
3. 3Set 'Mode' to 'Run Once for All Items'
4. 4Paste the grouping script into the code editor
5. 5Click 'Test Step' to verify the output structure

Paste this into the first Code node (set to 'Run Once for All Items'). It pulls the collaborators list from the previous HTTP Request node, builds an ID-to-name map, groups today's tasks by assignee, and returns one item per person with a pre-formatted Slack message string including priority emoji and clickable task links. The second part of the script (the message formatter) replaces the need for a separate formatting Code node.

// Node: Code — 'Group and Format Standup Messages'
// Mode: Run Once for All Items
// Expects: items from Todoist node, collaborators from HTTP Request node

// Node: Code — 'Group and Format Standup Messages'
// Mode: Run Once for All Items
// Expects: items from Todoist node, collaborators from HTTP Request node

const tasks = $('Todoist').all().map(item => item.json);
const collaborators = $('HTTP Request').all().map(item => item.json);

// Build ID → display name lookup
const nameMap = {};
for (const person of collaborators) {
  nameMap[String(person.id)] = person.name;
}

// Priority emoji map (Todoist: 4=urgent, 1=normal)
const priorityEmoji = { '4': '🔴', '3': '🟠', '2': '🟡', '1': '' };

// Group tasks by assignee_id
const grouped = {};
for (const task of tasks) {
  const assigneeKey = task.assignee_id ? String(task.assignee_id) : 'unassigned';
  if (!grouped[assigneeKey]) {
    grouped[assigneeKey] = [];
  }
  grouped[assigneeKey].push(task);
}

// Build one output item per assignee
const output = [];
for (const [assigneeId, assigneeTasks] of Object.entries(grouped)) {
  if (assigneeId === 'unassigned') continue; // skip unassigned tasks

  const displayName = nameMap[assigneeId] || `User ${assigneeId}`;

  // Sort by priority descending (4 first)
  const sorted = assigneeTasks.sort((a, b) => (b.priority || 1) - (a.priority || 1));

  // Format each task line
  const lines = sorted.map(task => {
    const emoji = priorityEmoji[String(task.priority)] || '';
    const link = task.url ? ` (<${task.url}|view>)` : '';
    const labels = task.labels && task.labels.length > 0
      ? ` [${task.labels.join(', ')}]`
      : '';
    return `• ${emoji} ${task.content}${labels}${link}`.trim();
  });

  const message = `*${displayName}*\n${lines.join('\n')}`;

  output.push({
    json: {
      assignee_id: assigneeId,
      assignee_name: displayName,
      task_count: assigneeTasks.length,
      message
    }
  });
}

// Sort output alphabetically by name for consistent Slack ordering
output.sort((a, b) => a.json.assignee_name.localeCompare(b.json.assignee_name));

return output;

Canvas > + Node > HTTP Request

Resolve assignee IDs to display names

If your team uses assignee_id in Todoist, add an HTTP Request node before the Code node to fetch project collaborators. Call GET https://api.todoist.com/rest/v2/projects/{project_id}/collaborators with your Todoist API token in the Authorization header. This returns an array of objects with id and name. Pass this data into the Code node so you can build the ID-to-name lookup map there.

1. 1Click '+' between the Todoist node and the Code node
2. 2Search 'HTTP Request' and select it
3. 3Set Method to 'GET'
4. 4Set URL to 'https://api.todoist.com/rest/v2/projects/YOUR_PROJECT_ID/collaborators'
5. 5Under Authentication, choose 'Header Auth' and add 'Authorization: Bearer YOUR_TODOIST_TOKEN'
6. 6Click 'Test Step' to confirm you receive a list of collaborators

Paste this into the first Code node (set to 'Run Once for All Items'). It pulls the collaborators list from the previous HTTP Request node, builds an ID-to-name map, groups today's tasks by assignee, and returns one item per person with a pre-formatted Slack message string including priority emoji and clickable task links. The second part of the script (the message formatter) replaces the need for a separate formatting Code node.

// Node: Code — 'Group and Format Standup Messages'
// Mode: Run Once for All Items
// Expects: items from Todoist node, collaborators from HTTP Request node

// Node: Code — 'Group and Format Standup Messages'
// Mode: Run Once for All Items
// Expects: items from Todoist node, collaborators from HTTP Request node

const tasks = $('Todoist').all().map(item => item.json);
const collaborators = $('HTTP Request').all().map(item => item.json);

// Build ID → display name lookup
const nameMap = {};
for (const person of collaborators) {
  nameMap[String(person.id)] = person.name;
}

// Priority emoji map (Todoist: 4=urgent, 1=normal)
const priorityEmoji = { '4': '🔴', '3': '🟠', '2': '🟡', '1': '' };

// Group tasks by assignee_id
const grouped = {};
for (const task of tasks) {
  const assigneeKey = task.assignee_id ? String(task.assignee_id) : 'unassigned';
  if (!grouped[assigneeKey]) {
    grouped[assigneeKey] = [];
  }
  grouped[assigneeKey].push(task);
}

// Build one output item per assignee
const output = [];
for (const [assigneeId, assigneeTasks] of Object.entries(grouped)) {
  if (assigneeId === 'unassigned') continue; // skip unassigned tasks

  const displayName = nameMap[assigneeId] || `User ${assigneeId}`;

  // Sort by priority descending (4 first)
  const sorted = assigneeTasks.sort((a, b) => (b.priority || 1) - (a.priority || 1));

  // Format each task line
  const lines = sorted.map(task => {
    const emoji = priorityEmoji[String(task.priority)] || '';
    const link = task.url ? ` (<${task.url}|view>)` : '';
    const labels = task.labels && task.labels.length > 0
      ? ` [${task.labels.join(', ')}]`
      : '';
    return `• ${emoji} ${task.content}${labels}${link}`.trim();
  });

  const message = `*${displayName}*\n${lines.join('\n')}`;

  output.push({
    json: {
      assignee_id: assigneeId,
      assignee_name: displayName,
      task_count: assigneeTasks.length,
      message
    }
  });
}

// Sort output alphabetically by name for consistent Slack ordering
output.sort((a, b) => a.json.assignee_name.localeCompare(b.json.assignee_name));

return output;

Canvas > + Node > Code (second instance)

Format the Slack message with a Function node

After the Code node that groups tasks, add another Code node to build the final Slack Block Kit message payload. This step takes each grouped assignee item and converts it into a Slack-formatted string with bold names and bulleted task lists. Run this node in 'Run Once for Each Item' mode so it processes one assignee at a time and outputs one Slack message per person.

1. 1Click '+' after the grouping Code node
2. 2Add another Code node
3. 3Set Mode to 'Run Once for Each Item'
4. 4Write the message formatting logic (see Pro Tip code)
5. 5Click 'Test Step' and inspect one output item to confirm the message string looks correct

Canvas > + Node > Slack > Message > Send

Add a Slack node to post each message

Add a Slack node after the formatting Code node. Set the resource to 'Message' and operation to 'Send'. Create a Slack credential using OAuth2 — click 'Create New Credential' and authorize n8n inside your Slack workspace. Set the Channel field to your standup channel ID (not the display name — use the channel ID starting with 'C'). Map the 'Text' field to the 'message' output from the previous Code node using the expression editor.

1. 1Click '+' after the second Code node
2. 2Search 'Slack' and select it
3. 3Set Resource to 'Message', Operation to 'Send'
4. 4Click 'Credential for Slack API' > 'Create New Credential' and complete OAuth2
5. 5In the Channel field, click the expression toggle (the '=' icon) and enter your channel ID
6. 6In the Text field, click the expression toggle and select 'message' from the previous node output

Canvas > + Node > Slack > Message > Send (header)

Add a header message to open the standup thread

Before the per-person Slack messages, post a single header message to the channel to frame the standup. Add a Slack node immediately after the Schedule Trigger (parallel to the Todoist fetch, or in sequence before it). Set the text to something like ':clipboard: *Daily Standup — {{$now.toFormat('EEEE, MMMM d')}}*'. This gives the thread a clear timestamp and makes it easy to search in Slack history.

1. 1Click '+' after the Schedule Trigger to insert a new node before Todoist
2. 2Add a Slack node set to Message > Send
3. 3In the Text field, enter ':clipboard: *Daily Standup — {{$now.toFormat('EEEE, MMMM d')}}*'
4. 4Use the same channel ID as the per-person messages
5. 5Connect the output of this Slack node to the Todoist node

Canvas > + Node > IF

Handle the no-tasks edge case

If a team member has no tasks due today, the grouping Code node may produce an empty tasks array for them. Add an IF node after the grouping Code node to check whether tasks.length is greater than 0. Route the 'true' branch to the formatting and Slack nodes. Route the 'false' branch to a No-Op node or skip entirely. This prevents sending empty standup entries like '*Maria Chen*\n(no tasks today)' unless you intentionally want that.

1. 1Click '+' after the grouping Code node
2. 2Search 'IF' and select the IF node
3. 3Set Condition: Value 1 = '{{$json.tasks.length}}', Operation = 'Greater Than', Value 2 = '0'
4. 4Connect the 'true' output to the formatting Code node
5. 5Connect the 'false' output to a No Operation node to terminate that branch cleanly

Canvas > Test Workflow > Active Toggle

Activate and test the full workflow

Click 'Test Workflow' at the bottom of the canvas to run the entire flow end-to-end with live data. Watch the execution log — each node should show a green checkmark and the execution count. Open Slack and verify the standup messages arrived in the correct channel. Once confirmed, toggle the workflow to 'Active' using the switch in the top right corner of the canvas. The workflow will now fire automatically every weekday at your configured time.

1. 1Click 'Test Workflow' at the bottom toolbar
2. 2Watch each node highlight green as it executes
3. 3Open Slack and confirm messages appear in your standup channel
4. 4Click the 'Inactive' toggle in the top right to switch it to 'Active'
5. 5Confirm the toggle shows 'Active' in green