What it does in ClientPulse: Reads your Salesforce pipeline to flag stalled stages, slowing deal velocity, declining contact engagement, aging pipeline, and opportunity age — so a cooling client relationship surfaces as a churn signal. The enterprise-facing CRM path, parity with HubSpot and Pipedrive.
Status: Coming soon. The catalog card and signal definitions exist, but there is no automated connection yet. Tell us this is a deal-breaker (support@helloaurora.ai) and we'll prioritise it.
Tier: Likely Agency / Pro+ when shipped.
Per-agency: One Salesforce org per ClientPulse workspace.
Before you start (prerequisites)
- Account requirement: A Salesforce org (Professional edition or above for full API access; API access is an add-on on some lower editions).
- You'll need a System Administrator (or a profile with API Enabled + the right object permissions) to authorise the connection.
- Cost: Salesforce pricing varies widely by edition — see https://www.salesforce.com/editions-pricing. Free on ClientPulse's side.
Step-by-step setup
Setup steps will appear here once Salesforce ships. The flow will mirror the other OAuth integrations:
1. In ClientPulse, click Connect Salesforce on
/dashboard/integrations/sources.2. You'll be sent to Salesforce's OAuth login. Sign in with an admin account and pick the org.
3. Review and accept the requested read scopes (opportunities, accounts, contacts, activities).
4. Salesforce redirects you back to the Sources page with the connection live.
What you'll be able to do with it once connected
- See "pipeline stage stalled" and "opportunity aging" signals per client.
- Catch declining engagement on key accounts before renewal.
- Fold enterprise-CRM health into the overall churn score.
Common pitfalls (anticipated)
- Pitfall: "API Enabled" permission missing on the connecting user's profile. Fix: Salesforce gates API access by profile permission and edition. Have an admin enable API access for the connecting user, or connect as an admin.
- Pitfall: Sandbox vs production org confusion. Fix: Connect the production org that holds your live client pipeline unless you're explicitly testing.
Restrictions (anticipated)
- Read-only. ClientPulse will not create or edit opportunities, accounts, or contacts.
- One Salesforce org per ClientPulse workspace.
Status — what's blocking this
Salesforce is on the roadmap behind HubSpot and Pipedrive. If it's a must-have for your agency, email support@helloaurora.ai — every request moves it up the queue.
Need help?
Email support@helloaurora.ai — and let us know Salesforce matters to you.