Skip to main content
All integrations
V
+
S
Shipped
CRM

Velora Marketing + Salesforce

Bidirectional sync with Sales Cloud — paste-token today, Connected App OAuth on the roadmap.

For larger broker agencies on Salesforce, Velora supports bidirectional sync into Sales Cloud (Lightning) including custom objects. We read Accounts / Contacts / Opportunities via REST API, write Tasks for every channel send + reply, and write Events for meeting bookings.

Two connection paths: (1) paste a Salesforce session/access token into /admin/settings → Integrations → Salesforce (Production or Sandbox toggle); (2) OAuth via Velora's Connected App — `/api/auth/salesforce/start?env=production|sandbox` + `/callback` are scaffolded and ready to enable once the Connected App passes Salesforce's review. The OAuth path captures the org-specific `instance_url` automatically so subsequent API calls land on the right host.

Salesforce-specific defenses are built in regardless of auth method: SOQL injection-safe parameterization, per-field whitelist on writes, and LIMIT clamping on reads to avoid pulling unbounded result sets through the API governor.

Data flow

What moves between Velora and Salesforce.

Velora sends to Salesforce
  • Tasks for every channel send + reply
  • Reply intent class as a custom field on Task
  • Meeting bookings as Events
Velora receives from Salesforce
  • Accounts + Contacts + Opportunities
  • Custom field mappings for lives, renewal date, carrier
  • Owner (User) + Territory + Pipeline
Setup

How to connect.

From /admin/settings → Integrations → Salesforce, paste a session/access token (Production or Sandbox toggle in the connect flow). Connected App OAuth lands once the app passes Salesforce review.