Documentation Index

Fetch the complete documentation index at: https://docs.relaynetwork.com/llms.txt

Use this file to discover all available pages before exploring further.

Version 2.28

  • Published on Jun 24, 2026
  • 1 minute(s) read
Prev Next

Release Date → December 1, 2025

Version →2.28

💫 WHAT’S NEW

RelayEvents__c Object

The following fields have been added to the RelayEvents__c object.

Field

Description

RootTriggerID__c

The system-generated unique identifier for the top-level APITrigger component that initiated an experience. This ID represents the originating source event responsible for generating the message card. All subsequent triggers or child components within the experience can be traced back to this root trigger.

RootClientTriggerID__c

An optional, client-assigned identifier (friendly name) for the top-level APITrigger component that initiated an experience. It corresponds to the same component referenced by root_trigger_id but uses a readable label assigned by the client for the originating trigger associated with a given message card. If no client-defined identifier is provided, this field will be null.

RootTriggerNickname__c

An optional nickname assigned to the top-level APITrigger component that initiated an experience. It corresponds to the same component referenced by root_trigger_id but uses an additional readable label assigned by the client for the originating trigger associated with a given message card. If no client-defined nickname is provided, this field will be null.

Added De-dup Logic on RelayEvents__c and RelayPowerups__c Objects

The Relay webhook push API follows an at least once delivery policy. This means it is possible to receive duplicate events. Based on customer feedback, Relay has added automatic de-dup logic to both objects. This will prevents duplicate records from being added.

Related articles