Get Record

Task type: Get Record

Use Get Record to fetch GTM records so later steps can reference only the fields they need. It is often the first step in account, contact, or opportunity workflows.

Run behavior

• Side effects: This task is read-only or computation-only by default. It returns data for later steps rather than directly writing records or sending messages.
• Credit usage: This task is not classified as credit-billed by the workflow task registry.

When to use this task

• Load an account, contact, opportunity, or user by id.
• Fetch specific fields before research, AI prompting, or record updates.
• Normalize workflow input ids into a record object for downstream tasks.

Setup tips

• Select the smallest field set that supports downstream tasks.
• Use workflow inputs such as {{ inputs.account_id }} for record ids.
• Fetch one record unless a later step truly needs a list.

Examples

Fetch account before research

Use {{ inputs.account_id }} to fetch account name, domain, industry, and owner before a Research task.

Outputs

• A fetched record object or list of records, depending on fetch mode and record type.

Common pitfalls

• Fetching every field when only a few are needed.
• Passing a contact id into an account lookup.
• Forgetting to update downstream variable paths after changing selected fields.

Reference details

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

Required fields

• recordType
• recordId

Variable-aware fields

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

• recordId
• recordIds
• fieldValues
• account_id
• account_ids

Liquid template fields

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

• recordId
• recordIds
• fieldValues
• account_id
• account_ids

Builder guidance

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

Choose the smallest selectedFields set that supports downstream tasks. Use trigger/input record ids when available.

Default configuration

New instances of this task start with the following configuration:

{
  "name": "Get Record",
  "outputKey": "get_record",
  "taskType": "Get Record",
  "description": "",
  "recordType": "contacts",
  "recordId": "",
  "identifierType": "id",
  "fetchMode": "single",
  "selectedFields": [],
  "createIfNotFound": false,
  "enrichIfCreated": false
}