How to Post Wrike Standups to Slack with Make

make.com > Dashboard > Create a new scenario

Create a new Make scenario

Log in to Make at make.com. Click 'Create a new scenario' from your dashboard. You'll land on the visual canvas with a single empty module circle in the center. This is where your scheduled trigger lives. Make saves automatically, but the scenario won't run until you activate it at the end.

1. 1Click the blue 'Create a new scenario' button in the top right
2. 2Click the empty circle module that appears on the canvas
3. 3Type 'Schedule' in the search box
4. 4Select 'Schedule' under the Built-in apps section

Schedule Module > Settings Panel

Configure the schedule trigger

In the Schedule module settings, set the trigger to run on weekdays at a specific time — 8:45 AM works for pre-standup delivery. Set 'Run scenario' to 'At regular intervals', then choose 'Days' and specify Monday through Friday. Set the exact time in the 'Time' field. Make uses UTC by default, so calculate your team's local offset before entering the time.

1. 1Set 'Run scenario' to 'At regular intervals'
2. 2Set interval unit to 'Days'
3. 3Enter '1' in the interval count field
4. 4Set the Time field to your target UTC time (e.g. 13:45 for 8:45 AM EST)
5. 5Check 'Restrict to days of the week' and select Mon, Tue, Wed, Thu, Fri

Canvas > + > Wrike > Search Tasks

Add the Wrike 'Search Tasks' module

Click the plus icon to the right of the Schedule module to add the next step. Search for 'Wrike' and select it. From the list of Wrike actions, choose 'Search Tasks'. This module queries Wrike's API with filters you define — it returns a batch of tasks matching your criteria rather than a single record. You'll connect your Wrike account here if you haven't already.

1. 1Click the small '+' circle to the right of the Schedule module
2. 2Type 'Wrike' in the app search field
3. 3Select 'Wrike' from the results
4. 4Choose 'Search Tasks' from the action list
5. 5Click 'Add' next to the Connection field and authorize your Wrike account via OAuth

Wrike Search Tasks Module > Filters

Filter tasks by status and due date

In the Wrike Search Tasks module, set the Folder or Project ID to the project you want to report on. Set Status to 'In Progress' to catch active work. Add a second filter for due date — set 'Due Date' to less than or equal to 7 days from today to surface upcoming deadlines. You can use Make's date formula addDays(now; 7) directly in the Due Date field. Leave the result limit at 50 unless your projects routinely have more active tasks than that.

1. 1Click the Folder ID field and select or paste your target Wrike project ID
2. 2Set the Status filter to 'In Progress'
3. 3Click 'Add filter' and choose 'Due Date'
4. 4Set the operator to 'Less than or equal to'
5. 5Type addDays(now; 7) in the Due Date value field

Canvas > + > Built-in > Text Aggregator

Add an Aggregator to build the message body

After the Wrike module, add a 'Text Aggregator' module. This loops over all returned tasks and concatenates them into a single Slack-ready string. In the Text field, map Wrike task fields to build one line per task. A good format is: • {{task.title}} — Due: {{formatDate(task.dueDate; 'MMM D')}} — Assignee: {{task.responsibles[].name}}. The separator field should be a newline character \n.

1. 1Click '+' after the Wrike module
2. 2Search 'Text Aggregator' in the Built-in section
3. 3Set 'Source Module' to your Wrike Search Tasks module
4. 4In the 'Text' field, map: • {{1.title}} — Due: {{formatDate(1.dueDate; "MMM D")}} — {{1.responsibles[].name}}
5. 5Set 'Row separator' to 'New row (\n)'

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

Canvas > Right-click Schedule module > Add Router > + (second path) > Wrike > Search Tasks

Add an overdue task filter and second Wrike query

You probably want to call out overdue tasks separately from upcoming ones — they need more attention in standup. Add a second Wrike Search Tasks module after the Schedule trigger using a Router. Set this module to filter for Status 'In Progress' AND Due Date less than today using now. Run this in parallel with your first query so both results feed into the final message independently.

1. 1Right-click the connection line between Schedule and Wrike Search Tasks
2. 2Select 'Add a router'
3. 3On the second router path, click '+' and add another Wrike Search Tasks module
4. 4Set the same project folder ID
5. 5Set Due Date filter to 'Less than' and enter now

Canvas > + (after both aggregators) > Built-in > Text Aggregator

Merge both aggregated strings with a second Text Aggregator

