Destinations
Route reviewed Prevenue signals to the team workflows that need them.
Destinations send signal output out of Prevenue after the signal has been evaluated. They are for alerting, handoff, and downstream workflow intake. They do not make Prevenue the owner of CRM tasks, campaigns, support tickets, or lifecycle execution.
Open Settings > Integrations to manage Slack, webhook, Customer.io, and HubSpot destinations.
Destination types
| Destination | Best for | Setup article |
|---|---|---|
| Slack | Human review, internal alerts, sales or success team visibility. | Slack Destination Setup |
| Webhook | Custom systems that receive signed JSON signal payloads through selected endpoints. | Webhook Destination Setup |
| Customer.io | Lifecycle sync, managed audiences, and manual segment data actions. | Customer.io Integration |
| HubSpot | CRM company property sync for workflow automation, with optional contact property updates. | HubSpot Integration |
| Email foundation | Prevenue-managed transactional paths and future lifecycle routing. | Workspace, Team, and Notification Settings |
Before routing signals
Confirm the signal workflow is useful before sending it downstream:
- Source events are arriving.
- Mappings are confirmed.
- Signal readiness is active or ready to preview.
- The signal detail page shows actionable evidence.
- The destination has a successful setup test.
- The receiving team knows what to do with the signal.
- The Funnel selects the exact endpoint or endpoints that should receive payloads.
If a destination receives noisy or incomplete messages, fix event quality or Funnel eligibility/follow-up criteria before expanding delivery.
What a good routed signal includes
A routed signal should include:
- Account name or account key.
- Signal type and motion.
- Reason and recommended action.
- Evidence summary.
- Priority or confidence.
- Destination or route context.
- Idempotency key or delivery identifier for webhook-style receivers.
Webhook payloads may include account intelligence and evidence references when available. Slack alerts are optimized for human review.
Funnels use selected teams for internal notifications and optional external destinations for Webhook and Customer.io delivery. Webhook routes choose 1-5 endpoints from the workspace endpoint list. Customer.io routes can also keep managed audiences such as upgrade_ready, annual_conversion, retention_rescue, support_recovery, trial_conversion, and checkout_recovery current for Journey entry and suppression logic. Read Signal Delivery Payloads for the shared payload shape, Customer.io shaping, compatibility fields, and safety limits.
Delivery health
Use the destination detail views to check:
- Last activity.
- Last success.
- Last failure code or response.
- Active route count.
- Recent rejected or failed delivery activity.
- Whether the destination is disabled.
For setup-specific failures, read Troubleshooting.