Skip to main content

​
What It Does

  • Automates updates to Salesforce records without manual clicks.
  • Keeps deal stages, campaign statuses, and account details in sync.
  • Cuts down on data entry errors and stale information.
  • Empowers your RevOps team to maintain clean, reliable CRM data.

​
🏁 Getting Started

Salesforce Node config screenshot
1

Select Account

Choose your connected Salesforce account where your org data lives.
2

Configure Inputs

Pick the object type, record ID, and which fields you want to update.

​
Inputs

​
🛠️ Required Fields

  • Select Account (✅)
    Choose the Salesforce connection containing the records you want to update.
    Why it matters: Ensures you’re writing to the right org.
  • SObject Type (✅)
    The type of Salesforce object (e.g., Account, Opportunity) to update.
    Why it matters: Directs the node to the correct object schema.
  • Record ID (✅)
    The unique ID of the record you want to modify.
    Why it matters: Targets exactly the record that needs updating, preventing mismatches.
  • Fields to Update (✅)
    Select one or more fields on the record to change.
    Why it matters: Lets you push specific data updates—stage changes, status flags, numeric values—into Salesforce.

​
🎯 Optional Fields

This node has no optional fields.

​
Output

When the action runs, it emits the updated record details, including all requested fields. Use these outputs to:
  • Feed downstream nodes for notifications or reporting.
  • Trigger conditional logic based on field values.
Salesforce Node output screenshot
The node returns the complete record snapshot after updates, so you always have the latest values downstream.

​
How It Works

  1. Connects to Salesforce using your selected account.
  2. Looks up the record by its ID on the chosen SObject.
  3. Applies all field changes in a single API call.
  4. Emits the updated record for your next steps—alerts, reports, or further automations.

​
🚀 Example Use Cases & Prompts

Use CaseSetup or Prompt Example
Pipeline Stage Sync”When an opportunity stage changes, update the Stage field in Salesforce.”
Bulk Priority Flagging”Mark high-value accounts with a priority flag based on deal size.”
Campaign Response Update”Set Lead.Status to ‘Contacted’ when a campaign sheet triggers this node.”

​
✨ Pro Tips

  • Double-check your recordId mapping to avoid overwriting the wrong record.
  • Use the Insert Input button to dynamically map fields from earlier nodes.
  • Test in a sandbox org first for high-stakes updates.

​
⚠️ Important Considerations

  • Field API names must match exactly what’s in Salesforce, including case sensitivity.
  • Ensure your user has edit permissions on the object and fields you’re updating.
  • Large batches of updates can hit Salesforce API limits—use throttling if needed.

​
🛠 Troubleshooting & Gotchas

SymptomLikely CauseQuick Fix
Update failuresInsufficient permissionsGrant edit rights or update user profile
API limit errorsToo many calls in short windowAdd delays or reduce batch size
Record not foundIncorrect recordId or objectVerify IDs and select the correct SObject

​
📝 FAQ

Use the Fields to Update input to select as many fields as necessary; the node applies them all in one request.
Yes — action nodes are free and don’t consume credits.

​
💰 Pricing

ActionCredit Cost
Update Record (action node)0 credits

Drop this Salesforce node into your flow to automate record updates and keep your pipeline in sync — automatically. 🚀