Channels
Use channels to target Push Notifications and Live Activities to the people who should see them.
Add a channels array to route the update
Channels give you a simple targeting model across backend services, scripts, CI pipelines, automations, and agent workflows. Send the update once, but decide which audience should receive it.
{ "title": "Production deploy paused", "message": "Waiting for approval before rollout resumes", "channels": ["release", "on-call"]}Use one routing model across the workflows you already run
Channels are useful when different parts of the team need different signal, even if the underlying events come from the same product or infrastructure.
Deploy and release updates
Route deploy progress to release owners and on-call teammates without notifying every paired device.
#release#on-call
Business event workflows
Send upgrades or failed payments to the people who handle revenue, support, or founder visibility.
#revenue#support
Agent review handoffs
Push generated assets, QA results, or approvals to the exact team responsible for the next step.
#design#qa
Choose who receives each update
Channels are especially useful for teams. Each person can pair their own iOS devices, while channels let you target the people or devices that should receive each Push Notification or Live Activity.
When channels help
- Release owners and on-call engineers need specific deployment updates.
- Revenue, support, and engineering follow different business events.
- An automation should notify only the team responsible for it.
Keep important updates within reach
Use ActivitySmith to follow deployments, incidents, automations, business events, and long-running tasks from your iOS devices.
