Skip to main content

​
Overview

The GET Profile node fetches a user’s Courier profile and attaches it to the automation run context. After this node runs, profile data is available via refs.profile in subsequent steps. Set the user ID to a dynamic value from the data object, such as refs.data.user_id.
GET Profile Node

​
Ad Hoc Usage

Use the get-profile step in an ad hoc automation to load a user’s profile before sending: 
{
  "automation": {
    "steps": [
      {
        "action": "get-profile",
        "user_id": "user_123",
        "merge_strategy": "none"
      },
      {
        "action": "send",
        "template": "order-update",
        "recipient": "user_123"
      }
    ]
  }
}

​
Merge Strategy

After the get-profile step, the user’s stored profile fields (email, phone, custom attributes) are available in the automation context. The merge_strategy field controls how fetched data combines with existing context data (defaults to soft-merge):
StrategyBehavior
soft-mergeMerge fetched fields into existing context; existing fields are preserved (default)
replaceReplace the entire context path with fetched data
overwriteOverwrite all properties from fetched data
noneDo not modify context if the path already has data
See Fetch Data for more on merge strategies.