Skip to main content

​
What It Does

  • Automatically inserts new records or updates existing ones in Salesforce based on your workflow data.
  • Ensures CRM data hygiene by preventing duplicates through upsert logic.
  • Keeps your pipeline and account records in sync with real-time inputs.
  • Saves manual entry time and reduces errors during high-volume updates.
  • Integrates seamlessly with other nodes, so you can chain enrichments or notifications after upserts.

​
🏁 Getting Started

Salesforce Upsert Record Node config screenshot
1

Select Salesforce Account

Choose your connected Salesforce account where records will be upserted.
2

Pick Your Object Type

Use the SObject Type dropdown to select which Salesforce object you want to create or update.
3

Map Your Fields

Use the Insert Input button or @ColumnName syntax to map data values from previous steps into Salesforce fields.

​
Inputs

​
🛠️ Required Fields

  • Salesforce Account (✅)
    Your connected Salesforce org.
    Why it matters: Ensures records go into the correct environment—production or sandbox—so you maintain data integrity.
  • SObject Type (✅)
    Choose the Salesforce object (e.g., Account, Opportunity, Lead) to upsert.
    Why it matters: Defines where new records land or which object’s records get updated, keeping your pipeline and CRM aligned.
  • Field Mappings (✅)
    Map workflow data to Salesforce fields (e.g., Name, Amount, CloseDate).
    Why it matters: Accurate field mapping drives clean data and powers reporting on up-to-date records.

​
Output

This node returns the full Salesforce record response, including the record ID, any created or null values, and other standard/object-specific fields.
Salesforce Upsert Record Node output screenshot
If there’s an external ID match, the existing record updates; otherwise, a new record is created.

​
How It Works

  1. Reads your chosen Salesforce Account and SObject Type.
  2. Sends an upsert request using field mappings or an external ID.
  3. Salesforce creates or updates the record under the hood.
  4. Emits the full record data for downstream nodes like alerts or reporting.

​
🚀 Example Use Cases & Prompts

Use CaseSetup or Prompt Example
New Lead Automation“Upsert a new Lead when a form submission comes through.”
Opportunity Update“Update Opportunity StageName when deal status changes.”
Account Data Hygiene“Ensure Accounts always have the correct region and owner.”
Bulk Field Sync“Map spreadsheet columns to custom fields and upsert in bulk.”

​
✨ Pro Tips

  • Use a unique external ID field (e.g., External_Id__c) to prevent duplicates.
  • Always preview your field mappings with a single test run to catch mapping typos.
  • Leverage the Insert Input button or @ColumnName syntax for dynamic data flow.

​
⚠️ Important Considerations

  • Upserting many records may hit Salesforce API limits—consider batching or rate limiting.
  • Ensure your account has “Modify All” or “API Enabled” permissions on the target object.
  • External ID fields must be indexed in Salesforce to optimize upsert performance.

​
🛠 Troubleshooting & Gotchas

SymptomLikely CauseQuick Fix
“INVALID_FIELD” errorTypo in field API nameVerify and correct field names in mappings.
Record not updatingMissing external ID or ID fieldMap the correct external ID to identify records.
API limit exceededBulk upserts without batchingSplit into smaller batches or throttle requests.

​
📝 FAQ

A new record is created—Salesforce upsert will insert if no match is found.
Yes—just select the custom SObject name (e.g., MyCustomObject__c) in the dropdown.
No—action nodes like upserts are free to run.

​
💰 Pricing

Action NodeCredit Cost
Upsert Record (action)Free
Action nodes (like this upsert) don’t consume credits—only trigger nodes do.

Ready to automate and clean up your Salesforce data? Drop in Upsert Record and watch your CRM stay in sync—all without lifting a finger. 🚀