ACTION_ID: salesforce_update_record
NAME: Salesforce: Update a Record
CATEGORY: sheets
CREDITS: 0

Update a record in Salesforce.

================================================================================
PREREQUISITE — USER ACTION REQUIRED
================================================================================

This action only works if the user has connected their Salesforce org
in Floqer. The connection cannot be made via the API or by an AI agent.

The user must do this themselves before this action will run:
  1. Sign in to Floqer at https://app.floqer.com
  2. Open the Connections page from the sidebar
  3. Click Salesforce and complete the OAuth flow

If the user has not connected Salesforce, this action will fail with a
connection / authentication error. Before configuring or running this
action, confirm with the user that the Salesforce connection exists.

INDEX:
  1. Inputs
  2. Outputs
  3. How to configure
  4. Key notes
  5. Where it fits in a workflow
  6. When to use
  7. When not to use

================================================================================
1. INPUTS
================================================================================

record_id (string, required)
  Record Id. Enter record ID to update.

salesforce_object (dropdown, required)
  Salesforce Object. Choose the SalesForce Object.

add_fields_and_their_values (jsonArray, required)
  Add Fields and their Values. Select Fields from the object and add
  Values.

ignore_empty_values (radio, optional)
  Ignore empty values. Default ON. If ON, empty Floqer fields won't
  replace existing values in Salesforce. If OFF, they will overwrite.

run_salesforce_assignment_rules (radio, optional)
  Run Salesforce assignment rules. Default ON.

================================================================================
2. OUTPUTS
================================================================================

record_id (string) — Record ID. Record ID of the record being
updated.
account_url (url) — Account URL. Salesforce Account URL. Placeholder:
  "https://test.my.salesforce.com".

================================================================================
3. HOW TO CONFIGURE
================================================================================

Resolve dynamic field values via Get Action Field Options before
configuring:

  POST /api/v1/workflows/{workflow_id}/sheets/{sheet_id}/actions/{action_instance_id}/options/salesforce_object
       (body: {})
  POST .../options/add_fields_and_their_values
       (body: { "context": { "salesforce_object": "Contact" } })

Configure Action body:

{
  "inputs": {
    "record_id": "{{salesforce_lookup_record_1.record_id}}",
    "salesforce_object": "Contact",
    "add_fields_and_their_values": [
      { "name": "Title",   "value": "{{input.title}}" },
      { "name": "Phone",   "value": "{{input.phone}}" }
    ],
    "ignore_empty_values": true,
    "run_salesforce_assignment_rules": true
  }
}

Field-by-field:
  - record_id                       Salesforce ID of the record to
                                    update — usually a `{{ref}}` to an
                                    upstream `salesforce_lookup_record`
                                    output.
  - salesforce_object               Object name from the
                                    `salesforce_object` options call.
  - add_fields_and_their_values     `[{name, value}]` — `name` is the
                                    Salesforce field's API name; `value`
                                    accepts `{{ref}}` tokens or literals.
  - ignore_empty_values             Default `true`. Empty Floqer fields
                                    don't overwrite existing values.
  - run_salesforce_assignment_rules Default `true`. Set `false` to skip
                                    Lead/Account/Case assignment rules.

================================================================================
4. KEY NOTES
================================================================================

- Updates by Salesforce record ID. Pair with `salesforce_lookup_record`
  upstream when the ID is not already known on the row.
- The Salesforce connection must live on the API key's user
  account. If the connection lives under a different team member,
  Get Action Field Options returns a 424.
- Token refresh is automatic on transient `INVALID_SESSION_ID`; one
  retry, then 502.
- For create-or-update by external ID (no prior lookup needed),
  prefer `salesforce_upsert_record`.

================================================================================
5. WHERE IT FITS IN A WORKFLOW
================================================================================

Pattern: salesforce_lookup_record -> workflow_if_else (found) ->
salesforce_update_record.

================================================================================
6. WHEN TO USE
================================================================================

Use salesforce_update_record to update an existing Salesforce record
by ID.

================================================================================
7. WHEN NOT TO USE
================================================================================

Need create-or-update on an external ID
  -> salesforce_upsert_record
     (https://floqer.com/docs/action-detail/salesforce_upsert_record.txt)

Need to create a new record
  -> salesforce_create_record
     (https://floqer.com/docs/action-detail/salesforce_create_record.txt)

Need to find a record (no ID yet)
  -> salesforce_lookup_record
     (https://floqer.com/docs/action-detail/salesforce_lookup_record.txt)

================================================================================

This file is maintained manually. Last updated: 2026-04-28.
Full interactive reference: https://floqer.com/docs/reference
Action catalog: https://floqer.com/docs/action-catalog.txt