Integrations

Pipe events out. Slack, webhooks, Segment, Zapier.

Forward tour, checklist, and announcement events to Slack channels, generic HTTPS webhooks, or your Segment workspace. One delivery worker handles HMAC signing, exponential-backoff retries, and auto-pause on sustained failures so a flaky endpoint can’t break Steppr.

Outbound destinations
    Slack #activation
    tour.completed · announcement.cta_clicked
    Webhook · api.example.com
    all events · HMAC-signed
    Segment · prod-write-key
    mapped to track() events
    Webhook · staging
    paused after 5 failures
POST /webhooks/steppr
X-Steppr-Signature: t=1715346721,v1=…
{ "type": "tour.completed", "endUserId": "u_42", … }
What ships
  • Generic webhooks: HMAC-SHA256 signed JSON, replay-protection timestamps, idempotency event ids
  • Slack: paste an incoming-webhook URL, pick events, get formatted block-kit messages in your channel
  • Segment outbound: forward Steppr events to your Segment workspace via the track API
  • Segment inbound: pipe identify/track from Segment into Steppr without re-instrumenting steppr.identify on your site
  • Test endpoint, deliveries log, manual retry, signing-secret rotation - all from the dashboard
  • Auto-pause on 5 consecutive failures + email alert; resume in one click after fixing
  • Zapier on the roadmap; today, point Webhooks-by-Zapier at the generic endpoint
How it works

Integrations, in detail.

01

One delivery worker, four destinations.

Every integration is a destination type on the same webhook delivery worker. Register an endpoint, pick which events it receives, and Steppr signs, delivers, retries with exponential backoff and dead-letters after repeated failure. Slack, Segment and Zapier are formatters on top of that worker, not separate systems.

  • Events: tour.viewed, tour.started, tour.step_completed, tour.completed, tour.dismissed, checklist.item_completed, checklist.completed, announcement.viewed, announcement.dismissed, announcement.cta_clicked
  • Headers: X-Steppr-Signature, X-Steppr-Event-Id, X-Steppr-Timestamp
02

Slack for activation visibility.

Paste a Slack incoming-webhook URL, subscribe to tour.completed and announcement.cta_clicked, and your #activation channel sees each one as a formatted message. Same retry behaviour as any webhook.

03

Segment in both directions.

Outbound, Steppr maps its events into Segment’s track format and sends them to your write key. Inbound, point a Segment destination at Steppr’s Segment-compatible identify and track endpoints and skip instrumenting steppr.identify() on your site entirely.

04

Operable from the dashboard.

Send a test event, read the last hundred deliveries per endpoint, retry one by hand, rotate the signing secret. If an endpoint fails five times in a row it pauses and you get an email; fix it and resume in one click.

Plans. All integrations are available on every paid tier. There is no Scale-only gate. See pricing

Common questions

Integrations FAQ.

Straight answers. If yours isn't here, email hello@steppr.io and a founder replies.

Each payload is signed with HMAC-SHA256 using a per-endpoint secret you can rotate from the dashboard. A timestamp header protects against replay and an event id header lets you deduplicate.

Not yet. Today you use Zapier’s Webhooks-by-Zapier Catch Hook as the destination URL and receive Steppr’s canonical event JSON. A directory-listed Zapier app is on the roadmap.

Deliveries retry with exponential backoff. After five consecutive failures the endpoint auto-pauses and you receive an email. Once it is fixed, resume from the dashboard and retry any missed deliveries manually.

Try integrations free for 7 days.

No card to start. The trial unlocks Growth-tier features so you can evaluate the whole product, not a stripped-down preview.