Salesforce
Receive opportunity, account and case changes from Salesforce as typed events in Tessel. Use them to start workflows, look up related records and write updates back within the fields you allow.
CRM
Category
Events
Sync mode
p95 520 ms
Latency
7 min
Setup time
What it can do
- Opportunity createdEvent
- Opportunity stage changedEvent
- Account updatedEvent
- Case createdEvent
- Run a SOQL queryQuery
- Create a recordWrite
- Update a recordWrite
- Upsert by external IDWrite
- Add a taskWrite
- Convert a leadWrite
Overview
The Salesforce connector subscribes to Change Data Capture through the Pub/Sub API, so workflows react to record changes without polling. Each change event carries the changed fields, the record ID and the user who made the change, and it lands in the trace of the run it started.
Teams use it to start onboarding when an opportunity moves to Closed Won, to create a Stripe customer for a new account and to alert a Slack channel when a high-priority case sits unassigned.
Supported objects
Opportunity, Account, Contact, Lead, Case and Task
Custom objects with Change Data Capture enabled, ending in
__cEnterprise, Unlimited, Performance and Developer editions
How change events work
Tessel subscribes to one channel per object, such as /data/OpportunityChangeEvent, and decodes each Avro payload against the object's schema. Events keep their replay ID, so if Tessel pauses it resumes from the last one it processed. Salesforce keeps change events for three days.
API limits
Writes go through the REST API and count against your org's daily API request allocation. Tessel groups upserts with the Composite API, up to 200 records per call, and shows remaining requests on the connection page.
Permissions needed
Use a dedicated integration user and an OAuth connected app. The user needs API Enabled and read access to the objects you subscribe to. Field-level security decides which fields Tessel can see and edit, so writes stay inside the fields you grant.
apiandrefresh_tokenOAuth scopesView All Data, orView Allon each subscribed object, for change eventsEditonly on objects you write back to
Five steps. About seven minutes.
Most of the time goes into the connected app and permission set. Tessel lists any missing permission before you finish.
- Create a connected app with the api and refresh_token scopesSalesforce2 min
- Assign the integration user a permission setSalesforce2 min
- Enable Change Data Capture for the objects you needSalesforce1 min
- Sign in with OAuth and pick objects and fieldsTessel2 min
- Edit a test opportunity and watch the event arriveVerify520 ms
Your pipeline, in a workflow today.
Connect Salesforce on the free plan. Up to three builders and 10,000 runs a month, no card required.