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 data loads and live change subscriptions, without stepping outside the governance and audit trail that covers every other Neblex workload.

• Works against both production and sandbox orgs, switched per connection
• Tracks Salesforce API versions on a rolling basis as they are released
• Schema is discovered dynamically, so custom objects and fields appear automatically with no manual mapping file
• One connector powers deterministic workflows, agent tool calls, and change-data-capture sync jobs

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

• Get clean records into the CRM.
• Keep Salesforce and the back office in sync.
• Give an agent safe CRM access.

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

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

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

1. 1Trigger: inbound webhook receives email, company, utm_campaign.
2. 2Enrich: lookup on company domain adds employee_count, industry, country.
3. 3Score: a rules step maps firmographics to a 0 to 100 fit score and a grade of A to D.
4. 4Route: a data table maps country plus employee_count band to a Salesforce OwnerId.
5. 5Write: Upsert record on Lead, keyed on external ID Web_Form_ID__c, mapping email → Email, company → Company, fit_score → Fit_Score__c, grade → Rating, utm_campaign → Campaign_Source__c, OwnerId → OwnerId.
6. 6Notify: if 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 automatically, 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 stream into Snowflake on the next poll using change data capture. (Data)
• Sales research agent. Given a new lead, 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. Custom objects and fields are picked up automatically through schema discovery, with no separate connector update.

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 are discovered automatically at connection time and behave identically to standard objects across every operation above.

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. Web Server (Authorization Code) flow for interactive setup, JWT Bearer flow for unattended server-to-server connections.
• 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 allowlisting supported. Compatible with Salesforce IP restriction rules and trusted IP ranges on the connected app.
• Full audit trail. Every read, write, and subscription event flows into the same Neblex audit trail as every other connector and workload.

The shape of the vendor's limits, as published at the time of writing. Verify the exact figures for your plan; they change without notice. Neblex honors the vendor's own rate-limit and retry signals and backs off within them.

• Rolling 24-hour API call allocation per org, which varies by edition and license count
• Batch actions cap at 200 records per batch, 2,000 per job, with larger volumes routed to bulk file load
• Query and Search return up to 2,000 records per call before pagination
• File downloads are capped at 25 MB per file
• Exponential backoff and retry are applied automatically on rate-limit and transient errors