How to Post Wrike Standup Summaries to Slack with Pipedream

pipedream.com > Workflows > New Workflow

Create a new Pipedream workflow

Go to pipedream.com and sign in. Click 'Workflows' in the left sidebar, then click the blue 'New Workflow' button in the top right. You'll land on a blank canvas with a 'Add a trigger' prompt at the top. This is where the schedule lives — not inside any app connection.

1. 1Click 'Workflows' in the left sidebar
2. 2Click the blue 'New Workflow' button
3. 3Click 'Add a trigger' on the blank canvas

Trigger Panel > Schedule > Cron Expression

Set a daily schedule trigger

In the trigger panel, search for 'Schedule' and select the 'Schedule' source. Choose 'Cron Expression' for full control over timing — the simple interval picker won't let you target a specific time of day. Enter a cron expression matching your standup prep window, e.g. 0 9 * * 1-5 fires at 9:00 AM UTC Monday through Friday. Confirm the next scheduled run time shown in the preview before moving on.

1. 1Type 'Schedule' in the trigger search bar
2. 2Click the 'Schedule' source
3. 3Select 'Cron Expression' from the schedule type dropdown
4. 4Enter your cron string, e.g. '0 9 * * 1-5'
5. 5Verify the 'Next run' preview timestamp matches your intended time

Workflow Canvas > + Add Step > Wrike > Get Tasks

Connect your Wrike account

Click the '+' button below the trigger to add a new step. Search for 'Wrike' and select it. Choose the action 'Get Tasks' (or 'Run API Request' if you need more query control). Click 'Connect Account' and authenticate via OAuth — Pipedream will open a Wrike authorization popup. Select the Wrike workspace that contains your active projects.

1. 1Click '+' below the Schedule trigger
2. 2Search 'Wrike' in the step search panel
3. 3Select the 'Wrike' app
4. 4Choose the 'Get Tasks' action
5. 5Click 'Connect Account' and complete the OAuth popup
6. 6Select your workspace from the account dropdown if prompted

Wrike Step > Configuration Fields

Configure the Wrike task query

In the Wrike step configuration, set the 'Status' filter to exclude completed tasks — use 'Active' or pass the status values ['Active', 'InProgress'] depending on your Wrike setup. Set the 'Due Date' range to return tasks due within the next 2 days plus any overdue tasks. Use the 'Fields' parameter to request title, assignees, due date, status, and permalink so you have everything needed for the summary message. If you manage multiple projects, add a 'Folder ID' or 'Project ID' filter to scope the query — otherwise you'll pull every task in the workspace.

1. 1Set 'status' field to 'Active' or your equivalent in-progress statuses
2. 2Set due date range to cover today through 48 hours from now
3. 3Add 'overdue: true' or equivalent filter for past-due tasks
4. 4Set 'fields' to include title, assignees, dueDate, status, permalink
5. 5Optionally paste a Wrike Folder ID to limit scope to one project

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

Add a Node.js code step to format the summary

Click '+' below the Wrike step and choose 'Run Node.js code'. This step takes the raw Wrike task array and builds the Slack Block Kit message payload. Group tasks by status (overdue, due today, due tomorrow), format the due dates into readable strings, and resolve assignee IDs to names using a lookup object or a secondary Wrike API call. The output of this step should be a complete Slack blocks array ready to POST.

1. 1Click '+' below the Wrike step
2. 2Select 'Run Node.js code' from the step type list
3. 3Paste your formatting code into the editor (see Pro Tip below)
4. 4Reference the Wrike step output using steps.wrike.$return_value
5. 5Click 'Test' to confirm the output is a valid Slack blocks array

Paste this into the Node.js code step (Step 5 on the canvas). It takes the Wrike task array from steps.wrike.$return_value, resolves assignee IDs using a pre-built contact map, groups tasks into overdue/today/upcoming buckets, and returns a complete Slack Block Kit payload. Replace the userMap object with real entries from your Wrike workspace contacts API response.

