docs: document webhook response toggle and triggering event context properties

- Add Return Event as Response Payload toggle documentation to webhooks page
- Add triggering_event_id and triggering_event_key properties to Python Context reference
- Add triggeringEventId() and triggeringEventKey() methods to TypeScript Context reference

Related to PR hatchet-dev#3625

Author: promptless[bot]

frontend/docs/pages/reference/python/context.mdx

@@ -132,6 +132,26 @@ Returns:
 | ------------- | --------------------------------------------------------- |
 | `str \| None` | The id of the workflow version that this task belongs to. |
 
+#### `triggering_event_id`
+
+The external ID of the event that triggered this workflow run, if any. Useful for correlating tasks back to the originating event when your workflow was triggered by an [event](/v1/external-events/run-on-event) or [webhook](/v1/webhooks).
+
+Returns:
+
+| Type          | Description                                                                              |
+| ------------- | ---------------------------------------------------------------------------------------- |
+| `str \| None` | The external ID of the triggering event, or None if the workflow was not event-triggered. |
+
+#### `triggering_event_key`
+
+The key of the event that triggered this workflow run, if any. This corresponds to the event key used when the event was pushed or generated by a webhook.
+
+Returns:
+
+| Type          | Description                                                                         |
+| ------------- | ----------------------------------------------------------------------------------- |
+| `str \| None` | The key of the triggering event, or None if the workflow was not event-triggered. |
+
 #### `task_run_errors`
 
 A helper intended to be used in an on-failure step to retrieve the errors that occurred in upstream task runs.

frontend/docs/pages/reference/typescript/Context.mdx

@@ -308,6 +308,30 @@ Returns
 
 True if the workflow was triggered by an event, otherwise false.
 
+<a id="triggeringeventid"></a>
+
+##### `triggeringEventId()`
+
+Gets the external ID of the event that triggered this workflow run. Useful for correlating tasks back to the originating [event](/v1/external-events/run-on-event) or [webhook](/v1/webhooks).
+
+Returns
+
+`string` \| `undefined`
+
+The triggering event external ID, or undefined if not triggered by an event.
+
+<a id="triggeringeventkey"></a>
+
+##### `triggeringEventKey()`
+
+Gets the key of the event that triggered this workflow run. This corresponds to the event key used when the event was pushed or generated by a webhook.
+
+Returns
+
+`string` \| `undefined`
+
+The triggering event key, or undefined if not triggered by an event.
+
 <a id="triggers"></a>
 
 ##### `triggers()`

frontend/docs/pages/v1/webhooks.mdx

@@ -62,6 +62,12 @@ The **Static Payload** is an optional JSON object that gets merged with the inco
 
 For example, if you set a static payload of `{"source": "stripe", "environment": "production"}` and receive a webhook with `{"type": "payment_intent.created", "source": "api"}`, the final payload passed to your workflow would be `{"type": "payment_intent.created", "source": "stripe", "environment": "production"}`.
 
+#### Return Event as Response Payload
+
+The **Return Event as Response Payload** toggle controls whether Hatchet returns the triggered event in the webhook HTTP response. This is enabled by default but can be disabled to avoid exposing sensitive information in responses.
+
+When enabled, the response includes the created event with its ID, which is useful for correlating webhook triggers with specific workflow runs. When disabled, the response omits the event payload.
+
 #### Authentication
 
 Finally, you'll need to specify how Hatchet should authenticate incoming webhook requests. For non-generic sources like Stripe and Github, Hatchet has presets for most of the fields, so in most cases you'd only need to provide a secret.