Integrations
Connect the tools your revenue process already depends on.
SholaX is designed to sit between acquisition, CRM, communication, appointments and revenue reporting while keeping workspace permissions, connection status and data provenance visible.
Connection Architecture
Product direction and current workflow model
SholaX
Acquisition connections
Bring campaign evidence into the customer journey.
Marketing integrations are most valuable when campaign identifiers and source evidence can survive beyond the initial conversion.
Meta advertising
Support campaign/source context, lead workflows and future closed-loop reporting through the Revenue Graph.
Google advertising
Carry search campaign context and click identifiers toward CRM outcomes and revenue reporting.
Communication & appointments
Keep customer activity visible around the CRM record.
Calendar and email connections should strengthen the customer timeline without turning external credentials into browser-visible workspace data.
CALENDAR
Calendly
The public strategy-call flow already uses Calendly. Future client workflows can connect appointment evidence to CRM timelines where appropriate.
CALENDAR
Google / Microsoft Calendar
Planned workspace connections can support appointments and reminder context once the production OAuth workflows are implemented.
Gmail
Planned email sync can make relevant sales communication visible inside the CRM without claiming the integration is live today.
Outlook
Planned Microsoft mail integration follows the same workspace-isolated design principle.
Tracking identifiers
The small identifiers behind useful attribution.
The customer should never need to think like a tracking engineer, but SholaX still needs to preserve the evidence required for defensible reporting.
Campaign
Meta / Google
Click
GCLID / FBCLID
Landing page
UTM context
Lead
Source attached
CRM
Opportunity timeline
Revenue
Attribution evidence
Connection centre
Show what is actually connected, what needs action and what is still planned.
The product should be explicit about integration status. A coming-soon integration should never be presented as if it is already syncing data.
Integrations
Example workspace status
Meta Ads
Manual access workflow
Google Ads
Manual access workflow
Calendly
Public booking embed
Gmail
OAuth sync
Google Calendar
OAuth sync
Outlook / Microsoft Calendar
OAuth sync
Security model
Connections stay inside the workspace boundary.
Integrations need the same tenant isolation and audit discipline as CRM and Revenue Graph data.
01
Workspace isolation
Connected records are scoped to the correct workspace rather than shared across customers.
02
Server-side credentials
OAuth tokens and provider secrets should remain server-side rather than living in general workspace tables.
03
Revocable access
Connections should expose status and support revocation/reconnection when authorisation changes.
04
Audit visibility
Important connection and sync changes should leave an operational record for administrators.
Integration roadmap
Separate available workflows from the deeper automation layer still being built.
This keeps the public site accurate while showing where the connected Revenue OS is heading.
Available now
Revenue Graph ready
Next integration layer
SholaX
Connect the customer journey without hiding what is and is not live.
Review the systems you already use and map which connections should feed CRM, attribution and revenue reporting first.