Custom Webhooks Integration
Build custom workflows by sending Shipstar events to any HTTP endpoint. Webhooks deliver structured payloads when content is generated, approved, or published — letting you connect Shipstar to internal tools, automation platforms, or any service that accepts HTTP requests.
Event-driven architecture
Webhooks fire on key events: content generated, content approved, content published, and release detected. Each payload contains structured data about the event, the content, and the source changes — everything you need to build downstream automations.
release.detectedNew release tagged
content.generatedAI draft created
content.approvedDraft approved for publishing
content.publishedContent published to channel
Team-scoped configuration
Configure webhook destinations at the team level. Different teams can route events to different endpoints, making it easy to integrate Shipstar into existing notification pipelines and automation workflows across your organization.
https://hooks.eng.acme.io/shipstarhttps://zapier.com/hooks/catch/...Connect to any platform
Send events to Zapier, Make, n8n, or any custom backend. Webhooks use standard HTTP POST with JSON payloads, so they work with virtually any integration platform or custom service you already run.
Retry and delivery guarantees
Failed webhook deliveries are retried automatically with exponential backoff. Delivery status is logged so you can monitor reliability and debug integration issues from the Shipstar dashboard.
200500200retry #2Why use Custom Webhooks with Shipstar
- Standard HTTP POST with structured JSON payloads
- Automatic retries with exponential backoff
- Works with Zapier, Make, n8n, and custom backends
- Team-scoped webhook destinations
Works great with
Explore related pages
Ship it. Share it. Celebrate it.
Release notes on autopilot.
Free to start. Connect your repo in 30 seconds.
No credit card required · Setup in 30 seconds