// Pipedream Node.js code step
// Reference: steps.wrike.$return_value must be an array of Wrike task objects
export default defineComponent({

// Pipedream Node.js code step
// Reference: steps.wrike.$return_value must be an array of Wrike task objects

export default defineComponent({
  async run({ steps, $ }) {
    const tasks = steps.wrike.$return_value?.data || [];

    // Replace with real Wrike user IDs from GET /contacts
    const userMap = {
      'KUAB12345': 'Sarah Chen',
      'KUCD67890': 'Marcus Webb',
      'KUEF11223': 'Jordan Park',
    };

    const now = new Date();
    const todayStr = now.toISOString().split('T')[0];
    const tomorrowStr = new Date(now.getTime() + 86400000).toISOString().split('T')[0];

    const priorityEmoji = { High: '🔴', Normal: '🟡', Low: '⚪' };

    const formatTask = (task) => {
      const assignees = (task.responsibleIds || [])
        .map(id => userMap[id] || id)
        .join(', ') || 'Unassigned';
      const priority = priorityEmoji[task.importance] || '🟡';
      const dueRaw = task.dates?.due;
      let dueLabel = 'No due date';

      if (dueRaw) {
        const dueDate = dueRaw.split('T')[0];
        if (dueDate < todayStr) {
          dueLabel = `Overdue (${dueDate})`;
        } else if (dueDate === todayStr) {
          dueLabel = 'Due Today';
        } else if (dueDate === tomorrowStr) {
          dueLabel = 'Due Tomorrow';
        } else {
          dueLabel = `Due ${dueDate}`;
        }
      }

      return {
        type: 'section',
        text: {
          type: 'mrkdwn',
          text: `${priority} *<${task.permalink}|${task.title}>*\nDue: ${dueLabel} · Assigned to: ${assignees} · Status: ${task.status?.name || task.status}`
        }
      };
    };

    const overdue = tasks.filter(t => t.dates?.due && t.dates.due.split('T')[0] < todayStr);
    const dueToday = tasks.filter(t => t.dates?.due && t.dates.due.split('T')[0] === todayStr);
    const upcoming = tasks.filter(t => t.dates?.due && t.dates.due.split('T')[0] > todayStr);
    const noDue = tasks.filter(t => !t.dates?.due);

    if (tasks.length === 0) {
      return {
        blocks: [
          {
            type: 'section',
            text: { type: 'mrkdwn', text: ':white_check_mark: No active tasks due in the next 48 hours. Enjoy the quiet.' }
          }
        ]
      };
    }

    const blocks = [
      {
        type: 'header',
        text: { type: 'plain_text', text: `📋 Daily Wrike Standup — ${todayStr}`, emoji: true }
      },
      { type: 'divider' }
    ];

    if (overdue.length > 0) {
      blocks.push({
        type: 'section',
        text: { type: 'mrkdwn', text: `*🚨 Overdue (${overdue.length})*` }
      });
      blocks.push(...overdue.map(formatTask));
      blocks.push({ type: 'divider' });
    }

    if (dueToday.length > 0) {
      blocks.push({
        type: 'section',
        text: { type: 'mrkdwn', text: `*📅 Due Today (${dueToday.length})*` }
      });
      blocks.push(...dueToday.map(formatTask));
      blocks.push({ type: 'divider' });
    }

    if (upcoming.length > 0) {
      blocks.push({
        type: 'section',
        text: { type: 'mrkdwn', text: `*🔜 Upcoming (${upcoming.length})*` }
      });
      blocks.push(...upcoming.map(formatTask));
    }

    return { blocks };
  }
});

Workflow Canvas > + Add Step > Slack > Send Message to Channel

Connect your Slack account

Click '+' below the code step and search for 'Slack'. Select the 'Send Message to Channel' action. Click 'Connect Account' and authorize via OAuth. Make sure you authorize as a user or bot that is already a member of the target channel — Pipedream will not auto-join channels. You can also use 'Send Message Using Block Kit' if your code step outputs a blocks array, which gives you richer formatting.

1. 1Click '+' below the Node.js code step
2. 2Search 'Slack' in the step panel
3. 3Select 'Send Message to Channel' or 'Send Message Using Block Kit'
4. 4Click 'Connect Account' and complete Slack OAuth
5. 5Confirm the authorized account appears in the account dropdown

Slack Step > Configuration Fields

Configure the Slack message target and payload

In the Channel field, type the channel name or ID where the summary should post — e.g. #product-standup. If posting to multiple channels, you'll need to duplicate the Slack step once per channel or loop through a channel list in the code step. In the Blocks field, reference the output of your code step using the expression picker: steps.nodejs.$return_value.blocks. Leave the Text field populated with a plain-text fallback like 'Daily Wrike standup summary' for Slack clients that don't render blocks.

1. 1Type or paste the target channel name in the 'Channel' field
2. 2Click the expression picker next to the 'Blocks' field
3. 3Navigate to steps.nodejs.$return_value.blocks
4. 4Add a plain-text fallback in the 'Text' field
5. 5Set 'Bot Name' and 'Bot Icon' if you want a branded sender appearance

Node.js Code Step > Editor (add early return guard)

Add error handling for empty task results

If Wrike returns zero tasks — common on holidays or quiet sprints — the code step will produce an empty blocks array and Slack will reject the API call. Add a conditional check in your Node.js code step: if the task array length is zero, return a short 'No tasks due today' message instead of an empty payload. Alternatively, add a Filter step between the Wrike and code steps that halts the workflow when no tasks are returned, avoiding a Slack post entirely.

1. 1Open the Node.js code step editor
2. 2Add an array length check at the top of the function
3. 3Return a fallback message object if tasks.length === 0
4. 4Re-test the step with an empty array to confirm the fallback triggers

Workflow Canvas > Test Workflow (top bar)

Test the full workflow end-to-end

Click 'Test Workflow' at the top of the canvas. Pipedream runs each step in sequence using live data. Watch the step-by-step output panel on the right — each step shows green (pass), yellow (warning), or red (error). Check the Slack channel after the test run to confirm the message appeared with correct formatting. Verify task titles, assignee names, due dates, and the permalink to the Wrike task all render correctly.

1. 1Click 'Test Workflow' in the top bar
2. 2Watch each step turn green in the execution panel
3. 3Open your Slack channel and confirm the message posted
4. 4Click a task permalink in the Slack message to confirm it links correctly in Wrike
5. 5Check that overdue tasks appear in the correct section of the summary

Workflow Canvas > Deploy (top right button)

Deploy and confirm the schedule is active

Click the 'Deploy' button in the top right of the workflow canvas. Pipedream changes the workflow state from Draft to Active. You'll see a confirmation banner and the workflow card in your dashboard will show an 'Active' badge. Check the 'Logs' tab the next morning to confirm the first real scheduled run completed without errors. The log will show each step's duration and output.

1. 1Click the blue 'Deploy' button in the top right
2. 2Confirm the status badge on the workflow card switches to 'Active'
3. 3Navigate to the 'Logs' tab on the workflow
4. 4Check back the next morning to review the first real execution log

pipedream.com > Workflows > [Your Workflow] > Logs

Monitor and iterate on message format

After the workflow runs for a week, review whether the task grouping and field selection are actually useful to your team. Pipedream's Logs tab shows the full input and output of every step in every historical run — use this to debug any formatting issues without re-running the live workflow. Common improvements at this stage: adding task priority field, linking to the specific Wrike project (not just the task), and threading replies so the channel stays clean.

1. 1Open your workflow and click the 'Logs' tab
2. 2Select any past run to inspect step-by-step inputs and outputs
3. 3Edit the Node.js code step to adjust grouping or add fields
4. 4Click 'Deploy' again after any code changes to push updates live