Primary signal
Pickup
Assignments get picked up
More assignments are opened and started soon after the notification goes out.
Task Assignment Notifications
Ship this workflow
Pick how you want to build it.
Try it in the dashboard Fastest
Go to Workflows → New Workflow → Use sample workflow in your workspace, and select this workflow.
Try it
Build with the SuprSend Agent
Build with SuprSend MCP
When to use this workflow
A round of assignments floods the assignee. Sprint planning or triage hands out many tasks at once, and each one fires its own notification.
An urgent assignment looks the same as a routine one. Work that needs attention now arrives with no more weight than a low-priority task.
Picking up your own task triggers a pointless notification. Users who assign work to themselves get pinged for an action they just took.
An assignment sent on just one channel goes unseen. If the assignee is not checking that one channel, the handoff is missed.
How it works
1
An assignment fires
Work is assigned to someone (TASK_ASSIGNED or TASK_REASSIGNED), and the workflow starts.
Trigger
2
Self-assignments are skipped
If the assigner and the assignee are the same user, the run exits without sending.
BranchExit
3
High-priority assignments send immediately
A high-priority task notifies the assignee right away.
BranchMulti-Channel
4
Routine assignments are grouped
The first assignment sends immediately; the rest in the next 30 minutes arrive as one.
BranchBatchMulti-Channel
Best practices
Lead with the assigner and the task name
"Sarah assigned you 'Update homepage'" gets opened. "You have a new task" gets ignored.
Group the batch by project
Set the batch to group by project so each summary covers one project, which keeps it readable for people working across several at once.
Send the grouped summary within working hours
A 2 AM summary is buried by morning. Keep it inside the assignee's working hours and timezone with a time window.
Common mistakes to avoid
Tagging every assignment the same priority
Mark everything high and people stop reacting. Mark everything standard and the urgent work sits in the 30-minute batch.
Using one template for the instant alert and the grouped summary
The immediate send is a single urgent task. The grouped send is a short list. They need different layouts.
Skipping the self-action check
Without it, a user who assigns a task to themselves gets notified about their own action - a notification no one needs.
What users receive
The actual notifications this workflow sends, on each channel.
High Priority Task Assignment
Email
In-app inbox
Slack
Microsoft Teams
Android push
iOS push
Web push (Mac)
.png)
Web push (Windows)
.png)
Standard Priority Task Assignment
Email
In-app inbox
Slack
Microsoft Teams
Android push
iOS push
Web push (Mac)
.png)
Web push (Windows)
.png)
What good looks like
Fatigue signal
Opt-outs
Rising opt-outs on routine updates
When assignees start switching off standard assignment updates, they are getting more pings than the routine work needs.
Support
Frequently Asked Questions
Quick answers about setting up and running this workflow.
No. The workflow checks who acted, and when the assigner and the assignee are the same user it exits before sending. Picking up your own task stays quiet.
No. The first assignment sends immediately, so nothing waits. Every other task assigned to the same user in the next 30 minutes is grouped into one notification.
Tag it high priority. High-priority assignments send the moment they are assigned and skip the 30-minute batch. Only standard assignments are grouped.
Assignments can go out on in-app inbox, email, Slack, Microsoft Teams, and mobile or web push. Each assignee only gets the channels they have enabled, and any they have turned off in their preferences are skipped automatically.
No. This workflow notifies once per assignment. For nudges as a due date approaches, pair it with Deadline Reminders, which runs alongside it.
Trigger it with a payload shaped like the TASK_ASSIGNED event: a recipient, an actor, and a priority. You can do this from the Test button in the workflow editor, by asking the SuprSend Agent in the dashboard, or through the API, CLI, or MCP.
Ship Task Assignment Notifications in under 5 minutes.
Try directly in SuprSend
FastestSign up and test the workflow directly in the dashboard.
Build with the SuprSend Agent
Copy the prompt, paste it into the Agent in your SuprSend dashboard, and the workflow gets built for you.
Build it with SuprSend MCP
Set up SuprSend MCP in Claude Code, Cursor or Windsurf, copy the prompt, and the workflow builds itself in your workspace.