Connector Architecture

Definition

Data integration approach: each external data source connects via its own API connector (Salesforce, Gong, Google Ads, Facebook Ads, HubSpot, etc.). Enables rapid onboarding by connecting customer’s existing tools. Preferred over pre-aggregated dependencies (BigBrain/Snowflake) so external customers without monday-specific infra can use Harmony.

Related decisions

• DEC-002 — Direct API access preferred over pre-aggregated data sources
• DEC-016 — Marketing connectors as the lightweight second vector

Sources

• harmony-bizapps-sync-2026-04-12 — origin (Guy Kori provisioning Salesforce + Gong access)
• offsite-2026-04-14 — confirmed for connector-first architecture
• vision-2026-04-15 — extended to marketing connectors as second vector

Related entities

• salesforce, gong, google-ads, facebook-ads, hubspot — connector targets
• bigbrain — explicitly not the path
• guy-kori — provisions API credentials

Related concepts

• account-timeline — what the connectors feed
• marketing-connectors — the lightweight second-vector instance
• brain-layer — what consumes the connector outputs

Open debates

• Connectors vs native: connectors first; native capabilities may grow over time
• For real-time SDR calls: cannot make API calls to Salesforce mid-conversation — need local data copy (“data will gradually migrate to Harmony”)