What GTMOS is actually connected to, and how much of each connection has genuinely run. One tool executes against a real instance, one runs on a simulated adapter, and two are contracts that work locally but have never met the real service. Every number here is derived from stored deliveries, sync runs and enrichment attempts.
Two independent axes: what the configuration does, and how much of it has ever happened
Product Analytics · Inbound only
Observes the product. GTMOS turns its events into account-level signals and the product-qualified rule.
Related surfaces
A boundary is only green when requests have genuinely been exchanged with a real running instance of the tool. Nothing is labelled “Connected”, because none of these has ever been.
Last failure 3d ago: rejected: signature check failed: signature mismatch
Still required to make this live
The inbound path is real code and is exercised: events in PostHog's documented shape are accepted, deduplicated, normalised and turned into signals. Not one of them came from PostHog itself.
docs/research/posthog.mdIntegrationsdocs/integrations.mdEnrichment · Inbound only
Buys commodity enrichment. GTMOS keeps the merge policy: a Clay value enters through the same provenance and conflict rules as any other provider.
Still required to make this live
The boundary is built against Clay's documented Public API and signed-webhook contract and tested locally against that contract. Nothing has ever been requested from clay.com.
docs/clay-live-setup.mdResearch: Claydocs/research/clay.mdWorkflow Automation · Both directions
Moves bytes between systems. Anything that decides revenue stays in GTMOS; anything that is plumbing lives on the n8n canvas.
Last failure 5d ago: failed: OperationalError: database connection reset (simulated)
Still required to make this live
n8n runs locally in Docker on the pinned image n8nio/n8n:2.40.5. Its workflows fire against this API for real, and the deliveries below are those executions.
docs/n8n.mdResearch: n8ndocs/research/n8n.mdCRM · Both directions
Where the revenue team works. GTMOS writes only its own gtmos_* fields and never applies an inbound CRM change as truth.
Last failure 8d ago: 503 Service Unavailable (simulated) — older than the 7-day window, so it does not affect health.
Still required to make this live
The simulated adapter is exercised end to end and every sync it performs is labelled SIMULATED. The live adapter is implemented against the documented v3 batch-upsert API and has never run against a real portal.
docs/research/hubspot.mdIntegrationsdocs/integrations.md