AutomationTasks

Update Record

Update a CRM/GTM record with values from prior steps.

Task type: Update Record

Use Update Record to write values back to GTM Engine records. It is the main task for making workflow results durable in CRM-facing fields.

Run behavior

  • Side effects: This task can change data or call an external system. Test with safe records and be careful when rerunning.
  • Credit usage: This task is not classified as credit-billed by the workflow task registry.

When to use this task

  • Write an AI-generated summary to an account, contact, or opportunity field.
  • Tag records after import, enrichment, or scoring.
  • Update workflow status fields after an integration step completes.

Setup tips

  • Map only fields that should change.
  • Prefer typed field mappings over raw JSON when possible.
  • Test on one record before running the workflow over a batch.

Examples

Write account angle

Map {{ steps.3.text }} into an AI-fillable account angle field after a Research and AI Prompt sequence.

Outputs

  • Updated record metadata and task status.

Common pitfalls

  • Updating too many fields in one task.
  • Writing generated text into the wrong record type.
  • Rerunning a workflow without checking whether the prior update already happened.

Reference details

These details are generated from the workflow task registry and match the fields available in the builder.

Required fields

  • recordType
  • recordId
  • fieldValues

Variable-aware fields

Fields that accept variable references ({{ inputs.x }}, {{ steps.N.y }}) from the workflow's variable graph:

  • recordId
  • fieldValues
  • rawJsonInput
  • account_id
  • account_ids
  • opportunity_ids

Liquid template fields

Fields that are rendered through Liquid (variables plus filters and control flow):

  • recordId
  • fieldValues
  • rawJsonInput
  • account_id
  • account_ids
  • opportunity_ids

Builder guidance

When the Workflow Builder Genie configures this task, it follows this guidance:

Only map fields that are explicitly needed. Prefer typed fieldValues and verify every value references an existing input or prior step.

Default configuration

New instances of this task start with the following configuration:

{
  "name": "Update Record",
  "outputKey": "update_record",
  "taskType": "Update Record",
  "description": "",
  "recordType": "accounts",
  "recordId": "",
  "fieldValues": {}
}

On this page