CRM & Sales · 73 pre-built actions
Salesforce integration with Nexus
Put Salesforce inside the process, not at the edge of it. Commercial records start and finish work in other systems. Nexus lets Salesforce act as both a trigger and a participant in one governed run, with the same approvals and audit as every other step.
Pre-built actions
What you can automate
73 pre-built Salesforce actions, grouped by what they work on.
73
PRE-BUILT ACTIONS
- 01AddContactToCampaign is available as a pre-built Salesforce action.
- 02Salesforce is one of the 46 trigger sources: Nexus can poll new or updated records using SOQL and start a workflow from the result.
Workflow
How it fits into a Nexus workflow
The Salesforce trigger polls for new or updated records using a SOQL query you define. Each detected record starts a workflow run with the record data as input, so the run can validate, enrich and hand off without a separate integration server.
A trigger source starts work. A connector action performs work. Both run inside the same governed execution.
Beyond pre-built actions
When the pre-built action is not enough
Move down one step: an API, protocol or database call, then custom logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript with any library. Every step uses the same secrets, approvals, history and audit.
01
Call the Salesforce API directly with the HTTP Request node when a required operation is outside the pre-built action groups.
02
Use Rules + Code to shape payloads, apply ownership rules or reconcile responses in the language your team prefers.
03
Keep credentials in vault-backed secret handling so direct calls use the same authority model as prebuilt actions.
Examples
Workflow examples
Record change to ERP handoff
A SOQL poll detects an updated record, Rules + Code validates it, and the run hands off to SAP through the SAP connector or an RFC call.
Campaign membership from a governed source
A qualified contact from another system is added to a campaign with AddContactToCampaign after deduplication and consent rules have run.
Escalation into service and engineering
A record change opens work in ServiceNow or Jira and the handoff state is written back through a direct API call where required.
Payment events reflected on the account
A Stripe or PayPal subscription event is validated and reflected in Salesforce, with finance approval where policy requires.
Deployment, trust and audit
Governance, audit and deployment
Deployment
Nexus runs on-premises, in private or sovereign cloud, or air-gapped. The step needs network reach to the system it calls, and nothing else changes.
Secrets and identity
Credentials are referenced through vault-backed secret handling and role-based access, never embedded in workflow logic.
Audit
Inputs, outputs, approvals and outcomes are written to the execution history for every run.
Multi-system workflows
Use cases that include Salesforce
Salesforce, SAP
Salesforce to SAP order handoff without replacing either system
A Salesforce record detected by SOQL polling is validated, handed to SAP through the connector or an RFC call, and reconciled back.
HubSpot, Salesforce
Lead handoff from HubSpot to Salesforce with governed enrichment
A lead moves from marketing to sales with deduplication, enrichment and routing rules applied in one recorded run.
Salesforce, ServiceNow, Jira
Customer issue escalation across Salesforce, ServiceNow and Jira
One governed run carries an escalation from the customer record to service operations and engineering, and keeps the handoff state visible.
Stripe, PayPal Subscriptions, Salesforce, SAP
Payment and subscription events into CRM and ERP
A Stripe event or PayPal subscription change is validated and reflected in Salesforce and SAP under one execution record.
Integration patterns
Salesforce integration patterns
Dedicated patterns that pair Salesforce with another system in one governed run.
Industry use cases
Processes that use Salesforce
Financial services
Lead to account and ERP handoff
Marketing leads become clean sales accounts, and approved deals reach ERP without re-keying.
Enterprise
Order to cash across CRM, ERP and billing
Won deals become orders and invoices without re-keying, with exceptions reviewed.
Enterprise
Customer support escalation
Support issues reach engineering with context, and customers and account teams stay informed.
Enterprise
Marketing to sales handoff
Qualified leads reach the right salesperson fast, with duplicates caught.
Enterprise
High-priority customer escalation
Cases that meet your escalation criteria become owned incidents with approvals and updates.
Enterprise
Marketing to sales handoff with support context
Sales receives leads with open support issues visible, so outreach starts informed.
Enterprise
CRM and ERP operational analytics
Pipeline and ERP data are modelled together in Snowflake for operational reporting.
FAQ
Salesforce connector questions
- Can Salesforce start a Nexus workflow?
- Yes. The Salesforce trigger source polls new or updated records via SOQL and starts a run for each detected record.
- Which Salesforce actions are prebuilt?
- Nexus includes 73 Salesforce actions across Contacts, Leads, Cases, Accounts, Opportunities, Reports and CPQ. AddContactToCampaign is a named example.
- What if the operation I need is not prebuilt?
- Use the HTTP Request node against the Salesforce API, with Rules + Code for payload logic. It runs in the same workflow, with the same secrets, approvals and audit.
- Does Nexus replace Salesforce data ownership?
- No. Salesforce remains the system of record for its objects. Nexus orchestrates reads, writes and handoffs under your policy.
Related reading
Continue from here
- SAP connector
The ERP side of the most common Salesforce handoff.
- Salesforce-SAP integration
The commercial-to-operational pattern in detail.
- HubSpot connector
Marketing-side lead capture ahead of Salesforce.
- Integration patterns
How systems work together in a complete process.
Integration review
Discuss how Salesforce fits your process.
Bring the operation you need. We will map it to a pre-built action, or to the API, protocol or code step that covers it.