How to Post Todoist Standups to Slack with Pipedream

pipedream.com > Workflows > New Workflow

Create a new Pipedream workflow

Go to pipedream.com and sign in. Click 'New Workflow' in the top-right corner of the dashboard. Give it a clear name like 'Daily Standup — Todoist to Slack'. You'll land on the workflow canvas with an empty trigger slot at the top.

1. 1Click the blue 'New Workflow' button in the top-right
2. 2Type 'Daily Standup — Todoist to Slack' in the workflow name field
3. 3Press Enter or click the checkmark to save the name
4. 4Click the '+ Add Trigger' block at the top of the canvas

Trigger Panel > Search > Schedule > Every Day

Set a daily schedule trigger

In the trigger panel, search for 'Schedule' and select the 'Schedule' source. Choose 'Every day' from the frequency dropdown. Set the time to 9:00 AM and select your team's timezone — this is critical for international teams. Pipedream runs the schedule in UTC by default until you change it.

1. 1Type 'Schedule' in the trigger search box
2. 2Click 'Schedule' under the 'Core' category
3. 3Select 'Every Day' from the frequency dropdown
4. 4Set the time field to '09:00'
5. 5Open the timezone dropdown and select your team's local timezone (e.g., 'America/New_York')

Workflow Canvas > + Add Step > Todoist > Get Active Tasks

Connect your Todoist account

Click '+ Add Step' below the trigger and search for 'Todoist'. Select the 'Get Active Tasks' action (action key: todoist-get-active-tasks). In the step configuration panel, click 'Connect Account' and authenticate with your Todoist credentials. You'll need a Todoist account that has access to the projects you want to pull from.

1. 1Click '+ Add Step' directly below the trigger block
2. 2Type 'Todoist' in the app search field
3. 3Select 'Todoist' from the results
4. 4Choose the 'Get Active Tasks' action
5. 5Click 'Connect Account' and complete the OAuth login

Todoist Step > Configuration > Filter Field

Filter tasks by project or assignee

In the Todoist 'Get Active Tasks' step, find the 'Filter' field. Todoist's REST API accepts filter strings like 'today | overdue' to limit which tasks come back. Type your filter string here. If your team members each own a Todoist project, you can also set 'Project ID' to pull from a specific project. Run a test now — click 'Test' at the bottom of the step — to confirm tasks return.

1. 1Click inside the 'Filter' input field in the Todoist step
2. 2Type 'today | overdue' to capture due-today and overdue tasks
3. 3Optionally set 'Project ID' if you want to scope tasks to one project
4. 4Click the 'Test' button at the bottom of the step
5. 5Expand the returned array to confirm your tasks appear in the output

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

Add a Node.js code step to format the standup message

Click '+ Add Step' and choose 'Run Node.js code'. This is where you transform the raw Todoist task array into a readable Slack message. You'll map task content, priority, and due date into a formatted string. Paste the code from the Pro Tip section below directly into this step's code editor. The code groups tasks by priority and assembles a Block Kit-friendly Slack message payload.

1. 1Click '+ Add Step' below the Todoist step
2. 2Select 'Run Node.js code' from the step type list
3. 3Clear the default boilerplate from the editor
4. 4Paste your formatting code into the editor
5. 5Click 'Test' to confirm the output includes a formatted 'blocks' array

Paste this into your Node.js code step (Step 5 on the canvas). It reads the Todoist task array from the previous step's output, maps priority numbers to labels, flags overdue tasks, groups everything by priority, and returns a Slack Block Kit blocks array ready to drop into the Slack Send Message step.

