You can configure Triggers and Actions on your Object Types to pass a Record (an instance of the data) along to an Agent for processing.
Triggers - These are configured on Object Types and pass a new (post insert), updated (post-update) or deleted (post-delete) record along to the designated Agent for processing.
Actions - These can be manually run or triggered via API. To run an Action manually you configure the Action on the Object Type and then execute it in the overflow menu for the record itself.
Note that the format of a Trigger payload for a Record is slightly different than that for an Action.
On a Trigger the record is passed and directly available on msg.payload.
On an Action it will be under an instance property, so msg.event.instance.
For all of the examples below, we will use the following sample weather-report record:
A post-insert trigger payload delivered to an Event processing agent (flow) sets both msg.payload and msg.event to the same initial value
Shown below is the msg object with the properties received as a result of a Post-Insert trigger. Note that payload shows "circular" because it is the same as msg.event.
In addition, note the various metaData, topic, and headers that provide additional context about the event being received, including the name of the object-type in the "x-type-id" header and the "x-kind" header which indicates that it was a "trigger" that sent the event. Finally the "x-subkind" header documents that it was a "post-insert" trigger.
Post-Update Trigger Payload
The msg object received by a post-update trigger has a different structure because it carries with it both the "old" and the "new" version of the record, as shown below:
An action is defined in object-type settings for a specific object-type and allows the user to invoke a specified action on an individual record. The action performs a SentToAgent to a specific agent, and the sample msg contents as shown below.
Note that the actual record contents in the case of action are in event.instance. This is because an action can also send “params” or parameters to the flow and these are passed in event.params.
Since the specific action-name is provided in the x-name header, a single flow/agent can be used to process multiple actions.
The final use case is that of the event that is received when it is sent by a "SendToAgent" node in a flow.
Shown below is the msg object with the properties received as a result of a SendToAgent node. Note that payload shows "circular" because it is the same as msg.event.
