Connect ShipPulse to 5,000+ tools — no code required. Use ShipPulse webhooks as triggers and the REST API as actions.
ShipPulse integrates with automation platforms in two directions:
📥 Triggers (ShipPulse → your tool)
ShipPulse sends a webhook event when something happens — new testimonial, monitor down, changelog published. Your automation tool receives it and can act on it.
📤 Actions (your tool → ShipPulse)
Your automation tool calls the ShipPulse REST API — create a testimonial, post a changelog, or add a subscriber — using your API key.
You need two things before you start: a ShipPulse API key (Settings → API Keys, requires Pro plan) and your Project ID (from the project URL).
Example Zap: New testimonial → send to Slack
event: testimonial.received)data.rating is 5POSThttps://shippulse.dev/api/v1/testimonialsAuthorization: Bearer YOUR_API_KEY, X-Project-Id: YOUR_PROJECT_ID, Content-Type: application/json{
"author_name": "{{full_name}}",
"author_email": "{{email}}",
"content": "{{review_text}}",
"rating": {{star_rating}},
"source": "zapier"
}Useful Zaps: import reviews from a Typeform, Google Form, or HubSpot deal into ShipPulse automatically.
https://your-n8n.com/webhook/shippulse).https://shippulse.dev/api/v1/testimonialsAuthorization · Value: Bearer {{$env.SHIPPULSE_API_KEY}}X-Project-Id · Value: your project ID{
"author_name": "={{ $json.name }}",
"author_email": "={{ $json.email }}",
"content": "={{ $json.feedback }}",
"rating": "={{ $json.score }}",
"source": "n8n"
}Tip: store your API key in n8n's Credentials → Header Auth and reference it across nodes — never hardcode it in the workflow.
https://shippulse.dev/api/v1/changelogAuthorization: Bearer YOUR_API_KEY and X-Project-Id: YOUR_PROJECT_IDapplication/json{
"title": "{{1.title}}",
"content": "{{1.description}}",
"type": "feature",
"status": "published"
}Example scenario: When a GitHub issue is closed with label shipped, automatically publish a changelog entry in ShipPulse.
All endpoints are at https://shippulse.dev/api/v1/ and require two headers:
Authorization: Bearer YOUR_API_KEY
X-Project-Id: YOUR_PROJECT_ID
Content-Type: application/json| Endpoint | Methods | Use case |
|---|---|---|
| /api/v1/testimonials | GET, POST | List or create testimonials |
| /api/v1/testimonials/:id | GET, PATCH, DELETE | Manage a testimonial |
| /api/v1/changelog | GET, POST | List or publish changelog entries |
| /api/v1/changelog/:id | GET, PATCH | Update a changelog entry |
| /api/v1/monitors | GET, POST | List or create uptime monitors |
| /api/v1/incidents | GET, POST | List or create incidents |
| /api/v1/subscribers | POST | Add an email subscriber |
| /api/v1/feedback/search | GET | Search feedback posts |
Full endpoint docs: API Reference · Interactive Playground
G2 / Capterra review → ShipPulse testimonial
ZapierWhen a new review appears on G2 (via Zapier's G2 integration), push it to ShipPulse via POST /api/v1/testimonials.
New 5-star testimonial → Tweet / Slack shoutout
n8n / ZapierTrigger on testimonial.received webhook, filter rating = 5, then post to Twitter or Slack.
GitHub PR merged → Changelog entry
n8n / MakeOn GitHub 'pull_request.closed' event (merged), create a ShipPulse changelog entry with the PR title and description.
Monitor down → PagerDuty incident
Zapier / n8nTrigger on monitor.down webhook, create a PagerDuty incident. Resolve it on monitor.up.
New feedback post → Notify team in Telegram
n8n / MakeTrigger on feedback.created webhook, send a Telegram message to your team channel.
Stripe payment → Add testimonial request
Zapier / n8nAfter a Stripe payment succeeds, send an email (via Resend) asking for a testimonial with your ShipPulse collection form link.
If you'd like a native ShipPulse app in the Zapier or Make marketplace, vote for it or request it on our feedback board. We prioritize based on demand.