export default defineComponent({
  async run({ steps, $ }) {
    const tasks = steps.todoist_get_active_tasks.$return_value;

export default defineComponent({
  async run({ steps, $ }) {
    const tasks = steps.todoist_get_active_tasks.$return_value;

    if (!tasks || tasks.length === 0) {
      return {
        blocks: [
          {
            type: 'section',
            text: {
              type: 'mrkdwn',
              text: ':white_check_mark: No tasks due today — enjoy the quiet.'
            }
          }
        ]
      };
    }

    const priorityMap = {
      4: { label: 'Urgent', emoji: ':red_circle:' },
      3: { label: 'High',   emoji: ':large_orange_circle:' },
      2: { label: 'Medium', emoji: ':large_yellow_circle:' },
      1: { label: 'Normal', emoji: ':white_circle:' }
    };

    const today = new Date().toISOString().split('T')[0];

    const sorted = [...tasks].sort((a, b) => b.priority - a.priority);

    const blocks = [
      {
        type: 'header',
        text: {
          type: 'plain_text',
          text: `:clipboard: Daily Standup — ${new Date().toLocaleDateString('en-US', { weekday: 'long', month: 'short', day: 'numeric' })}`,
          emoji: true
        }
      },
      { type: 'divider' }
    ];

    for (const task of sorted) {
      const { label, emoji } = priorityMap[task.priority] || priorityMap[1];
      const dueDate = task.due?.date || 'No due date';
      const isOverdue = task.due?.date && task.due.date < today;
      const overdueFlag = isOverdue ? ' :warning: *Overdue*' : '';

      const formattedDate = dueDate !== 'No due date'
        ? new Date(dueDate + 'T00:00:00').toLocaleDateString('en-US', { month: 'short', day: 'numeric' })
        : 'No due date';

      blocks.push({
        type: 'section',
        text: {
          type: 'mrkdwn',
          text: `${emoji} *${label}* — <${task.url}|${task.content}> · Due: ${formattedDate}${overdueFlag}`
        }
      });
    }

    blocks.push({ type: 'divider' });
    blocks.push({
      type: 'context',
      elements: [
        {
          type: 'mrkdwn',
          text: `${sorted.length} task${sorted.length !== 1 ? 's' : ''} · Pulled from Todoist at ${new Date().toLocaleTimeString('en-US', { hour: '2-digit', minute: '2-digit' })}`
        }
      ]
    });

    return { blocks };
  }
});

Workflow Canvas > + Add Step > Slack > Send Message

Connect your Slack account

Click '+ Add Step' and search for 'Slack'. Select the 'Send Message' action. Click 'Connect Account' and authorize Pipedream via OAuth. Pipedream will request the 'chat:write' and 'chat:write.public' scopes — both are required. If you're posting to a private channel, you'll also need to invite the Pipedream Slack app to that channel manually inside Slack.

1. 1Click '+ Add Step' below the Node.js code step
2. 2Type 'Slack' in the app search
3. 3Select 'Slack' and then 'Send Message'
4. 4Click 'Connect Account' and complete the Slack OAuth flow
5. 5Confirm the connected account name matches your workspace

Slack Step > Channel > Blocks Field > Expression Picker

Configure the Slack message destination and payload

In the Slack 'Send Message' step, set the Channel field to your standup channel name, e.g. '#standup-product'. In the Blocks field, reference the output from your Node.js code step by clicking the '{{' expression picker and selecting 'steps.nodejs.$return_value.blocks'. Leave the Text field as a fallback string like 'Daily standup summary' — Slack uses this as a notification preview.

1. 1Click the Channel field and type '#standup-product' or your channel name
2. 2Click into the Blocks field
3. 3Click the '{{' button to open the expression picker
4. 4Navigate to your Node.js step and select '$return_value.blocks'
5. 5Set the Text field fallback to 'Daily standup summary — see thread'

Workflow Canvas > Run Now Button (top toolbar)

Test the full workflow end to end

Click 'Run Now' at the top of the workflow canvas to trigger a manual test run. Watch each step execute in sequence — green checkmarks indicate success. Open your Slack standup channel and confirm the message posted correctly. Check that task priorities, due dates, and task content all look right. If any step shows a red X, click it to read the error log.

1. 1Click the grey 'Run Now' button in the top toolbar
2. 2Watch each step tile turn green as they complete
3. 3Open Slack and navigate to your standup channel
4. 4Confirm the posted message shows the correct tasks and formatting
5. 5If a step fails, click the red X icon on that step to read the error detail

Node.js Code Step > Editor

Handle the case where no tasks are due

When Todoist returns zero tasks, your Node.js code will produce an empty blocks array and Slack will reject the message with a 'no_text' error. Add a short conditional in your code step that checks the array length. If it's zero, export a simple fallback message like 'No tasks due today — enjoy the quiet.' This prevents workflow errors on low-activity days.

1. 1Open your Node.js code step
2. 2Add an array length check before the blocks-building logic
3. 3Return a minimal Slack block with the fallback text if the array is empty
4. 4Click 'Test' to confirm the fallback triggers when task count is zero

Workflow Canvas > Deploy Button (top-right)

Deploy and activate the workflow

Click the grey 'Deploy' button in the top-right corner of the canvas. Pipedream will switch the workflow from draft mode to active. The toggle next to the workflow name will turn green. Your standup will now fire automatically every day at the time and timezone you set in Step 2. You can pause it anytime by flipping the toggle back.

1. 1Click the 'Deploy' button in the top-right corner
2. 2Confirm the prompt if one appears
3. 3Check that the toggle next to the workflow name turns green
4. 4Navigate to 'Workflow > Logs' to confirm the next scheduled run time