Inbound Webhooks for GitLab, Railway, and Custom JSON Events

Use inbound webhooks when the service you care about does not have a native ActivitySmith integration yet. Railway deploys, GitLab pipelines, internal tools, and any custom JSON source can send events into ActivitySmith so your team sees backend work on the lock screen while it is still happening.

Choose Live Activities for rollouts, pipelines, and other long-running work. Choose push notifications for one-off outcomes, failures, and handoffs that someone should see immediately.

ActivitySmith accepts inbound webhooks from Railway, GitLab, and any service that sends custom JSON.

What's new

• Railway inbound webhooks for deployment events.
• GitLab inbound webhooks for pipelines, merge requests, issues, releases, comments, and repository events.
• Generic JSON webhooks for custom backend events and no-code tools.
• Delivery log for recent webhook requests, payloads, processing errors, and verification failures.

Webhooks also support secret-token verification and channel targeting, so incoming events can be checked before processing and routed to the right people and devices.

Railway deployment events

Railway deployment state can stay visible from rollout start to success or failure, without turning the release into another tab to watch.

For example, deployment start and progress events can update a Live Activity, then production success or failure can arrive as a Push Notification.

Good fits:

• production deploy started
• deployment failed
• rollback started
• deployment succeeded
• service metadata changed

GitLab pipeline and project events

GitLab pipeline, review, and release state can follow the work from the lock screen while it moves.

You can route pipeline events to Live Activities, send Push Notifications for failed jobs or review handoffs, and open the related GitLab page from the notification action.

Generic JSON webhooks

Generic webhooks are the escape hatch.

If a service can send JSON, it can send an event into ActivitySmith. Paste a sample payload, map JSON fields into the notification or Live Activity text, and choose the delivery mode that fits the event.

For optional verification, send the generated secret in:

X-ActivitySmith-Webhook-Secret: YOUR_SECRET

This is useful for internal tools, workers, cron jobs, low-code automations, or webhook providers that do not need a dedicated preset yet.

Delivery log

Inbound webhooks include a delivery log for the inevitable "did the webhook fire?" moment.

Availability

Inbound webhooks are available now in the ActivitySmith dashboard.

Start with Railway, GitLab, or Generic JSON, then choose whether that endpoint should deliver Push Notifications or Live Activities.

More integrations such as Vercel, Sentry, Stripe, and Polar are coming soon.