How to Post Wrike Standups to Slack with n8n

n8n Canvas > + New Workflow

Create a new n8n workflow

Open your n8n instance and click the orange 'New Workflow' button in the top right of the canvas. Name it something like 'Wrike Daily Standup → Slack' so it's easy to find later. You'll build this workflow left to right: trigger on the left, Wrike fetch in the middle, code transformation next, then Slack post on the right. Keep the canvas clean — this workflow has 5 nodes total.

1. 1Click '+ New Workflow' in the top right
2. 2Click the pencil icon next to 'My Workflow' and rename it to 'Wrike Daily Standup → Slack'
3. 3Press Enter to save the name

Canvas > + Node > Schedule Trigger

Add a Schedule trigger

Click the '+' node placeholder on the canvas and search for 'Schedule Trigger'. This is the built-in n8n node — no credentials required. Set the interval to 'Days' and configure the time to fire at 8:45 AM in your team's local timezone. The timezone dropdown is in the trigger settings panel on the right — it defaults to UTC, which will cause the summary to post at the wrong time if you don't change it.

1. 1Click the '+' placeholder node on the canvas
2. 2Type 'Schedule' in the search box and select 'Schedule Trigger'
3. 3Set 'Trigger Interval' to 'Days'
4. 4Set 'Hour' to 8 and 'Minute' to 45
5. 5Open the 'Timezone' dropdown and select your team's local timezone

Wrike > Account Settings > Apps & Integrations > API > Create App

Connect your Wrike account

Add an HTTP Request node after the Schedule Trigger — n8n does not have a native Wrike node, so you'll call the Wrike REST API directly. In the node settings, set the method to GET. Paste your Wrike API endpoint for tasks into the URL field. You'll authenticate using a permanent Wrike access token passed as a Bearer token in the Authorization header. Get your token from Wrike's Apps & Integrations page.

1. 1Log in to Wrike and navigate to Account Settings > Apps & Integrations > API
2. 2Click 'Create New App', name it 'n8n Standup', and copy the permanent access token
3. 3Back in n8n, add an HTTP Request node after the Schedule Trigger
4. 4Set Method to 'GET'
5. 5Set URL to 'https://www.wrike.com/api/v4/tasks?status=Active&fields=["assignees","dates","status","description","parentIds"]'
6. 6Under 'Authentication', select 'Header Auth', set Name to 'Authorization', Value to 'Bearer YOUR_TOKEN_HERE'

HTTP Request Node > URL Field > Expression Editor

Filter tasks to the relevant window

The raw Wrike API returns all active tasks — potentially hundreds. Add a second HTTP Request node or use n8n's built-in filtering to scope results. The cleaner approach: modify the Wrike URL query to filter by due date. Wrike accepts 'dueDate' range parameters in the query string. Set 'dueDateStart' to today's date and 'dueDateEnd' to 48 hours from now, formatted as ISO 8601. You'll construct these dates dynamically using n8n expressions.

1. 1Click the HTTP Request node you created in Step 3
2. 2Click the URL field and switch to 'Expression' mode using the toggle on the right
3. 3Replace the static URL with the expression shown in the pro tip code section to inject dynamic date ranges
4. 4Click 'Test Step' to verify the filtered response returns only near-term tasks

Canvas > + Node after Schedule Trigger > HTTP Request

Fetch overdue tasks in a second API call

Add a second HTTP Request node branching from the Schedule Trigger (or chained after the first). This call targets the same Wrike tasks endpoint but filters for tasks where 'dueDate' is before today and status is still Active. These are your overdue items — critical for any standup summary. You'll merge this response with the near-term tasks in the next step.

1. 1Add a new HTTP Request node — click the '+' on the canvas
2. 2Set Method to 'GET' and use the same Bearer token auth
3. 3Set URL to filter tasks where dueDateEnd equals yesterday's date in ISO 8601 format (use an expression identical to Step 4 but subtract 1 day for the end date and set start far in the past)
4. 4Label this node 'Wrike — Overdue Tasks' by clicking the node title

Canvas > + Node > Merge, then + Node > Code

Merge and transform task data with a Code node

Add a Merge node to combine the two Wrike API responses, then chain a Code node after it. The Code node is where the real work happens — you'll extract task title, assignee, due date, and status from each item, group tasks by assignee, and build the Slack message block string. Use JavaScript inside the n8n Code node. The full transformation script is in the pro tip section below — paste it directly into the Code node's editor.

1. 1Add a Merge node after both HTTP Request nodes — connect both nodes to its inputs
2. 2Set Merge Mode to 'Append' so both task arrays are combined into one list
3. 3Add a Code node after the Merge node
4. 4Paste the transformation script from the pro tip section into the JavaScript editor
5. 5Click 'Test Step' and inspect the output — you should see a single formatted string ready for Slack

Paste this into the Code node that sits after your Merge node. It resolves assignee IDs to names using a pre-built lookup map (which you populate from the /contacts API response passed in as a second input), groups tasks by assignee, flags overdue vs. upcoming items, and builds the final Slack-formatted message string with mrkdwn bold headers and emoji indicators.

// n8n Code Node — Wrike Standup Message Builder
// Inputs: items[0..N] = merged Wrike tasks, contactMap passed via $node['Wrike Contacts'].json
const today = new Date();

