Skip to main content
images/active_campaign.svg

​
Parameters

​
Action
Parameters
{
  "$result_object_key": {
    "customer_account_name": "Morf",
    "email": "john.doe@gmail.com",
    "field_values": {
      "Age Group": ">60",
      "Timezone": "America/Los_Angeles"
    },
    "first_name": "John",
    "id": "10",
    "ip": "1.2.3.4",
    "last_name": "Doe",
    "organization_name": "Morf",
    "phone": "+15551234123",
    "tags": [
      "tag1",
      "tag2"
    ],
    "updated_at": "2024-01-01T09:00:00Z"
  }
}

{
  "$result_object_key": {
    "customer_account_name": "Customer account name",
    "email": "Email address",
    "field_values": "Custom fields' values",
    "first_name": "First name",
    "id": "ID",
    "ip": "IP address",
    "last_name": "Last name",
    "organization_name": "Organization name (if plan allows)",
    "phone": "Phone number",
    "tags": "Tags",
    "updated_at": "When a webhook ran for the contact"
  }
}

​
Result Object Field Details

You can use the result of the action’s data as inputs to downstream workflow actions. Each fetch action requires a result object key to be specified which will nest the action’s result data inside the downstream data context in the Workflow. Here we demonstrate how to refer to this data using the prefix $result_object_key.
​
Contact
Fetch Action Response Object