Can it skip weekends and public holidays?

Weekends, yes, out of the box: the schedule runs Monday to Friday. Public holidays need a list. The setup guide shows where to add dates the run should skip, and the workflow checks that list before it reads anything.

What if someone has no Slack account matching their Asana email?

Their tasks are not lost. They appear in the project channel summary under their Asana name with a note that no Slack user matched, and the run carries on for everyone else.

Will it nag people about tasks due today?

No. Only tasks with a due date before today are included. A task due today is still on time at 08:30, and the next morning it appears if it is still open.

Is there a Make version?

Yes. The blueprint in the package uses the same schedule, Asana list-tasks modules, an array aggregator grouped by assignee and two Slack modules. Zapier is not included: turning one task list into one message per person needs Looping by Zapier plus a Code step, and it stops being a template at that point.

AsSMade to order

Projects & operations

Asana overdue tasks → Slack DM to each assignee + project channel summary

Overdue Asana tasks reach their owner by Slack DM at 08:30 every weekday.

Due dates in Asana only work when someone looks at them. Each weekday morning this package reads every open task past its due date in the projects you choose, groups them by assignee and sends each person one Slack DM listing their tasks, oldest first, with links. The project channel gets a one-line count. Nothing is reassigned or rescheduled; people just stop being surprised.

How it works

As
Trigger
Schedule: every weekday at 08:30 in your timezone (n8n Schedule Trigger), then a read of the open tasks in each chosen Asana project
Asana
As
Step 1
Pull open tasks past their due date
For each project ID in the setup list, Asana's tasks-in-project call (completed_since=now) returns open tasks with name, assignee, due date, section and permalink; the run keeps those due before today. It works on the free Personal plan.
if
Step 2
Group the tasks by assignee
Tasks without an assignee or a due date are set aside. The rest are grouped per person and sorted by days overdue, so the oldest item sits at the top of each list.
S
Step 3
DM each assignee their list
The assignee's Asana email is matched to a Slack user with users.lookupByEmail, then one chat.postMessage to that user lists their overdue tasks with project name, days overdue and a link to each task.
S
Step 4
Post a count to each project channel
One line per project: how many tasks are overdue, who holds them, and how many have no assignee, so the project lead sees the shape without opening Asana.

What changes once it runs

Each person gets one DM with their overdue tasks, oldest first, before the day starts.
Project leads see a per-project count in the channel without opening Asana.
Unassigned overdue tasks are counted separately, so nobody assumes someone else has them.
Nothing in Asana changes; the package reads tasks and writes only to Slack.

What you get

n8n workflow export, tested against a sample project
Setup guide covering the Asana token, the Slack app scopes and the project-to-channel list
Recorded walkthrough of one morning run, from the project read to the DMs
Make blueprint: Asana list-tasks modules, an array aggregator grouped by assignee, two Slack modules

Before you start

Asana, any plan including Personal, with a personal access token that can see the chosen projects
Slack with permission to install an app carrying the users:read.email, chat:write and im:write scopes, so it can find people by email and DM them
Assignee email addresses that match between Asana and Slack, which is how each DM finds its person
n8n, cloud or self-hosted; nothing calls in, so no public URL is needed

Built for

Questions before you buy

Can it skip weekends and public holidays?: Weekends, yes, out of the box: the schedule runs Monday to Friday. Public holidays need a list. The setup guide shows where to add dates the run should skip, and the workflow checks that list before it reads anything.
What if someone has no Slack account matching their Asana email?: Their tasks are not lost. They appear in the project channel summary under their Asana name with a note that no Slack user matched, and the run carries on for everyone else.
Will it nag people about tasks due today?: No. Only tasks with a due date before today are included. A task due today is still on time at 08:30, and the next morning it appears if it is still open.
Is there a Make version?: Yes. The blueprint in the package uses the same schedule, Asana list-tasks modules, an array aggregator grouped by assignee and two Slack modules. Zapier is not included: turning one task list into one message per person needs Looping by Zapier plus a Code step, and it stops being a template at that point.

Nearby on the shelf

Whole catalog