Salesforce Integration
Push Workestra bookings to Salesforce as Event records, route routing-form submissions by SFDC owner, and attach AI Notetaker recaps as Notes.
Connect Salesforce so Workestra can push every confirmed booking as an Event on the matched Lead, Contact, Account, or Opportunity, route routing-form submissions to the SFDC record owner's booking link, and attach Notetaker-generated recaps to SFDC contacts as Notes.
For the deeper context on the integration model — workspace-vs-personal CRM, owner mapping rules, owner-based routing — see CRM Integrations.
Screenshot needed — /settings/integrations/salesforce with the connect button + scope picker
What gets pushed
| Workestra event | Salesforce result |
|---|---|
| Booking confirmed | New Event record on the matched contact / lead |
| Booking rescheduled | Event updated with the new time |
| Booking cancelled | Event deleted (or marked closed — configurable per workspace) |
| Recap pushed (from Notetaker) | Note attached to the related contact + deal with summary + action items |
Connecting
- Go to
/settings/integrations/salesforce→ Connect. - Pick Production or Sandbox.
- Sign in to Salesforce. Grant the requested scopes (
api,refresh_token,offline_access). - Configure the user mapping — by default each Workestra user is mapped to the SFDC user with the same email; override on
/settings/integrations/salesforce→ User mapping for mismatched cases. - Pick the object scope: Events only, or Events + Notes (for recap push).
- Save.
The integration uses an OAuth refresh-token grant. Tokens are refreshed automatically; if a token gets revoked from the SFDC side, the integration's status flips to "needs reconnect" and surfaces in the calendar disconnect banner.
Configuring per booking link
On any booking link's Integrations tab, toggle Push to Salesforce. The default behavior pushes every confirmed booking. Disable it per-link for internal-only meetings you don't want cluttering SFDC.
Owner-based routing
Routing forms can route to the SFDC record owner's booking link automatically. See Routing Forms and the Salesforce lookup route action.
Required Salesforce permissions
The connecting user needs:
- API enabled in their SFDC profile (most paid editions; Essentials does not include API access)
- Edit on
Eventfor push, Create + Edit onNotefor recap push - Read on
Lead,Contact,Account,Opportunityfor lookup
OAuth client setup
The substrate ships with this release. Your workspace needs SALESFORCE_CLIENT_ID and SALESFORCE_CLIENT_SECRET environment values for the connect flow to work — the values come from a SFDC Connected App you set up in your org's Setup → App Manager. Workestra ships staging-only defaults; production workspaces need their own app.
If you see "integration not configured" when you click Connect, the env vars haven't been set for your workspace. Ask support or your workspace admin.
What's NOT yet supported
- AppExchange managed package — not published yet. The integration is OAuth-only.
- Custom field mapping beyond standard Event fields (Subject, Description, StartDateTime, DurationInMinutes, OwnerId, WhoId, WhatId).
- Lead Owner sync — when a SFDC Lead is reassigned, the resulting Workestra booking owner doesn't update.
- Sandbox + production simultaneously — connect to one or the other per workspace; for both, use separate workspaces.
Read next
- CRM Integrations — full integration model
- Routing Forms — owner-based routing on SFDC lookup
- HubSpot Integration — the equivalent for HubSpot teams
- AI Notetaker & Recaps — push recaps to SFDC contacts
Browser Extensions
Click-to-book Workestra meetings from anywhere on the web — Chrome, Firefox, Edge, Safari, with deep hooks for LinkedIn Sales Nav, Gmail, and Google Calendar.
HubSpot Integration
Push Workestra bookings to HubSpot as Meeting engagements with full contact + deal association, plus owner-based routing form lookup.