Platform

Integrations

How connectors work, soft-fail behavior, and where to start.

MoneyGap connects analysis and Fix Paths™ to the rest of your growth stack through the Integration Hub. Unavailable connectors soft-fail — they never invent findings.

Why connect / what happens today

Connect tools so MoneyGap can understand your growth stack beyond the public website (analytics, CRM, email, CMS, payments, and code).

Today:

  • Improves Integration Health and the Connection Map for your workspace
  • GitHub unlocks Developer Mode™ — Project Memory™, IDE prompts, and draft PRs only (never auto-merge to main)
  • Soft-fail: Hub issues never block reports; connections do not rewrite MoneyGap Score™
  • Most connectors stage encrypted credentials; live Engine enrichment from Hub data ships incrementally
  • No auto-publish and no auto-email to customers

The first time you click Connect in the Hub, MoneyGap asks you to acknowledge this purpose. After that, Connect proceeds normally.

How to think about connectors

  • Connect what you already use (analytics, publishing, CRM, and related tools as they become available).
  • Expect clear status when a connector is off, pending, or erroring.
  • Keep human review on anything that could publish or message customers.

Where to start

  1. Read the public Integrations overview.
  2. Open Integration Hub in the dashboard.
  3. Read Why connect, then Connect a provider (GitHub first if you want Developer Mode™).
  4. Treat Hub snapshots as staging — do not assume Engine findings already use every connected app.

API

Public API access is reserved on higher plans. See the API overview for positioning; use Documentation Center™ and Developer Hub in-app for authenticated developer surfaces.