How to Send Weekly Todoist Reports to Slack with n8n

n8n Dashboard > + New Workflow

Create a new n8n workflow

Open your n8n instance and click the '+ New Workflow' button in the top-right corner of the dashboard. Give it a clear name like 'Weekly Todoist → Slack Report'. You'll land on an empty canvas with a single gray 'Add first step' node in the center. Everything you build will chain off this canvas left-to-right.

1. 1Click '+ New Workflow' in the top-right of the n8n dashboard
2. 2Click the pencil icon next to 'My workflow' at the top and rename it 'Weekly Todoist → Slack Report'
3. 3Click 'Save' in the top-right to register the name

Canvas > Add first step > Schedule Trigger

Add a Schedule trigger

Click the gray 'Add first step' node on the canvas. In the node picker that slides in from the right, search for 'Schedule' and select the 'Schedule Trigger' node. Set the trigger to run every Friday at 4:00 PM in your team's local timezone — this is critical to get right before anything else. The Schedule Trigger uses cron syntax under the hood; n8n exposes a dropdown UI for common intervals so you don't need to write raw cron.

1. 1Click the gray 'Add first step' node
2. 2Type 'Schedule' in the search box and select 'Schedule Trigger'
3. 3Set 'Trigger Interval' to 'Weeks'
4. 4Set 'Day of Week' to 'Friday'
5. 5Set 'Hour' to '16' and 'Minute' to '0'
6. 6Set 'Timezone' to your team's local timezone from the dropdown

Todoist Web App > Settings > Integrations > Developer > API token

Connect Todoist credentials

Add a new node after the Schedule Trigger by clicking the '+' connector on its right edge. Search for 'Todoist' and select the 'Todoist' node. In the node settings, click 'Credential for Todoist API' and then '+ Create New Credential'. n8n will prompt you to paste a Todoist API token. You get this from Todoist's web app under Settings > Integrations > Developer.

1. 1Click the '+' connector on the right edge of the Schedule Trigger node
2. 2Search 'Todoist' and click the Todoist node
3. 3Click 'Credential for Todoist API' dropdown then '+ Create New Credential'
4. 4Open Todoist in another tab: Settings > Integrations > Developer, copy your API token
5. 5Paste the token into n8n's credential field and click 'Save'

Todoist Node > Resource: Task > Operation: Get All

Fetch completed tasks from the past 7 days

With the Todoist node open, set 'Resource' to 'Task' and 'Operation' to 'Get All'. You need to filter by completion status and date range. Todoist's REST API v2 doesn't support completed task queries directly — you must use the Sync API endpoint via an HTTP Request node instead (see Step 5). For now, set this node's Operation to 'Get All' with 'Filter' set to 'today' just to confirm auth works, then you'll replace it.

1. 1Set 'Resource' to 'Task'
2. 2Set 'Operation' to 'Get All'
3. 3Click 'Test step' to confirm tasks load
4. 4Verify your projects appear in the output panel on the right

Canvas > HTTP Request Node > Parameters

Fetch completed tasks via Todoist Sync API

Delete the Todoist node from Step 4 and replace it with an 'HTTP Request' node connected directly to the Schedule Trigger. The Todoist Sync API endpoint for completed tasks is https://api.todoist.com/sync/v9/items/completed/get_all. You'll pass your API token as a Bearer token in the Authorization header and set since as a query parameter calculated 7 days back from today. Use n8n's expression editor to compute the date dynamically.

1. 1Add an HTTP Request node after the Schedule Trigger
2. 2Set 'Method' to 'GET'
3. 3Set 'URL' to 'https://api.todoist.com/sync/v9/items/completed/get_all'
4. 4Under 'Authentication', select 'Generic Credential Type', choose 'Header Auth', set Header Name to 'Authorization' and Header Value to 'Bearer YOUR_TODOIST_TOKEN'
5. 5Add Query Parameter: Name = 'since', Value = '{{ $now.minus({days: 7}).toISO() }}'
6. 6Add Query Parameter: Name = 'limit', Value = '200'
7. 7Click 'Test step'

Canvas > Code Node > JavaScript

Extract and aggregate completions by project

Add a 'Code' node after the HTTP Request node. This is where you process the raw API response into a structured summary. The Sync API returns a nested JSON object, so you need to access items.items (double-nested). Write JavaScript to count completions per project_id, then map project IDs to human-readable names. See the Pro Tip code section for the full transformation script.

1. 1Click '+' after the HTTP Request node and search for 'Code'
2. 2Select 'Code' node and set 'Language' to 'JavaScript'
3. 3Set 'Mode' to 'Run Once for All Items'
4. 4Paste the aggregation script from the Pro Tip section into the code editor
5. 5Click 'Test step' and verify the output shows one item per project with a count field

Canvas > HTTP Request Node (second) > REST v2 Projects endpoint

Fetch project names from Todoist

The Sync API returns project_id values, not names. Add a second HTTP Request node before the Code node (between Steps 5 and 6) to fetch all projects. Use GET https://api.todoist.com/rest/v2/projects with the same Bearer token. This returns an array of project objects with id and name fields. Pass this data into the Code node alongside the completed tasks so you can do the ID-to-name lookup inside one Code node.

1. 1Add a second HTTP Request node between the completed-tasks node and the Code node
2. 2Set Method to 'GET', URL to 'https://api.todoist.com/rest/v2/projects'
3. 3Add the same Bearer token Authorization header
4. 4In the Code node, reference this node's output using $('HTTP Request Projects').all()

