Provider-specific connections
Connect CRM, website, advertising, email and social sources to the workspace. The tables below explain the business information and workflows each connection supports.
Integrations, workspaces & governance
Connect the supported sources. Keep their scope clear.
Bring authorized CRM, marketing and mapped operational records into the selected workspace, with source health, access and configuration available for review.
ContextConfirm the workspace membership and source permissions.
ReviewConfigure the supported scope and validate available records.
Follow-throughReview freshness, failures, access and budget before relying on the result.
A connection starts with the specific records you need.
Verify the provider, permissions, source scope and synchronization before relying on a view. Operational mappings also need validated entities, fields, periods and units. A catalog entry or logo does not establish complete integration.
Feature functionality
Inside Integrations, workspaces & governance.
Operational mappings
Discover and read supported Dynamics or NetSuite entities, validate their mappings and synchronize the scoped operational records. Read access does not imply transaction write-back.
Workspace membership and switching
Choose an authorized workspace and confirm its active identity before opening client work. A successful switch returns to Command Center. Sources, budgets and membership belong to the relevant workspace.
Access, budgets and audit
Authorized administrators can manage the permitted membership, source-health, AI-usage, budget, plan/access and audit views. Menu visibility alone is not authorization.
Brand and layout
Use the available brand and layout settings for the workspace. Brand controls do not establish white-label resale terms or a particular deployment commitment.
Signed events and form intake
Receive supported signed raw events or website forms through their configured intake paths. Downstream mapping and matching are separate; accepting a payload is not a full native connector.
Administrators manage workspace membership, authorized sources, mappings, AI usage and budgets. Keep each business or client’s data, permissions and audit history within its intended workspace.
Connection scope
Review the reader or delivery path you need.
Choose connections around the business questions you need to answer. Authorize the relevant accounts, map the required records and confirm the reporting or delivery permissions.
| Source or path | Business workflow | What to check |
|---|---|---|
| Salesforce | CRM records, ownership, activity and data-quality findings. | Authorize the relevant CRM account and confirm synchronized record coverage. |
| GoHighLevel / LeadConnector | CRM records, data-quality checks, and supported conversation and appointment analytics. | Confirm the selected location, permissions and synchronized history. Analytics does not provide an in-app phone system. |
| Dynamics 365 / Dataverse | Mapped CRM and operational reads, with entity and field discovery. | Validate the account, entities and field mappings used in the workspace’s CRM and operational views. |
| Dynamics ERP | Read-only, mapped operational records within a selected company. | Validate entities, fields, units and reporting periods. No ERP transaction write-back. |
| NetSuite | Read-only operational records through configured mappings. | Confirm permitted records and valid mappings. No ERP transaction write-back. |
| Google Analytics 4 & Search Console | Website activity and search observations for authorized properties. | Select the correct properties and period. Independent form feeds are not automatically GA4 session conversions. |
| Google Ads, Meta Ads & LinkedIn Ads | Supported paid-media campaign and performance measures. | Authorize the ad account. Spend and engagement do not establish matched pipeline or revenue. |
| Meta Lead Ads forms | Supported Facebook Page form and lead reads. | Authorize the Page and lead permissions. Verify the subsequent CRM matching separately. |
| Organic social analytics | Provider-specific measures from LinkedIn, Instagram, Facebook, TikTok, X and YouTube. | Confirm each account’s available metrics and reporting scope. Analytics access does not grant publishing access. |
| Social publishing | Facebook Pages, LinkedIn organizations and X: static image or text. Eligible Instagram accounts: static image. YouTube: ready short-video media. | Requires eligible destinations, publishing permissions, ready media and delivery workers. Scheduled is distinct from provider-confirmed publication. |
| HubSpot email | Supported email event reads. | Authorize the email account and select the relevant campaign history. CRM records use the corresponding CRM connection. |
| Gmail | Permitted message data for normalized email activity. | Confirm the user’s authorized mailbox scope. Reading activity does not automatically send messages. |
| Microsoft Outlook | Supported mail and calendar activity through Microsoft Graph. | Confirm granted mailbox and calendar scope; this is not access to every account in a tenant. |
| Outreach | Supported event activity reads. | Confirm the account, permissions and available event history. |
| Signed events / Zapier intake | Signed incoming raw-event payloads with duplicate protection. | Map and normalize accepted events for their downstream use. Intake is separate from a complete native application connector. |
| Website form intake | Signed form submissions and supported CRM matching. | Configure the form schema and verify identity matching. Unmatched submissions remain a coverage question. |
| Source or path | Business workflow | What to check |
|---|---|---|
| TikTok content handoff | Prepare content for TikTok’s manual publishing workflow. | Review the final media, caption and destination before publishing. |
| Mailchimp | Email campaign and engagement context. | Authorize the account and select the campaign history and measures needed for the review. |
| Constant Contact | Email campaign and engagement context. | Authorize the account and select the campaign history and measures needed for the review. |
| Google Calendar | Authorized calendar and appointment context. | Verify the appointment data available to the intended workflow before relying on a report. |
| Source or path | Business workflow | What to check |
|---|---|---|
| Stripe payment analytics | Payment and transaction context for commercial reporting. | Confirm the source transactions, reporting period, currency and relationship to CRM outcomes. |
| HubSpot CRM, Pipedrive & Zoho CRM | CRM leads, contacts, opportunities, ownership and activity. | Select the workspace’s primary CRM, authorize the account and validate record coverage. |
| Google Business Profile, call tracking & LinkedIn Lead Gen Forms | Local performance, call-source and lead-form context. | Review source definitions and identity matching before connecting activity to opportunities or revenue. |
Each connection supplies a defined part of the business picture. Keep sources, matching, freshness and permissions visible when turning a signal into a decision or reviewing an outcome.
How the work moves
Authorize · Map and sync · Monitor
Authorize
Confirm the workspace membership and source permissions.
Map and sync
Configure the supported scope and validate available records.
Monitor
Review freshness, failures, access and budget before relying on the result.
Discuss Integrations, workspaces & governance
Bring the question your team needs to answer.
Walk through the relevant sources, review steps and supported handoff for your integrations, workspaces & governance workflow.