Skip to main content
Looks up matching rows from a reference entity and formats the results as a text field. Useful for enriching records with context from another dataset — for example, attaching related notes, activities, or linked records as formatted text.

​
Configuration

SettingDescription
Key FieldField in the reference entity to match against
Source FieldLookup key from your workflow data
Display FieldsFields from the reference entity to include in the output
LimitMaximum matching rows to return per record (default: 5)
Result Field NameName for the output field (default: reference_result)
Format TemplateTemplate for formatting each matching row (e.g., {Name}: {Amount})
Case SensitiveKey matching case sensitivity (default: off)
Virtual Object NameNamespace prefix (default: reference_lookup)

​
Exclusion Options

SettingDescription
Exclude FieldField in reference entity for exclusion filtering
Exclude Source FieldSource field providing the exclusion value

​
How It Works

1

Select the reference entity

Choose which entity to look up matching rows from.
2

Define the match

Map the key field (in the reference entity) to the source field (in your workflow data).
3

Choose display fields

Select which fields from matching rows should appear in the output.
4

Format the output (optional)

Write a template using {FieldName} placeholders to control how matching rows are formatted.

​
Output

A text field containing formatted matching rows from the reference entity. This is especially useful as input for AI Enrichment prompts or reports.

​
Example

Enrich accounts with their recent support tickets:
  • Key Field: Zendesk.Ticket.AccountId
  • Source Field: Salesforce.Account.Id
  • Display Fields: Subject, Status, Created Date
  • Format Template: {Subject} ({Status}) - {Created Date}
  • Limit: 3
Result: each account gets a text field like: 
Login issue (Open) - 2024-01-15
Billing question (Closed) - 2024-01-10
Feature request (Pending) - 2024-01-08

​
Best Practices

  • Set a reasonable Limit — too many matching rows creates very long text fields
  • Use Format Template for clean, readable output
  • Use the Exclusion options to skip irrelevant matches (e.g., exclude the record itself)
  • Reference Lookup output works well as input to AI Enrichment prompts
  • Dictionary Lookup — maps values using key-value pairs rather than returning formatted text
  • AI Enrichment — feed Reference Lookup output into an LLM prompt for analysis
  • Bond Node — creates relationships between entities (structured join vs. text lookup)