// n8n Code Node — Wrike Standup Message Builder
// Inputs: items[0..N] = merged Wrike tasks, contactMap passed via $node['Wrike Contacts'].json

const today = new Date();
today.setHours(0, 0, 0, 0);

// Build contact ID → display name lookup from the contacts API response
const contactItems = $node['Wrike — Contacts'].json;
const contactMap = {};
if (contactItems && contactItems.data) {
  for (const contact of contactItems.data) {
    contactMap[contact.id] = `${contact.firstName} ${contact.lastName}`.trim();
  }
}

// Collect all tasks from merged input
const allTasks = $input.all().map(item => item.json);

// Group tasks by primary assignee
const byAssignee = {};
for (const task of allTasks) {
  const assigneeIds = task.responsibleIds || [];
  const primaryId = assigneeIds[0] || 'unassigned';
  const displayName = contactMap[primaryId] || primaryId;

  if (!byAssignee[displayName]) {
    byAssignee[displayName] = [];
  }

  const dueRaw = task.dates && task.dates.due ? task.dates.due : null;
  const dueDate = dueRaw ? new Date(dueRaw) : null;
  dueDate && dueDate.setHours(0, 0, 0, 0);

  const isOverdue = dueDate && dueDate < today;
  const dueDateStr = dueDate
    ? dueDate.toLocaleDateString('en-US', { month: 'short', day: 'numeric' })
    : 'no due date';

  const emoji = isOverdue ? '🔴' : '🟡';
  const label = isOverdue ? `overdue since ${dueDateStr}` : `due ${dueDateStr}`;
  const link = task.permalink ? `<${task.permalink}|view>` : '';

  byAssignee[displayName].push(`${emoji} ${task.title} — ${label} ${link}`.trim());
}

// Build Slack message
const dateHeader = today.toLocaleDateString('en-US', { weekday: 'short', month: 'short', day: 'numeric' });
let message = `🗓 *Daily Standup — ${dateHeader}*\n`;

if (Object.keys(byAssignee).length === 0) {
  message += '\nNo active tasks due in the next 48 hours. ✅';
} else {
  for (const [name, tasks] of Object.entries(byAssignee)) {
    message += `\n*${name}*\n${tasks.join('\n')}\n`;
  }
}

return [{ json: { slackMessage: message } }];

Canvas > + Node > Slack > Credentials > Add OAuth2

Connect your Slack account

Add a Slack node after the Code node. Click 'Add Credential' in the node panel and select OAuth2. n8n will open a Slack authorization popup — sign in with the Slack workspace where you want to post standups. The Slack app that n8n creates needs the 'chat:write' and 'channels:read' OAuth scopes. If you're posting to a private channel, also add 'groups:write'.

1. 1Add a Slack node and click 'Add Credential'
2. 2Select 'OAuth2' and click 'Connect'
3. 3In the Slack authorization popup, select your workspace and click 'Allow'
4. 4Back in n8n, confirm a green checkmark appears next to the credential name

Slack Node > Resource: Message > Operation: Post

Configure the Slack message

In the Slack node, set Resource to 'Message' and Operation to 'Post'. Select your target channel from the dropdown — for example, #product-standup. In the 'Text' field, switch to Expression mode and reference the output from the Code node using '{{ $node["Code"].json["slackMessage"] }}'. Set 'As User' to true if you want the message to appear under a bot name rather than your personal account.

1. 1Set Resource to 'Message'
2. 2Set Operation to 'Post'
3. 3Select your standup channel from the 'Channel' dropdown
4. 4Click the 'Text' field and toggle to Expression mode
5. 5Type {{ $node["Code"].json["slackMessage"] }} in the expression field
6. 6Set 'Bot Name' to 'Standup Bot' and optionally set an emoji icon under 'Icon'

HTTP Request Node > ... Menu > Add Error Output > Slack Node

Add error handling with a fallback notification

Wrap the workflow in error handling so you know when the standup fails to post. In n8n, click the three-dot menu on any node and select 'Add Error Output'. Chain a second Slack node to the error output of your HTTP Request nodes. This fallback node posts a simple alert to a #alerts channel: 'Standup failed — Wrike API did not respond. Check n8n execution log.' Without this, a failed run is silent.

1. 1Click the three-dot menu on the first HTTP Request node
2. 2Select 'Add Error Output' — a red error connector appears on the node
3. 3Add a new Slack node and connect it to the red error output
4. 4Set it to post to your #alerts or #dev-ops channel with a hardcoded error message string
5. 5Repeat for the second HTTP Request node

Canvas > Active Toggle (top right) > Execute Workflow (play icon)

Activate and verify the workflow

Click the toggle in the top right of the n8n canvas to activate the workflow. The toggle turns green and the workflow is now live. To verify without waiting until 8:45 AM, click the 'Execute Workflow' button (the play icon) to run it immediately. Check your Slack channel — the standup summary should appear within 15 seconds. Then check the n8n execution log to confirm all nodes returned green status.

1. 1Click the gray toggle in the top right — it turns green labeled 'Active'
2. 2Click the play icon to trigger an immediate manual execution
3. 3Switch to your Slack channel and confirm the message appears
4. 4Click 'Executions' in the left sidebar of n8n to review the run log