How to Automate Daily Standups from Asana 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 scenario canvas with an empty circle in the middle. This is your trigger slot. Click the circle to open the module picker. You're building a scheduled scenario, so the first module will be a scheduling trigger, not an app trigger.

1. 1Log into make.com and go to the Scenarios tab in the left sidebar
2. 2Click the blue 'Create a new scenario' button in the top-right
3. 3Click the empty circle in the center of the canvas to open the module picker
4. 4Type 'Schedule' in the search bar and select the 'Schedule' module

Scenario canvas > Schedule module > Settings panel

Configure the schedule trigger

Click the Schedule module to open its settings panel on the right. Set the interval to 'Days' and enter 1. Set the time to 08:45 or whatever time your team wants the standup posted. Make runs scenarios in UTC by default, so adjust the time accordingly — if your team is in ET (UTC-5), enter 13:45 UTC to hit 8:45 AM ET. Set it to run Monday through Friday only by enabling the 'Days of week' filter.

1. 1Click the Schedule module on the canvas to open its configuration panel
2. 2Set 'Run scenario' to 'Every day'
3. 3Enter your target time converted to UTC in the time field
4. 4Toggle 'Days of week' and uncheck Saturday and Sunday

Scenario canvas > + > Asana > Search Tasks

Connect Asana and search for completed tasks

Click the '+' icon to the right of the Schedule module to add the next module. Search for 'Asana' and select 'Search Tasks'. This module lets you query Asana for tasks matching specific criteria — you'll filter by project and by completion date. Click 'Add' next to the Connection field and authenticate with your Asana account using OAuth. Make will open an Asana authorization popup.

1. 1Click the '+' icon to the right of the Schedule module
2. 2Type 'Asana' in the module search bar and select it
3. 3Choose 'Search Tasks' from the action list
4. 4Click 'Add' next to Connection and authorize via the Asana OAuth popup
5. 5Select your Workspace from the dropdown after authentication

Search Tasks module > Filters panel

Filter for tasks completed in the last 24 hours

In the Search Tasks module settings, set the Project field to the Asana project your team uses. Under 'Completed Since', use Make's date formula to dynamically calculate yesterday's date: enter {{formatDate(addDays(now; -1); 'YYYY-MM-DD')}}. This tells Asana to return only tasks marked complete after that timestamp. Set the Maximum number of returned results to 50 — enough for any team's daily output without hitting API limits.

1. 1Select your target Asana project from the Project dropdown
2. 2Click the 'Completed Since' field and switch to formula mode by clicking the formula icon
3. 3Paste: {{formatDate(addDays(now; -1); 'YYYY-MM-DD')}}
4. 4Set 'Completed' to 'Yes' to exclude open tasks
5. 5Set 'Maximum number of returned results' to 50

Scenario canvas > + > Asana > Search Tasks (second instance)

Add a second Asana module for upcoming due tasks

Click '+' again after the first Asana module to add another 'Search Tasks' module using the same Asana connection. This time, you're pulling tasks due today — not completed ones. Set 'Completed' to 'No' and use the Due Date filter. Set 'Due On' to {{formatDate(now; 'YYYY-MM-DD')}} to match today's date exactly. This gives you the 'what's coming up today' section of the standup report.

1. 1Click the '+' icon after the first Asana Search Tasks module
2. 2Select Asana > Search Tasks again
3. 3Reuse the same Asana connection from the dropdown
4. 4Set 'Completed' to 'No'
5. 5Set 'Due On' field to {{formatDate(now; 'YYYY-MM-DD')}}

Scenario canvas > + > Tools > Text Aggregator

Add a Text Aggregator to format completed tasks

Click '+' after the first Search Tasks module and search for 'Text Aggregator'. This module concatenates every task returned from a bundle into a single block of text — exactly what you need to build the standup message body. Set the Source Module to the first Asana Search Tasks module. In the Text field, build your row format: ✅ {{name}} — assigned to {{assignee.name}} — <{{permalink_url}}|View in Asana>. Each task will become one line in the final Slack message.

1. 1Click '+' after the first Asana Search Tasks module
2. 2Search for 'Text Aggregator' under Tools
3. 3Set 'Source Module' to the first Asana Search Tasks module
4. 4In the Text field, enter: ✅ {{name}} — {{assignee.name}} — <{{permalink_url}}|View in Asana>
5. 5Set the Row Separator to 'New Line'

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

Scenario canvas > + > Tools > Text Aggregator (second instance)

Add a second Text Aggregator for due-today tasks

