This topic was automatically generated from Slack. You can find the original thread here.
What does an event.trigger.context look like if it’s direct from a trigger to a webhook?
This topic was automatically generated from Slack. You can find the original thread here.
What does an event.trigger.context look like if it’s direct from a trigger to a webhook?
When an event is triggered directly from a webhook, the steps.trigger.context
contains metadata about the workflow and the execution tied to this event. Here is what the steps.trigger.context
typically includes: | Property | Description | | ------------------ | --------------------------------------------------------------------------- | | deployment_id
| A globally-unique string representing the current version of the workflow. | | emitter_id
| The ID of the workflow trigger that emitted this event, e.g., the event source ID. | | id
| A unique, Pipedream-provided identifier for the event that triggered this workflow. | | owner_id
| The Pipedream-assigned workspace ID that owns the workflow. | | platform_version
| The version of the Pipedream execution environment this event ran on. | | replay
| A boolean indicating whether the event was replayed via the UI. | | trace_id
| Holds the same value for all executions tied to an original event. | | ts
| The ISO 8601 timestamp at which the event invoked the workflow. | | workflow_id
| The workflow ID. | | workflow_name
| The workflow name. | This metadata helps you uniquely identify and manage the event within your workflow. You can access this data in any step of your workflow using steps.trigger.context
. For more detailed information, you can refer to the Pipedream documentation on workflows.