Salesforce connector

The Salesforce connector gives any Neblex workflow or agent read and write access to a Salesforce org, from simple record lookups to bulk loads, and a Live stream trigger can subscribe to Salesforce Change Data Capture and Platform Events.

• Works against both production and sandbox orgs, one connection each
• Uses Salesforce API version 67.0
• Custom objects and fields work through the generic sObject and describe operations, with no separate connector update
• One connector powers deterministic workflows, agent tool calls, and sync jobs, all in the same run history

The three jobs this connector is picked for most often, and what each one gets you.

• Get clean records into the CRM. Leads and contacts from forms, events, and other systems are checked, enriched, and upserted by an external ID, so a resubmission updates the record instead of duplicating it.
• Keep Salesforce and the back office in sync. Won opportunities become orders and invoices in the ERP, and status and invoice numbers come back to the opportunity.
• Give an agent safe CRM access. An AI agent reads accounts and opportunities to answer questions, and any write it proposes can wait for a person to approve it.

A real flow teams build on day one, with the actual step-level detail.

Web form to scored, owned Salesforce Lead in under a minute

A marketing site form posts to a Neblex Webhook trigger. Neblex enriches the record, scores it, assigns an owner by territory, and writes it to Salesforce, with every step in the run history.

1. 1
   Trigger: a Webhook trigger receives email, company, utm_campaign.
2. 2
   Enrich: a lookup on the company domain adds employee_count, industry, country.
3. 3
   Score: a rules step maps firmographics to a 0 to 100 fit score and a grade of A to D.
4. 4
   Route: a data table maps country plus employee_count band to a Salesforce OwnerId.
5. 5
   Write: Upsert by external ID on Lead, keyed on Web_Form_ID__c, mapping email → Email, company → Company, fit_score → Fit_Score__c, grade → Rating, utm_campaign → Campaign_Source__c, OwnerId → OwnerId.
6. 6
   Notify: if the grade is A, post the Lead link to the owner in Slack. Otherwise no notification.

Common patterns other teams start from with this connector.

• Quote-to-cash sync. Closed-won opportunities flow from CRM to CPQ to billing, with no rekeying between systems. (Sales and RevOps)
• Order-to-cash. Orders sync from Salesforce to NetSuite for fulfillment, invoicing, and revenue recognition, with status flowing back to the CRM. (Finance)
• CRM to warehouse replication. Account, Opportunity, and custom object changes reach Snowflake through a Change Data Capture stream, or through polled triggers on a schedule. (Data)
• Sales research agent. Given a new lead, an agent researches the company and contact, scores fit against your ICP, and drafts a personalized outreach sequence for rep review. (Agentic)

All standard objects are supported, through typed operations for the common ones and the generic sObject operations for the rest.

Commonly used standard objects

Account, Contact, Lead, Opportunity, Case, Campaign, Task, Event, User, Product2, Pricebook2, Quote, Contract, Order

Custom objects (any __c object) and custom fields work through the generic sObject and describe operations, the same way as standard objects.

The connector inherits Salesforce's own permission model rather than working around it, so field-level and object-level security is respected end to end.

• OAuth 2.0. The connection holds your connected app's client ID and secret and a refresh token, stored encrypted, plus your org's host prefix.
• Field-level security enforced. Reads and writes respect the connected user's field-level security and object permissions. The connector cannot touch what that user could not in the Salesforce UI.
• IP restrictions. Salesforce IP restriction rules and trusted IP ranges on the connected app apply to the connection.
• Run history. Every run shows each step's status and errors; record data from successful runs is kept when the flow is set to keep run data for replay.

The shape of Salesforce's limits, as published at the time of writing. Verify the exact figures for your edition; they change without notice.

• Rolling 24-hour API call allocation per org, which varies by edition and license count
• Collection operations cap at 200 records per call; use the Bulk operations for larger volumes
• Query and Search return up to 2,000 records per call before pagination
• File downloads are capped at 25 MB per file
• The connector does not retry on its own; turn on Retry on failure for steps that should try again on rate-limit or transient errors