
Push Notifications now support optional redirection and actions fields.
Use redirection to open a URL when a user taps the notification. Use actions to show up to four buttons on long-press.
redirection: HTTPS URL opened on notification tap.actions: up to 4 action buttons shown on long-press.type:
open_url: opens the provided URL in browser.webhook: triggers backend webhook call (GET or POST).This feature is available in the ActivitySmith iOS app version 1.1.0 and newer.
{
"title": "Build Failed 🚨",
"message": "CI pipeline failed on main branch",
"redirection": "https://github.com/org/repo/actions/runs/123456789",
"actions": [
{
"title": "Open Failing Run",
"type": "open_url",
"url": "https://github.com/org/repo/actions/runs/123456789"
},
{
"title": "Create Incident",
"type": "webhook",
"url": "https://hooks.example.com/incidents/create",
"method": "POST",
"body": {
"service": "payments-api",
"severity": "high"
}
}
]
}All SDKs, CLI, and the GitHub Action now support these optional fields in push notification requests.

ActivitySmith now provides a skill you can install with npx skills add to send Push Notifications and trigger Live Activities from your coding agents.
npx skills add ActivitySmithHQ/activitysmith-cli --skill activitysmithRepository: github.com/activitysmithhq/activitysmith-cli
./skills/activitysmith/scripts/send_push.sh \
-t "Codex task finished" \
-m "Implemented OAuth callback fix, added regression tests, and opened PR #128."
activity_id="$(./skills/activitysmith/scripts/start_activity.sh \
--title "Codex: migrate billing webhooks" \
--subtitle "Analyzing handlers" \
--type "segmented_progress" \
--steps 4 \
--current 1 \
--id-only)"
./skills/activitysmith/scripts/update_activity.sh \
--activity-id "$activity_id" \
--title "Codex: migrate billing webhooks" \
--subtitle "Implementing + tests" \
--current 2
./skills/activitysmith/scripts/end_activity.sh \
--activity-id "$activity_id" \
--title "Codex: migrate billing webhooks" \
--subtitle "Done" \
--current 4 \
--auto-dismiss 2
Use ACTIVITYSMITH_API_KEY for auth in your shell or environment.

ActivitySmith now integrates with Zapier so you can send iOS Push Notifications and Live Activities from your automations.
Connect ActivitySmith to any Zap and route runtime events from your apps, scripts, and workflows to paired team devices.
Visit ActivitySmith integration on Zapier for more details.

Use channels to route push notifications and Live Activities to specific users and devices.
Channels are now supported across all ActivitySmith SDKs and integrations, and the documentation has been updated with channel examples.

You can also scope API keys to specific channels for tighter control over where updates can be delivered.
Channels let you route updates to the right audience, for example: #engineering, #ios-builds, #marketing.
{
"title": "Build Failed",
"message": "CI pipeline failed on main branch",
"channels": ["ios-builds", "engineering"]
}If channels are omitted, delivery behavior stays unchanged.

Add your team members to keep everyone notified and up to date with shared push notifications and Live Activities.
When your backend, scripts, or automations send push notifications or Live Activities, each update is delivered to all paired iOS devices on your team.


The official ActivitySmith SDK suite is now available across all major backend stacks.
You can now integrate ActivitySmith with:
# Node.js SDK
npm i activitysmith
# Python SDK
pip install activitysmith
# Go SDK
go get github.com/ActivitySmithHQ/activitysmith-go
# PHP SDK
composer require activitysmith/activitysmith
# Ruby SDK
gem install activitysmith
# ActivitySmith CLI
npm i -g activitysmith-cliFull SDK documentation:

The official ActivitySmith GitHub Action is now live on the GitHub Marketplace.
Connect your CI and deployment workflows directly to ActivitySmith so your team gets real-time updates on their mobile devices.
You can now:
For lightweight updates like deploy completed, build failed, or rollback started, send a push notification in a single step:
- name: Send push notification
uses: ActivitySmithHQ/[email protected]
with:
action: send_push_notification
api-key: ${{ secrets.ACTIVITYSMITH_API_KEY }}
payload: |
title: "ActivitySmith Deployment"
message: "New release deployed to production."This is a good fit for one-off alerts where you want immediate visibility but no ongoing activity timeline.
For long-running workflows, start the activity, post as many progress updates as needed, then end it when complete.
The start_live_activity step returns live_activity_id, which you pass into update/end steps.
- name: Start live activity
id: start_activity
uses: ActivitySmithHQ/[email protected]
with:
action: start_live_activity
api-key: ${{ secrets.ACTIVITYSMITH_API_KEY }}
payload: |
content_state:
title: "ActivitySmith API Deployment"
subtitle: "ci: install & build"
number_of_steps: 3
current_step: 1
type: "segmented_progress"
- name: Update live activity
uses: ActivitySmithHQ/[email protected]
with:
action: update_live_activity
api-key: ${{ secrets.ACTIVITYSMITH_API_KEY }}
live-activity-id: ${{ steps.start_activity.outputs.live_activity_id }}
payload: |
content_state:
title: "ActivitySmith API Deployment"
subtitle: "ci: tests"
current_step: 2
- name: End live activity
uses: ActivitySmithHQ/[email protected]
with:
action: end_live_activity
api-key: ${{ secrets.ACTIVITYSMITH_API_KEY }}
live-activity-id: ${{ steps.start_activity.outputs.live_activity_id }}
payload: |
content_state:
title: "ActivitySmith API Deployment"
subtitle: "done"
current_step: 3After months of building, ActivitySmith is live! Trigger Live Activities and send Push Notifications to your iOS device(s) with a simple API call.
Start here:
Try it now at activitysmith.com.