Destinations Overview
What Destinations Do
Destinations push lead evaluation results from TrailSpark to your CRM, marketing automation, or analytics platforms. After a lead is evaluated, TrailSpark writes the score, reasoning, and evaluation date to the configured fields in each active destination.
Available Destinations
| Destination | Write Target | Objects |
|---|---|---|
| Salesforce | Lead, Contact, Account | Score, reasoning, evaluation date, propensity |
| HubSpot | Contact, Company | Score, reasoning, evaluation date, propensity |
| Airtable | Contacts, Companies | Score, reasoning, evaluation date, propensity |
Destinations vs Integrations
Integrations pull data into TrailSpark (signal sources). Destinations push data out of TrailSpark (evaluation results). You can use the same platform for both -- for example, Salesforce as both a signal source and a score destination.
Data Sent to Destinations
Each destination push includes:
| Field | Description |
|---|---|
| Score | Lead evaluation score (text: hot, warm, or cold) |
| Reasoning | AI-generated evaluation reasoning |
| Evaluation Date | When the evaluation occurred |
| Propensity Score | Account-level propensity: high, medium, or low (Salesforce and HubSpot only) |
Results are sent after each evaluation completes -- whether triggered by batch processing, re-evaluation, or manual evaluation.
Configuration
Go to Settings > CRM Integration > Destinations tab to see all available destinations. Each card shows whether the destination is currently active.
All destinations follow the same setup pattern:
- Select the connected integration to use
- Toggle Send Evaluations on
- Map TrailSpark fields to your platform's fields
- Optionally configure record creation and propensity score mapping
- Save
The platform must be connected as a CRM integration first (Settings > CRM Integration > Connect tab). Only Owner or Admin roles can configure destinations.
Multiple Destinations
You can enable multiple destinations simultaneously. All active destinations receive the same evaluation data with their own independent field mappings.
