Send each rep their daily Outreach task list in Slack

Every weekday at 7:30am, send each of my reps a Slack direct message listing their Outreach tasks due today, so they start the day with a clear plan instead of digging through the task queue. Use a cron trigger scheduled for weekdays only, and run everything in my team's time zone so that both the definition of "due today" and the due times shown in each message line up with the rep's working day.

Start with Outreach List Tasks, filtered to tasks that are still open (not yet completed) and due today. Outreach supports range filtering on the due date, so filter[dueAt] with a range covering the start and end of today works here (the range format is 2024-01-01..2024-01-02). Page through the entire result set using cursor pagination: request page[size] with sort=id and keep following links.next until there is no next link, so a rep with heavy task volume never gets a silently truncated list.

Then call Outreach List Users to pull every user in the org and build a lookup from user id to that person's name and email address. Join each task to its owner through that lookup so every task carries a real name and email rather than a bare id. Note that Outreach has no /me endpoint, so any user resolution is done by listing users and matching on email.

Group the tasks by owner. Within each rep's group, sort the tasks by type in a fixed order: calls first, then emails, then all other action items. Format one line per task showing the prospect name and the time that task is due. At the top of each message, put that rep's total count of tasks due today so they can see their load at a glance before reading the detail.

Send one Slack direct message per rep using Slack Bot. Map each rep to their Slack account with Look Up User by Email using the Outreach email address from the user lookup, then use Send a Message to deliver the digest as a direct message. Skip any rep who has no tasks due today rather than sending them an empty message. If a rep's Outreach email has no matching Slack account, skip that rep and continue, so one unmatched user does not block everyone else's sends.

Build this as a code workflow. Every step is deterministic: fetch a filtered list, join it to users, group by owner, sort by a fixed type order, format the message, and send. There is no judgement call and no step whose shape depends on what the previous step found.