Update Record

salesmate.update_record
ActionCRM & salesconnection required

Calls the Salesmate API with the connection's credentials.

Update one contact, company, deal or activity.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
Salesmate
Secret shape
the Salesmate access key, or {"access_token": "…"}
Config it needs
linkname
Resolved by
config.connection_id, else node.connection_id

Configuration

3 fields, 3 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
module
Which Salesmate record this node acts on.
stringYes—one of "contact", "company", "deal", "activity"—
record_id
Numeric id of the Salesmate record to act on, as returned by a create or search.
stringYes——1540
fields
The fields to write, as Salesmate names them. Salesmate revalidates the module's required fields on every update, so send those too.
objectYes—≥ 1 characters{"designation":"Head of Ops","lastName":"Doe","owner":1}

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "fields": {
    "designation": "Head of Ops",
    "lastName": "Doe",
    "owner": 1
  },
  "record_id": "1540"
}

Output

One shape.

result

FieldTypeExample
module
The module the record belongs to (contact, company, deal…).
string—
id
The record's numeric Salesmate id.
number—
record
The record as Salesmate returned it, including related objects.
object—
{
  "id": 0,
  "module": "",
  "record": {}
}

Notes

  • 'owner' is a required field on every create and update, and it is the numeric user id — salesmate.list_active_users returns it.
  • An update is a full write, not a patch: a required field left out of 'fields' is a 400 ValidationError, not an unchanged value.

See Update Record run in a workflow.

In a technical demo we add the Salesmate connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.