Connect a signal provider in three steps: authorize the integration, map signal fields to canonical schema, set threshold and routing rules. Once active, signals flow into the signal stream and trigger agents and workflows.
Step 1 — Authorize
Settings → Signals → Add Source → pick a provider (Bombora, G2, custom webhook). Authorize via API key, OAuth, or webhook endpoint depending on the provider. Wait for the green Connected badge.
Step 2 — Map fields
Each signal source has its own field schema. Map the source's fields to turgo's canonical signal schema: account identifier (domain or external ID), signal type (intent, surge, news), signal value (topic, score, event), timestamp, and confidence. Most major providers have pre-built mappings — review and adjust if needed.
Step 3 — Set thresholds and routing
Not every signal should trigger action. Set the threshold (how strong does the signal need to be?) and the routing (which agent or workflow consumes it?). Common configuration: above-threshold signals on ICP-fit accounts → AI SDR; below-threshold or non-ICP → log only.
Verify with sample signals
Once active, the source begins streaming signals. Open Signals → Stream → filter to this source → confirm signals are arriving and routing correctly. If signals aren't arriving, check the integration log for auth or schema errors.
Tuning over time
Initial thresholds are guesses. Review weekly: are above-threshold signals producing reply rates higher than baseline? If yes, the threshold is well-calibrated. If no, it's too low (signals are noisy). If reply rates are excellent but volume is too low, it's too high.