api.slack.com/apps > Your App > OAuth & Permissions > Bot Token Scopes

Connect Slack credentials

Add a Slack node after the Code node. Click 'Credential for Slack API' and select '+ Create New Credential'. Choose 'OAuth2' as the auth type — n8n will walk you through authorizing a Slack app. If you don't have a Slack app yet, you'll need to create one at api.slack.com/apps, add the chat:write and channels:read scopes, install it to your workspace, and paste the Bot OAuth Token into n8n.

1. 1Add a Slack node after the Code node
2. 2Click 'Credential for Slack API' > '+ Create New Credential'
3. 3Go to api.slack.com/apps and create or open your existing Slack app
4. 4Under 'OAuth & Permissions', add scopes: chat:write, channels:read
5. 5Click 'Install to Workspace' and copy the 'Bot User OAuth Token'
6. 6Paste the token into n8n's Slack credential field and click 'Save'

Slack Node > Resource: Message > Operation: Post > Channel + Text

Format and send the Slack message

In the Slack node, set 'Resource' to 'Message' and 'Operation' to 'Post'. Set 'Channel' to the channel ID or name where leadership reviews updates (e.g., #leadership-updates). For the message body, use n8n's expression editor to build a formatted string from the Code node's output. Use Slack's Block Kit or a plain mrkdwn text block with *bold* project names and task counts on separate lines.

1. 1Set 'Resource' to 'Message' and 'Operation' to 'Post'
2. 2Set 'Channel' to your target channel name or ID
3. 3Set 'Text' to a dynamic expression referencing the Code node output (see Pro Tip for the full formatter)
4. 4Enable 'Blocks' if you want structured Block Kit layout instead of plain text
5. 5Click 'Test step' to send a test message to the channel

Node Settings > Continue on Fail | Canvas > Error Branch > Slack Alert Node

Add error handling with a fallback notification

Click the Slack node, then open the 'Settings' tab inside the node panel. Enable 'Continue on Fail' to prevent the workflow from silently dying if Slack rejects the message. Add a separate Slack node connected to the error output of the Code node and the HTTP Request nodes — this fallback node sends a plain alert to a #alerts channel if the data fetch fails. This takes 5 extra minutes and saves you from missing a report without knowing why.

1. 1Click the Code node, open the 'Settings' tab, enable 'Continue on Fail'
2. 2Do the same for both HTTP Request nodes
3. 3Hover over the Code node and click the red error output connector
4. 4Add a Slack node on the error branch
5. 5Set its channel to '#alerts' and text to 'Weekly Todoist report failed — check n8n workflow logs'

Canvas > Top-right toggle > Active | Executions tab

Activate the workflow

Click the gray 'Inactive' toggle in the top-right of the canvas and flip it to 'Active'. n8n will now run this workflow automatically every Friday at 4:00 PM in your configured timezone. The first real execution happens at the next scheduled Friday — click 'Execute Workflow' manually now to confirm everything works end-to-end before then. Check the Executions tab to review the full run log.

1. 1Click 'Save' to save the current workflow state
2. 2Click 'Execute Workflow' to run it manually right now
3. 3Verify the Slack message appears in your target channel
4. 4Click the 'Inactive' toggle to switch it to 'Active'
5. 5Open the Executions tab and confirm the manual run shows a green success status

Paste this into the Code node (set to 'Run Once for All Items'). It pulls completed tasks from the Sync API node, fetches project names from the separate REST v2 node, groups completions by project, builds the formatted Slack message string, and returns a single item containing the final text ready for the Slack node.

// Node names assumed:
// 'HTTP Completed Tasks' = Sync API response
// 'HTTP Projects' = REST v2 projects list

// Node names assumed:
// 'HTTP Completed Tasks' = Sync API response
// 'HTTP Projects' = REST v2 projects list

const completedRaw = $('HTTP Completed Tasks').all();
const projectsRaw = $('HTTP Projects').all();

// Extract the items array from the Sync API response
const tasks = completedRaw[0].json.items || [];

// Build a project ID → name lookup map
const projectMap = {};
for (const p of projectsRaw[0].json) {
  projectMap[p.id] = p.name;
}

// Group tasks by project_id
const grouped = {};
for (const task of tasks) {
  const pid = task.project_id;
  if (!grouped[pid]) {
    grouped[pid] = { name: projectMap[pid] || `Project ${pid}`, tasks: [] };
  }
  grouped[pid].tasks.push(task.content);
}

// Calculate week range label
const now = new Date();
const weekStart = new Date(now);
weekStart.setDate(now.getDate() - 7);
const fmt = (d) => d.toLocaleDateString('en-US', { month: 'short', day: 'numeric', year: 'numeric' });
const weekLabel = `${fmt(weekStart)} – ${fmt(now)}`;

// Build Slack message text
let totalCount = 0;
let lines = [`*Weekly Progress Report — ${weekLabel}*\n`];

for (const pid of Object.keys(grouped)) {
  const proj = grouped[pid];
  const count = proj.tasks.length;
  totalCount += count;
  lines.push(`*${proj.name}* — ${count} task${count !== 1 ? 's' : ''} completed`);
  for (const t of proj.tasks) {
    lines.push(`  • ${t}`);
  }
  lines.push('');
}

lines.push(`*Total: ${totalCount} task${totalCount !== 1 ? 's' : ''} completed this week*`);

return [{ json: { slackMessage: lines.join('\n') } }];