INTEGRATION CENTER · PHASE 4
Connect Watchdog directly to the systems that run your business.
Use native CRM sync for continuous context, or Zapier and signed webhooks for flexible automation. Every path stays scoped, revocable and auditable.
Native CRMPhase 4 liveBoldTrail Direct beta · Zapier · webhooks · governed CRM context
Sign in to manage integrations
Your connections, keys and permissions are account-scoped.
Integrations require Pro+ or Teams
Zapier, CRM context and automation webhooks are professional workflow capabilities.
Integration Center could not load
Try again from this page.
bt
TeamsBOLDTRAIL DIRECT · BETA
Native CRM connection
Bring approved BoldTrail / kvCORE relationship context into Watchdog without routing it through Zapier.
Native CRM connections are a Teams capabilityPro+ keeps Zapier and generic webhooks. Teams adds managed direct CRM synchronization.
View TeamsCONNECT
BoldTrail / kvCORE
Enter a kvCORE API token. Watchdog validates it with BoldTrail before moving it into Supabase Vault. The token is never shown again.
Only the approved Watchdog CRM context contract is retained. Arbitrary raw provider contact payloads are not stored.
CONNECTION
ReadyBoldTrail Direct
BoldTrail CRMLast successful syncNot yet
Last batch0 contacts
Total normalized0
Failures0
Automatic incremental sync every 15 minutesWatchdog requests contacts updated since the last completed cursor, with a small overlap to prevent boundary misses.
WHAT SYNCS
Relationship context, not a raw CRM mirror
Contact identityProvider ID, display name and valid email when available.
Lead and deal contextkvCORE status, deal type and source become normalized workflow context.
Assignment contextProvider agent references can remain as CRM relationship metadata.
Watchdog property truth stays separateCRM fields never silently replace governed property facts or source lineage.
DIRECT CRM SYNC HISTORY
Recent BoldTrail runs
| Started | Trigger | Status | Seen | Normalized | Completed |
|---|
No sync runs yetThe first run is queued when a valid connection is created.
WATCHDOG FOR ZAPIER
Automation access
_
Create a dedicated key, choose only the capabilities a workflow needs, and revoke it at any time.
YOUR KEYS
No Zapier keys yetCreate one when you are ready to connect Zapier.
CRM CONTEXT
What Watchdog can understand
CRM data is customer and workflow context. Watchdog's governed property records remain the property-data source of truth.
Records received0
Linked to property0
Latest context syncNot yet
CRM owns relationship contextLead stage, workflow state and customer associations.
Watchdog owns governed property factsAssessment, taxes, property changes, lineage and derived signals.
Intelligence access is separateCRM context stays out of Intelligence until explicitly enabled.
GENERIC CONNECTION
Webhook bridge
Use Zapier/Make webhook URLs, CRM middleware or another public HTTPS endpoint.
SECURITY CONTRACT
Scoped, revocable, auditable
Secrets stay server-sideReusable CRM credentials live in Vault, not browser-readable tables.
CRM data is normalizedDirect and webhook ingestion use a fixed Watchdog contract.
Sync and delivery historySuccess, failure and retry evidence is retained for operations.
Intelligence permission is explicitEach CRM connection has an auditable off-by-default switch.
YOUR WEBHOOK CONNECTIONS
Connected workflows
No webhook connections yetCreate a bridge above or connect through Zapier.
DELIVERY LOG
Recent outbound activity
| Event | Connection | Status | Attempts | HTTP | When |
|---|
No deliveries yetTest a webhook connection or wait for a subscribed Watchdog event.
PHASE 4 · PROVIDER FRAMEWORK
One native connector framework, not one-off CRM code.
BoldTrail is the first provider on the shared direct-sync runtime. The same Vault boundary, sync history and normalized context contract can support the next demanded CRM.