Repeat the process from Step 6 for the second Asana module. Click '+' after the second Search Tasks module, add another Text Aggregator, and set its Source Module to the second Asana Search Tasks module. Format each row as: 📅 {{name}} — {{assignee.name}} — due today. This creates the second block of the standup message covering what's on deck for the day.

1. 1Click '+' after the second Asana Search Tasks module
2. 2Add another Text Aggregator from Tools
3. 3Set 'Source Module' to the second Asana Search Tasks module
4. 4In the Text field enter: 📅 {{name}} — {{assignee.name}} — due today
5. 5Set Row Separator to 'New Line'

Scenario canvas > + > Slack > Create a Message

Connect Slack and configure the message module

Click '+' after your second Text Aggregator and add the Slack module 'Create a Message'. Authenticate with your Slack workspace using OAuth — Make will ask for bot token scopes including chat:write. Select the target channel from the Channel dropdown (e.g. #standup or #engineering-standup). In the Text field, build the full standup message using output from both Text Aggregators and static formatting.

1. 1Click '+' after the second Text Aggregator
2. 2Search for 'Slack' and select 'Create a Message'
3. 3Click 'Add' next to Connection and authorize your Slack workspace via OAuth
4. 4Select your target channel from the Channel dropdown
5. 5Build the message body in the Text field using both Text Aggregator outputs

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

Slack > Create a Message > Text field

Build the full standup message body

In the Slack 'Create a Message' Text field, construct the full report using a combination of static text and dynamic variables from both Text Aggregators. Use Make's if() formula to handle the case where either section is empty. The message should have a header, a completed tasks section, and a due-today section. Use Slack's mrkdwn formatting — *bold* for headers, line breaks between sections.

1. 1Click into the Text field of the Slack module
2. 2Type the header: *📋 Daily Standup — {{formatDate(now; 'MMMM D, YYYY')}}*
3. 3Add a line break, then type: *✅ Completed Yesterday:*
4. 4Map the first Text Aggregator output using {{bundle1.text}} or the variable picker
5. 5Add another section: *📅 Due Today:* followed by the second Text Aggregator output
6. 6Wrap each section in: {{if(isEmpty(aggregator.text); '_Nothing to report_'; aggregator.text)}}

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

Slack module > Right-click > Add error handler

Add an error handler for failed runs

Right-click on the Slack module and select 'Add error handler'. Choose 'Ignore' if you want silent failures, or 'Rollback' if you want Make to retry. For a standup bot, add a separate Slack 'Create a Message' module inside the error handler that posts to a #make-alerts channel with the error message. This way, if Asana's API is down or the Slack token expires, someone gets notified immediately instead of the standup silently not posting.

1. 1Right-click the Slack 'Create a Message' module on the canvas
2. 2Select 'Add error handler' from the context menu
3. 3Choose 'Break' as the error handler type
4. 4Click '+' inside the error handler path and add another Slack 'Create a Message' module
5. 5Set the channel to #make-alerts and the message to: ⚠️ Standup bot failed: {{error.message}}

Scenario canvas > bottom-left toggle > ON

Activate the scenario and verify the first run

Toggle the scenario from OFF to ON using the switch in the bottom-left of the canvas. Make will confirm the next scheduled run time. Click 'Run once' immediately to trigger a manual test run and verify the full pipeline end-to-end. Check your Slack channel for the standup message. Then open the Scenario History tab to confirm all modules completed without errors — each should show a green bubble with a count of processed bundles.

1. 1Click the toggle in the bottom-left corner to switch from OFF to ON
2. 2Click 'Run once' in the toolbar to trigger an immediate test
3. 3Open your target Slack channel and confirm the standup message arrived
4. 4Click 'History' in the left sidebar to review the run log
5. 5Verify each module shows a green bundle count and no red error icons

Paste this into a Make 'Set Variable' module placed between the Text Aggregators and the Slack module. It truncates long task names at 60 characters, strips newlines from task notes, and adds a fallback string when either section is empty — preventing blank standup sections from posting to Slack.

{{if(
  isEmpty(1.text);
  '_No tasks completed in the last 24 hours._';

{{if(
  isEmpty(1.text);
  '_No tasks completed in the last 24 hours._';
  1.text
)}}

{{if(
  isEmpty(2.text);
  '_No tasks due today._';
  2.text
)}}

// Truncate task name to 60 chars in the Text Aggregator row:
{{if(
  length(name) > 60;
  substring(name; 0; 60) + '...';
  name
)}}

// Strip line breaks from task notes before including in message:
{{replace(notes; '\n'; ' ')}}

// Format completed_at to human-readable local time:
{{formatDate(completed_at; 'h:mm A'; 'America/New_York')}}