Integrations and automations

Destinations you can publish to

Discord, Slack, Telegram, Microsoft Teams, Email, Jira, SMS and WhatsApp (via your Twilio account), and custom webhooks that receive the whole release as JSON.

You can connect several of the same type, two Discord channels, three webhooks, and give each a name; that name is how it appears in publish menus and logs.

Live means live

Every connection is verified when you save it: Discord webhooks are checked silently, Slack, Teams, Telegram and Twilio get a small "Shipnote connected" test message, and custom endpoints get a ping. A connection that fails verification is never saved, so a Live badge always means the destination actually works.

The delivery log

Every send, manual or automated, success or failure, is recorded in the Delivery log tab, filterable by connection. Webhook deliveries keep the full exchange: the JSON payload sent, the response body and the status code, so you can debug your endpoint without guessing.

Push to Publish (automations)

An automation turns activity into announcements. Choose when it runs (every push, or a daily, weekly or monthly digest), which outputs to generate, and what it does with them:

• Draft only leaves a release waiting for your review.
• Auto-send generates and delivers straight to your chosen destinations. Each destination gets its native format when you selected that channel, otherwise the first channel you picked.

Wiring up the push trigger

Repos connected through the one-click GitHub connect need no wiring at all: pushes to the default branch already reach Shipnote and run your automations.

For token-connected repos and other providers, copy the automation's hook URL into your repo once:

• GitHub (token connections): Settings → Webhooks → Add webhook, content type application/json, just the push event.
• GitLab: Settings → Webhooks.
• Bitbucket: Repository settings → Webhooks.
• Anything else: curl the URL from any CI step.

Every run appears under the automation with its status.