Create Record

Task type: Create Record

Use Create Record to create a new GTM Engine record from workflow data.

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

• Create a contact after finding a qualified prospect.
• Create a follow-up record from a trigger or external event.
• Turn structured AI output into a new GTM record after review.

Setup tips

• Provide required fields for the selected record type.
• Deduplicate before creating records when possible.
• Keep field values explicit and easy to inspect in run history.

Examples

Create a contact from a prospect

Create a contact using enriched first name, last name, email, account id, and campaign tag values.

Outputs

• The created record id and created record metadata.

Common pitfalls

• Creating duplicates because the workflow did not check for existing records.
• Leaving required fields blank.
• Creating records from AI-generated values without validation.

Reference details

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

Required fields

• recordType
• fieldValues

Variable-aware fields

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

• fieldValues
• account_id
• account_ids
• opportunity_ids

Liquid template fields

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

• fieldValues
• account_id
• account_ids
• opportunity_ids

Builder guidance

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

Create only required fields plus values the user explicitly requested. For activities, put contact_ids/opportunity_ids in fieldValues because the activity executor reads those built-in array fields from fieldValues; when the contact/account may not exist, use preceding Get Record tasks with createIfNotFound rather than embedding lookup logic in the activity create step.

Default configuration

New instances of this task start with the following configuration:

{
  "name": "Create Record",
  "outputKey": "create_record",
  "taskType": "Create Record",
  "description": "",
  "recordType": "contacts",
  "fieldValues": {}
}