After both paths produce their aggregated strings, add a final Text Aggregator that receives output from both aggregators. Use this module to build the full Slack message with section headers. Structure it as: *🔴 Overdue*\n{{overdue_text}}\n\n*📅 Due This Week*\n{{upcoming_text}}. This creates the complete message body in a single variable you'll pass to Slack. Map overdue output first so it gets team attention at the top.

1. 1Add a new Text Aggregator after both parallel paths converge
2. 2In the Text field, type the header: *🔴 Overdue*\n
3. 3Map the overdue aggregator's output text bundle
4. 4Add \n\n*📅 Due This Week*\n as a separator
5. 5Map the upcoming aggregator's output text bundle

Canvas > + > Slack > Create a Message

Connect your Slack account and choose the channel

Add a Slack module after the final Text Aggregator. Choose 'Create a Message' as the action. Authorize your Slack workspace via OAuth if not already connected. In the Channel field, type the channel name where you want standups posted — for example, #eng-standup. Make resolves channel names automatically, but you can also use the channel ID for reliability.

1. 1Click '+' after the final Text Aggregator
2. 2Search 'Slack' and select it
3. 3Choose 'Create a Message'
4. 4Click 'Add' next to Connection and authorize via Slack OAuth
5. 5In the Channel field, type your channel name or paste the Slack channel ID

Slack Create a Message Module > Text / Blocks

Build the Slack message with Block Kit formatting

In the Slack Create a Message module, map the final aggregated text into the 'Text' field. For better formatting, enable 'Use Block Kit' if the module supports it. Prefix the message with a date header: *📋 Daily Standup — {{formatDate(now; 'dddd, MMM D')}}*\n followed by the aggregated task string. Set 'As User' to true so the message posts under the connected bot name rather than a generic Slack app label.

1. 1In the Text field, type: *📋 Daily Standup — then map formatDate(now; 'dddd, MMM D') then *
2. 2Add a newline then map the final aggregated message string
3. 3Set 'As User' toggle to 'Yes'
4. 4Leave 'Thread Timestamp' empty unless you want replies threaded
5. 5Set 'Reply Broadcast' to 'No'

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

Canvas > Bottom Toolbar > Run once

Test the full scenario end-to-end

Click 'Run once' in the bottom toolbar to fire the scenario manually without waiting for the schedule. Watch each module execute in sequence — Make highlights them green as they complete. Check the output of each module by clicking the bubble that appears above it. Confirm the Slack message lands in your channel with the correct data before activating the schedule.

1. 1Click 'Run once' in the bottom toolbar
2. 2Watch each module light up green as it executes
3. 3Click the output bubble above the Wrike module to verify tasks are returned
4. 4Click the output bubble above the final Slack module to see the message payload
5. 5Open Slack and confirm the message appears in the correct channel

Canvas > Bottom Left > Activate scenario toggle

Activate the scenario and confirm scheduling

Click the blue 'Activate scenario' toggle in the bottom left of the canvas. The toggle turns green and Make shows the next scheduled run time. You can verify this by clicking 'Schedule' on the scenario detail page — it lists past runs and the upcoming trigger time. Set up email notifications for scenario errors in Make's notification settings so you hear about failures before your team notices a missing standup.

1. 1Click the grey toggle labeled 'Inactive' in the bottom left
2. 2Confirm the toggle turns green and reads 'Active'
3. 3Click the scenario name in the breadcrumb to go to scenario detail
4. 4Confirm the 'Next run' timestamp matches your intended schedule
5. 5Go to Account Settings > Notifications and enable error alerts via email

Paste this formula into the Text Aggregator's Text field to build a richer per-task line that includes priority emoji, completion percentage, and a clickable link. The `if()` and `substring()` calls handle missing fields so the message never breaks on incomplete Wrike tasks.

{{if(
  1.priority = "High";
  "🔴";

{{if(
  1.priority = "High";
  "🔴";
  if(
    1.priority = "Normal";
    "🟡";
    "⚪"
  )
)}} • {{1.title}}
   Due: {{formatDate(1.dueDate; "MMM D, YYYY")}}
   Assigned to: {{if(isEmpty(1.responsibles[].name); "Unassigned"; 1.responsibles[].name)}}
   Progress: {{if(isEmpty(1.completionPercent); "0"; 1.completionPercent)}}%
   🔗 {{if(isEmpty(1.permalink); "No link"; substring(1.permalink; 0; 80))}}