ShellOrbit / Integrations

Keep the providers you already use.

Receive HTTP webhooks from your existing services. Start with a provider guide, a test event, and a verified delivery.

Payments

Stripe and Paddle

Keep an inspectable trail for billing events.

Learn more →

Commerce

Shopify

Understand delivery failures around order workflows.

Learn more →

Development

GitHub

Connect repository events with explicit redelivery handling.

Learn more →

Payments

Stripe setup guide — receive payment and subscription events, configure the endpoint signing secret, and verify the first delivery.

Paddle setup guide — connect notification destinations and validate the Paddle signature before forwarding.

Commerce

Shopify setup guide — receive store events and configure HMAC verification with your app’s appropriate secret.

Development

GitHub setup guide — receive repository events, verify the webhook secret, and plan explicitly for redelivery.

Other HTTP providers

ShellOrbit can receive HTTP webhook requests from other services. Native signature verification currently supports the providers above and the ShellOrbit format. Check your provider’s request format, retry behavior, and payload limits before moving production traffic.

A safe first connection

  1. Create a staging endpoint and set a test destination.
  2. Configure the provider’s webhook URL and secret.
  3. Send the provider’s test event.
  4. Confirm the signature result and destination response in Events.
  5. Move production traffic only after your handler verifies signatures and handles duplicates.

Start with one provider

Give your next webhook a clear destination.

Create an endpoint, connect your handler, and send a test event.