Integrations
Choose sources and destinations that give Prevenue useful account-level evidence.
Integrations connect Prevenue to the systems that know what customers do, what they pay for, and where your team reviews revenue moments.
Open Settings > Integrations to search providers, filter by setup state, create credentials, open setup guides, test delivery, and review recent activity.
Default setup path
Most workspaces should start with these three actions:
- Connect Stripe so Prevenue has billing truth for subscriptions, trials, plans, invoices, MRR, payment state, and monitored revenue.
- Install the Web SDK so browser-visible intent and account traits can arrive from the product UI.
- Add Direct API for backend source-of-truth events such as durable usage, activation, setup milestones, lifecycle changes, metered usage, and completed state changes.
PostHog and Segment are good existing-pipeline routes when they already contain clean product events with account identity. Use them to forward a small allowlist, not a full analytics firehose.
Supported source paths
| Source | Use it for | Setup article |
|---|---|---|
| Stripe | Customer billing context, subscriptions, invoices, plans, monitored revenue, billing events. | Stripe Connect Setup |
| Web SDK | Browser-visible intent, prompts, checkout starts, cancel intent, setup friction, supplemental product behavior. | Web SDK Installation |
| Direct API | Backend source-of-truth events, durable product usage, account setup, lifecycle state, metered usage, completed state changes. | Direct API Installation |
| PostHog | Selected product events forwarded through PostHog Data Pipelines. | PostHog Source Setup |
| Segment | Segment track and group payloads normalized into revenue semantics. | Segment Source Setup |
Start with account identity and the strongest evidence for the motion you want to operate first. Stripe, Web SDK, and Direct API answer different setup questions, so they can be installed together without duplicating the same event.
Supported destination paths
| Destination | Use it for | Setup article |
|---|---|---|
| Slack | Internal alerts and team review loops. | Slack Destination Setup |
| Webhook | Signed JSON signal payloads to your own systems. | Webhook Destination Setup |
| Customer.io | Lifecycle sync, managed audiences, and manual segment data actions. | Customer.io Integration |
| HubSpot | CRM company property sync for native HubSpot workflow automation. | HubSpot Integration |
| Email foundation | Transactional paths managed by Prevenue infrastructure. | Destinations |
Prevenue routes signal output. It does not own downstream campaigns, CRM tasks, sequences, or customer lifecycle execution.
Connection states
Integrations use status labels to separate setup from successful activity:
| State | Meaning |
|---|---|
| Needs setup | No usable credential, connection, or destination exists yet. |
| Ready to verify | Setup exists, but Prevenue has not seen a successful event or delivery yet. |
| Connected | Recent successful activity confirms the integration is working. |
| Needs attention | Setup exists, but recent activity failed, was rejected, or needs review. |
| Disabled | The integration was intentionally turned off. |
| Coming soon | The provider is catalog-only and not live in the current workspace. |
Old successful activity should not make an integration look connected when the current key, destination, or credential is missing or disabled.
Recommended order
- Connect Stripe.
- Install Web SDK and send one account-scoped browser event.
- Create a Direct API key and send one account-scoped backend event.
- Review events in Event Log and Payload Review.
- Confirm mappings in Event Mapping and Signal Readiness.
- Run the Revenue Signal Scan.
- Review signals in Signals.
- Add one destination and send a test.
Expand integrations after the first workflow produces useful, reviewable signals.
Credential boundaries
Raw API keys, OAuth tokens, webhook URLs, signing secrets, and provider credentials should not appear in app screenshots, logs, support messages, Linear comments, or docs examples.
Prevenue stores customer/provider credentials through server-side credential helpers. Workspace API keys are returned only once on create or rotate. Copy them into the provider you are configuring, then treat the Prevenue UI as the place to rotate or revoke them later.