How to Send Weekly Todoist Reports to Slack with Pipedream

pipedream.com > Workflows > New Workflow

Create a new Pipedream Workflow

Go to pipedream.com and click 'Workflows' in the left sidebar. Click the green 'New Workflow' button in the top right corner. Pipedream will open a blank workflow canvas with an empty trigger slot at the top. Give the workflow a name — something like 'Weekly Todoist Report to Slack' — by clicking the default name at the top of the canvas.

1. 1Log in at pipedream.com
2. 2Click 'Workflows' in the left navigation
3. 3Click the green 'New Workflow' button
4. 4Click the workflow name at the top and rename it to 'Weekly Todoist Report to Slack'

Workflow Canvas > Add Trigger > Schedule > Cron Scheduler

Set a Schedule Trigger

Click the 'Add Trigger' block. In the trigger selector panel that slides in from the right, search for 'Schedule' and select it. Choose 'Cron Scheduler' as the trigger type. Enter the cron expression '0 8 * * 1' — this fires every Monday at 8:00 AM UTC. Adjust the timezone field if your leadership team is not on UTC.

1. 1Click the 'Add Trigger' block
2. 2Type 'Schedule' in the search box
3. 3Select 'Schedule' from the results
4. 4Choose 'Cron Scheduler' as the schedule type
5. 5Enter '0 8 * * 1' in the cron expression field

Workflow Canvas > + Add Step > App > Todoist > Get Completed Tasks

Connect Your Todoist Account

Click '+ Add Step' below the trigger and select 'App' from the step type options. Search for 'Todoist' in the app selector. Choose the action 'Get Completed Tasks' (also listed as 'Get all completed items' depending on the component version). In the step configuration panel, click 'Connect Todoist Account' and follow the OAuth flow. Todoist will ask you to authorize Pipedream — accept all requested scopes.

1. 1Click '+ Add Step' below the Schedule trigger
2. 2Select 'App' as the step type
3. 3Search for 'Todoist' and select it
4. 4Choose the action 'Get Completed Tasks'
5. 5Click 'Connect Todoist Account' and complete the OAuth flow in the popup

Workflow Canvas > Todoist Step > Configure > Since / Until fields

Configure the Todoist Date Range Parameters

In the Todoist step, you need to pass dynamic date values for 'Since' and 'Until' so the query always covers the last 7 days. Click the 'Since' field and switch to expression mode (click the '{{ }}' toggle). Enter a JavaScript expression to calculate last Monday's date. Leave 'Project ID' blank to fetch completions across all projects, or enter a specific project ID to narrow the scope. Set 'Limit' to 200 to avoid missing tasks in busy weeks.

