How to Send Weekly Todoist Reports to Slack with Make

make.com > Scenarios > Create a new scenario

Create a new scenario in Make

Log into Make at make.com and click the blue 'Create a new scenario' button in the top right corner of the Scenarios dashboard. You'll land on the visual canvas with a large plus-circle in the center — this is where your first module goes. Give the scenario a name immediately by clicking the default name at the top ('New Scenario') and typing something like 'Weekly Todoist → Slack Report'. Naming it now saves confusion when you have multiple scenarios running.

1. 1Click 'Create a new scenario' (top right, blue button)
2. 2Click the pencil icon next to 'New Scenario' at the top
3. 3Type a name like 'Weekly Todoist → Slack Report'
4. 4Press Enter to save the name

Canvas > + Module > Schedule

Add the Schedule trigger

Click the plus-circle on the canvas to open the module picker. Search for 'Schedule' and select it — this is Make's built-in clock trigger, not a Todoist module. Set it to run every week. You'll configure the exact day and time in the next step, but selecting 'Schedule' here locks in the weekly cadence as your trigger type.

1. 1Click the large plus-circle in the canvas center
2. 2Type 'Schedule' in the search bar
3. 3Click 'Schedule' under the Tools category
4. 4Select 'Every week' from the interval dropdown

Schedule Module > Settings > Advanced scheduling

Set the day and time for the weekly run

Inside the Schedule module settings, set 'Day of week' to Friday and 'Time' to your desired UTC time. The 'Advanced scheduling' toggle lets you pick specific days rather than just intervals. Double-check the UTC offset — this is the most common reason teams get reports on Saturday morning instead of Friday evening. Click 'OK' to save the module.

1. 1Toggle on 'Advanced scheduling' inside the Schedule module panel
2. 2Set 'Day of week' to Friday
3. 3Set 'Time' to your target UTC time (e.g., 22:00 for 5pm EST)
4. 4Click 'OK' to save

Canvas > + > Todoist > Search Tasks

Add Todoist — Search Tasks module

Click the plus icon to the right of the Schedule module to add the next module. Search for 'Todoist' and connect your Todoist account when prompted — you'll need to authorize Make via OAuth. Once connected, select the 'Search Tasks' action. This module will fetch tasks filtered by completion status and date range, giving you only the tasks completed in the past 7 days.

1. 1Click the right-side plus icon on the Schedule module
2. 2Search for 'Todoist' in the module picker
3. 3Click 'Todoist' and select 'Search Tasks'
4. 4Click 'Add' to connect a new Todoist account via OAuth
5. 5Authorize Make in the Todoist OAuth popup that appears

Todoist Module > Search Tasks > Filter / Since / Until fields

Configure the Todoist filter for completed tasks

In the Search Tasks module, set the 'Filter' field to target completed tasks from the past week. Todoist's filter syntax uses 'overdue', 'today', or date-specific strings. For completed task history, you'll use the Todoist 'Get Completed Tasks' endpoint instead — if your Make Todoist module version offers it, select that action. Set the 'Since' field using Make's date formula: formatDate(addDays(now; -7); 'YYYY-MM-DD') to dynamically calculate 7 days back. Set 'Until' to formatDate(now; 'YYYY-MM-DD').

1. 1In the 'Since' field, click the formula icon (fx) and type: formatDate(addDays(now; -7); 'YYYY-MM-DD')
2. 2In the 'Until' field, type: formatDate(now; 'YYYY-MM-DD')
3. 3Leave 'Project ID' blank to pull from all projects, or enter a specific project ID to narrow scope
4. 4Set the maximum number of returned records to 100
5. 5Click 'OK' to save

Canvas > + > Tools > Text Aggregator

Add an Aggregator to count tasks by project

Click the plus icon after the Todoist module and add a 'Text Aggregator' module from Make's built-in Tools. This module loops through every completed task returned by Todoist and combines them into a single text block. Set the 'Source Module' to your Todoist module. In the 'Text' field, format each task as a line: {{project_name}}: {{content}} using the mapped fields from the Todoist output. The aggregator will join all lines so you can send one Slack message instead of one message per task.

1. 1Click the plus icon after the Todoist Search Tasks module
2. 2Search for 'Text Aggregator' under Tools
3. 3Set 'Source Module' to your Todoist module (the iterator source)
4. 4In the 'Text' field, enter: {{project_name}}: {{content}}
5. 5Set 'Row separator' to a newline character (\n)
6. 6Click 'OK'

Canvas > + > Tools > Set Variable

Add a Tools — Set Variable module to count total tasks

Before the Slack message step, add a 'Set Variable' module to store the total count of completed tasks. Click the plus icon, search for 'Set Variable' under Tools. Set the variable name to total_completed and the value to the bundle count output from the Text Aggregator: {{totalCount}}. This gives you a clean number to drop into the Slack message header without extra formatting logic.

