Webhooks

SaaSFlow consumes webhooks from integration providers to keep imported data fresh. We don't yet emit webhooks back to customer endpoints — see Outbound webhooks below.

Inbound webhooks (handled by SaaSFlow)

You don't configure these — they're set up automatically when you connect the corresponding integration.

Stripe

Endpoint: https://saasflow.com/api/webhooks/stripe

Events processed:

• customer.* — customer create / update / delete.
• customer.subscription.* — subscription lifecycle.
• invoice.* — invoice events that drive MRR and recognised revenue.
• charge.*, payment_intent.* — transaction-level inflows.
• refund.* — refunds applied to existing transactions.
• payout.* — payouts to bank accounts.

Stripe's signature is verified using the integration-specific webhook secret stored at connect time.

HubSpot

Endpoint: handled at /api/webhooks/hubspot.

Events processed:

• Commerce subscription create / update / cancel.
• Contact create / update.
• Deal create / update.

Outbound webhooks

Customer-configurable outbound webhooks (SaaSFlow → your endpoint) are not available yet. If you need notifications of changes in SaaSFlow:

• Slack — the Slack integration pushes change notifications to a Slack channel.
• Polling — call the API on a schedule. The data slices return current values; the customerChanges and mrrChangeEvents slices return changes since a given date.
• MCP for LLM workflows — let a hosted client poll on its own. See MCP overview.

Outbound webhooks are on the roadmap. Email support@saasflow.com with the use case if you'd find this valuable — it helps us prioritize.