1. 1Click the 'Since' field in the Todoist step
2. 2Click the '{{ }}' expression toggle to enable dynamic values
3. 3Enter the expression for 7 days ago (handled in the code step next — leave this as a static value for now: the prior Monday's ISO date)
4. 4Leave 'Project ID' blank for all projects or paste a specific project ID
5. 5Set 'Limit' to 200

Workflow Canvas > + Add Step > Run Node.js code

Add a Node.js Code Step to Aggregate Task Data

Click '+ Add Step' and select 'Run Node.js code'. This is where you transform the raw Todoist API response into a structured summary grouped by project. Paste the code from the Pro Tip section into the code editor. The script pulls the completed task array from the previous step, groups tasks by project name, counts completions per project, calculates a total, and assembles the Slack message payload. Click 'Test' to run it against real data before moving on.

1. 1Click '+ Add Step' below the Todoist step
2. 2Select 'Run Node.js code'
3. 3Delete the placeholder code in the editor
4. 4Paste the aggregation code from the Pro Tip section
5. 5Click 'Test' to validate the output

Paste this into the Node.js code step (Step 3 in your workflow). It pulls the completed tasks array from the Todoist step output, resolves project IDs to names using a second Todoist API call, groups and counts by project, then builds a Slack Block Kit payload ready to drop into the Slack step's Blocks field.

import axios from 'axios';
export default defineComponent({
  async run({ steps, $ }) {

import axios from 'axios';

export default defineComponent({
  async run({ steps, $ }) {
    // Pull completed tasks from previous Todoist step
    const completedItems = steps.todoist.$return_value?.items || [];

    if (completedItems.length === 0) {
      // Post a fallback message rather than an empty report
      return {
        totalCompleted: 0,
        byProject: [],
        slackBlocks: [
          {
            type: 'header',
            text: { type: 'plain_text', text: '📋 Weekly Progress Report', emoji: true }
          },
          {
            type: 'section',
            text: { type: 'mrkdwn', text: 'No tasks were completed in Todoist this week.' }
          }
        ]
      };
    }

    // Fetch project names from Todoist API to resolve IDs to labels
    const todoist_token = process.env.TODOIST_API_TOKEN;
    let projectMap = {};
    try {
      const projectsResp = await axios.get('https://api.todoist.com/rest/v2/projects', {
        headers: { Authorization: `Bearer ${todoist_token}` }
      });
      for (const project of projectsResp.data) {
        projectMap[project.id] = project.name;
      }
    } catch (err) {
      console.error('Failed to fetch Todoist projects:', err.message);
      // Continue with raw IDs if lookup fails
    }

    // Group completions by project
    const projectCounts = {};
    for (const item of completedItems) {
      const projectName = projectMap[item.project_id] || `Project ${item.project_id}`;
      projectCounts[projectName] = (projectCounts[projectName] || 0) + 1;
    }

    const totalCompleted = completedItems.length;
    const byProject = Object.entries(projectCounts)
      .sort((a, b) => b[1] - a[1])
      .map(([name, count]) => ({ name, count }));

    // Build date range label
    const now = new Date();
    const lastMonday = new Date(now);
    lastMonday.setDate(now.getDate() - 7);
    const dateLabel = `${lastMonday.toLocaleDateString('en-US', { month: 'short', day: 'numeric' })}–${now.toLocaleDateString('en-US', { month: 'short', day: 'numeric', year: 'numeric' })}`;

    // Build Slack Block Kit payload
    const projectLines = byProject
      .map(p => `• *${p.name}* — ${p.count} task${p.count !== 1 ? 's' : ''} completed`)
      .join('\n');

    const slackBlocks = [
      {
        type: 'header',
        text: { type: 'plain_text', text: `📋 Weekly Progress Report — ${dateLabel}`, emoji: true }
      },
      { type: 'divider' },
      {
        type: 'section',
        text: { type: 'mrkdwn', text: projectLines }
      },
      { type: 'divider' },
      {
        type: 'section',
        text: { type: 'mrkdwn', text: `*Total completed this week: ${totalCompleted} task${totalCompleted !== 1 ? 's' : ''}*` }
      },
      {
        type: 'context',
        elements: [{ type: 'mrkdwn', text: `Generated automatically by Pipedream · ${new Date().toISOString()}` }]
      }
    ];

    return { totalCompleted, byProject, slackBlocks };
  }
});

Workflow Canvas > + Add Step > App > Slack > Send Message

Connect Your Slack Account

Click '+ Add Step' and search for 'Slack'. Select the 'Send Message' action (or 'Send Block Kit Message' if you want rich formatting). Click 'Connect Slack Account' — this opens a Slack OAuth window asking you to select the workspace and approve the bot's permissions. You need at minimum the 'chat:write' scope. If you want the bot to post to private channels, you must invite it to those channels manually in Slack first.

1. 1Click '+ Add Step' below the code step
2. 2Search for 'Slack' and select it
3. 3Choose 'Send Message (Block Kit)' for formatted output
4. 4Click 'Connect Slack Account'
5. 5Select your workspace in the OAuth popup and click Allow

Workflow Canvas > Slack Step > Configure > Channel / Blocks fields

Configure the Slack Message Destination

In the Channel field, type the name of your target channel — for example '#leadership-updates'. You can also paste a channel ID (starts with 'C') for more reliability. In the Blocks field, reference the output from your code step using the expression '{{steps.code.$return_value.slackBlocks}}'. Set the 'Text' fallback field to something like 'Weekly Todoist Progress Report' for clients that don't render Block Kit.

1. 1Type your channel name (e.g. '#leadership-updates') in the Channel field
2. 2Click the Blocks field and switch to expression mode with '{{ }}'
3. 3Enter '{{steps.code.$return_value.slackBlocks}}' to reference the formatted payload
4. 4Set the Text fallback field to 'Weekly Todoist Progress Report'

Workflow Canvas > Run Now button (top right)

Test the Full Workflow End-to-End

Click 'Run Now' at the top of the workflow canvas to trigger a manual test run (this bypasses the Monday schedule and fires immediately). Watch each step turn green in sequence. Click the Todoist step to inspect the raw API response — confirm you see completed tasks in the 'items' array. Click the code step to verify the aggregated output. Click the Slack step to confirm it shows a 200 OK response from Slack.

1. 1Click the 'Run Now' button at the top right of the canvas
2. 2Watch each step indicator — green means success, red means error
3. 3Click the Todoist step result to inspect the raw 'items' array
4. 4Click the code step result to verify 'totalCompleted' and 'byProject' values
5. 5Check your Slack channel to confirm the message appeared

Workflow Canvas > Node.js Code Step > Edit code

Add Error Handling to the Code Step

Go back to your Node.js code step. Wrap the main logic in a try/catch block. In the catch block, use $.send.http or log the error — but more practically, add a fallback Slack notification so leadership knows the report failed instead of just silently not appearing. Update the step to export an error flag if the Todoist response is empty or malformed. This prevents silent failures on weeks where the API is slow.

1. 1Click the code step to open the editor
2. 2Wrap your main logic in a try/catch block
3. 3In the catch block, throw a descriptive error with $.flow.exit() or re-throw to halt the workflow
4. 4Add a check for empty 'items' array and return an early 'No completed tasks this week' message
5. 5Click 'Test' again to confirm the updated code still passes

Paste this into the Node.js code step (Step 3 in your workflow). It pulls the completed tasks array from the Todoist step output, resolves project IDs to names using a second Todoist API call, groups and counts by project, then builds a Slack Block Kit payload ready to drop into the Slack step's Blocks field.

import axios from 'axios';
export default defineComponent({
  async run({ steps, $ }) {

import axios from 'axios';

export default defineComponent({
  async run({ steps, $ }) {
    // Pull completed tasks from previous Todoist step
    const completedItems = steps.todoist.$return_value?.items || [];

    if (completedItems.length === 0) {
      // Post a fallback message rather than an empty report
      return {
        totalCompleted: 0,
        byProject: [],
        slackBlocks: [
          {
            type: 'header',
            text: { type: 'plain_text', text: '📋 Weekly Progress Report', emoji: true }
          },
          {
            type: 'section',
            text: { type: 'mrkdwn', text: 'No tasks were completed in Todoist this week.' }
          }
        ]
      };
    }

    // Fetch project names from Todoist API to resolve IDs to labels
    const todoist_token = process.env.TODOIST_API_TOKEN;
    let projectMap = {};
    try {
      const projectsResp = await axios.get('https://api.todoist.com/rest/v2/projects', {
        headers: { Authorization: `Bearer ${todoist_token}` }
      });
      for (const project of projectsResp.data) {
        projectMap[project.id] = project.name;
      }
    } catch (err) {
      console.error('Failed to fetch Todoist projects:', err.message);
      // Continue with raw IDs if lookup fails
    }

    // Group completions by project
    const projectCounts = {};
    for (const item of completedItems) {
      const projectName = projectMap[item.project_id] || `Project ${item.project_id}`;
      projectCounts[projectName] = (projectCounts[projectName] || 0) + 1;
    }

    const totalCompleted = completedItems.length;
    const byProject = Object.entries(projectCounts)
      .sort((a, b) => b[1] - a[1])
      .map(([name, count]) => ({ name, count }));

    // Build date range label
    const now = new Date();
    const lastMonday = new Date(now);
    lastMonday.setDate(now.getDate() - 7);
    const dateLabel = `${lastMonday.toLocaleDateString('en-US', { month: 'short', day: 'numeric' })}–${now.toLocaleDateString('en-US', { month: 'short', day: 'numeric', year: 'numeric' })}`;

    // Build Slack Block Kit payload
    const projectLines = byProject
      .map(p => `• *${p.name}* — ${p.count} task${p.count !== 1 ? 's' : ''} completed`)
      .join('\n');

    const slackBlocks = [
      {
        type: 'header',
        text: { type: 'plain_text', text: `📋 Weekly Progress Report — ${dateLabel}`, emoji: true }
      },
      { type: 'divider' },
      {
        type: 'section',
        text: { type: 'mrkdwn', text: projectLines }
      },
      { type: 'divider' },
      {
        type: 'section',
        text: { type: 'mrkdwn', text: `*Total completed this week: ${totalCompleted} task${totalCompleted !== 1 ? 's' : ''}*` }
      },
      {
        type: 'context',
        elements: [{ type: 'mrkdwn', text: `Generated automatically by Pipedream · ${new Date().toISOString()}` }]
      }
    ];

    return { totalCompleted, byProject, slackBlocks };
  }
});

Workflow Canvas > Active/Inactive toggle (top right)

Activate the Workflow

Toggle the workflow from 'Inactive' to 'Active' using the switch in the top right of the canvas. Pipedream will confirm activation and show the next scheduled run time. Verify the next run shows the upcoming Monday at your configured time. You can also check the 'Runs' tab to see historical executions once the first scheduled run fires.

1. 1Click the toggle switch at the top right of the canvas from 'Inactive' to 'Active'
2. 2Confirm the dialog if prompted
3. 3Check the trigger block — it should display the next scheduled run time
4. 4Navigate to the 'Runs' tab to monitor future executions