1. 1Click the plus icon after the Text Aggregator module
2. 2Search for 'Set Variable' under Tools
3. 3Set 'Variable name' to: total_completed
4. 4Set 'Variable value' to: {{totalCount}} from the Text Aggregator output
5. 5Click 'OK'

Canvas > + > Slack > Create a Message

Connect your Slack account and add Send Message module

Click the plus icon and search for 'Slack'. Select 'Create a Message' (not 'Send a Message' — Make's Slack module uses 'Create a Message' for posting to channels). Authorize your Slack workspace via OAuth when prompted. Make will ask for permission to post messages — approve it. Once connected, you'll see fields for Channel, Text, and optional Block Kit formatting.

1. 1Click the plus icon after the Set Variable module
2. 2Search for 'Slack' in the module picker
3. 3Select 'Create a Message'
4. 4Click 'Add' to connect a Slack account
5. 5Authorize Make in the Slack OAuth popup and grant the requested permissions

📬 New entry: {{1.name}}
Email: {{1.email}}
Details: {{1.description}}

Slack Module > Create a Message > Channel / Text fields

Configure the Slack message content

Set the 'Channel' field to the Slack channel where leadership reviews reports — type the channel name or ID (e.g., #leadership-updates). In the 'Text' field, build the message using mapped variables. A clean format: *Weekly Progress Report — {{formatDate(now; 'MMM D, YYYY')}}* ✅ Tasks completed this week: {{total_completed}} *By project:* {{aggregatedText}}. This uses the Text Aggregator output and the variable from Step 7 to produce a readable, consistent message every Friday.

1. 1Click inside the 'Channel' field and type or select your target channel (e.g., #leadership-updates)
2. 2Click inside the 'Text' field
3. 3Paste your message template using {{}} mapped variables from previous modules
4. 4Map {{total_completed}} from the Set Variable module output
5. 5Map the aggregated task list from the Text Aggregator output
6. 6Click 'OK'

📬 New entry: {{1.name}}
Email: {{1.email}}
Details: {{1.description}}

Canvas > Run once (bottom toolbar)

Run a test and verify the Slack output

Click 'Run once' in the bottom toolbar to trigger a manual test run. Watch the execution flow animate across the canvas — each module turns green when it succeeds and shows a bubble with the record count processed. Open your Slack channel and confirm the message arrived with the correct task count and project list. If the task list is empty, your Todoist date range filter may be returning no results — check Step 5's formula output in the Todoist module's execution log.

1. 1Click 'Run once' in the bottom toolbar
2. 2Watch each module's status bubble for green checkmarks
3. 3Open your Slack channel to verify the message appeared
4. 4Click any module bubble on the canvas to inspect the exact data it processed
5. 5Check the Todoist module bubble to confirm tasks were returned

Canvas > bottom-left toggle > ON | Scenario Settings > Max stored executions

Activate the scenario

Once the test run looks correct, toggle the scenario from OFF to ON using the switch in the bottom left corner of the canvas. Make will now run this scenario automatically every Friday at the time you configured in Step 3. The scenario log (accessible from the Scenarios dashboard under 'History') records every run so you can audit past reports. Set the number of stored execution logs to at least 30 under Scenario Settings so you have a month of history.

1. 1Click the toggle switch in the bottom left from OFF to ON
2. 2Confirm the activation dialog if prompted
3. 3Click 'Scenario Settings' (gear icon near the toggle)
4. 4Set 'Max stored executions' to 30
5. 5Click 'Save' and close settings

Paste this formula block into Make's Text Aggregator 'Text' field to group tasks by project with a count per project and a visual separator between groups. The if() logic checks whether the current project name matches the previous one and only prints the project header when it changes — creating a cleaner grouped layout without needing an extra Iterator module.

// Make Formula — Text Aggregator 'Text' field
// Groups completed tasks by project name with per-project headers
// Paste this into the Text field of the Text Aggregator module

// Make Formula — Text Aggregator 'Text' field
// Groups completed tasks by project name with per-project headers
// Paste this into the Text field of the Text Aggregator module

if(
  {{project_name}} != {{previousProjectName}};
  "\n📁 " + {{project_name}} + "\n" + "  • " + {{content}};
  "  • " + {{content}}
)

// In the Slack message Text field, wrap the aggregated output:
// *Weekly Progress Report — " + formatDate(now; "MMM D, YYYY") + "*
// \n✅ Total tasks completed: " + {{totalCount}} + "\n"
// + {{aggregatedText}}

// To add a per-project count, use a separate Numeric Aggregator
// before the Text Aggregator, grouped by project_id:
// Set 'Group by' to: {{project_id}}
// Set 'Value' to: 1 (counts one per task)
// Then map {{sum}} into the project header line above