Skip to content

feat: Update actions.md #1667

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 3, 2025
Merged

feat: Update actions.md #1667

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
040c983
Update actions.md
jancurn Jul 3, 2025
30dc846
Update actions.md
jancurn Jul 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 9 additions & 9 deletions sources/platform/integrations/programming/webhooks/actions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -152,16 +152,16 @@ Note that the `eventData` and `resource` properties contain redundant data for b

## Headers template

The headers template is a JSON-like string where you can add additional information to the default header of the webhook request. You can pass the variables in the same way as in [payload template](#payload-template) (including the use of string interpolation and available variables). The resulting headers need to be a valid `json` object and values can be strings only.
The headers template is a JSON-like text where you can add additional information to the default HTTP header of the webhook request. You can pass the variables in the same way as in [payload template](#payload-template), including the use of string interpolation and the available variables. The resulting interpolated text need to be a valid JSON object, and values can be strings only.

Note that the following keys are hard-coded and will be always be rewritten:
Note that the following HTTP headers are always set by the system and your changes will always be rewritten:

| Variable | Value |
|---------------------------|-------------------------|
| `host` | request url |
| `Content-Type` | application/json |
| `X-Apify-Webhook` | Apify value |
| `X-Apify-Webhook-Dispatch-Id` | Apify id |
| `Host` | Request URL |
| `Content-Type` | `application/json` |
| `X-Apify-Webhook` | Apify internal value |
| `X-Apify-Webhook-Dispatch-Id` | Apify webhook dispatch ID |
| `X-Apify-Request-Origin` | Apify origin |

## Description
Expand All @@ -172,10 +172,10 @@ The description is an optional string that you can add to the webhook. It serves

| Variable | Type | Description |
|-------------|--------|-------------------------------------------------------------------------------------|
| `userId` | string | ID of the user who owns the webhook. |
| `userId` | string | ID of the Apify user who owns the webhook. |
| `createdAt` | string | ISO string date of the webhook's trigger event. |
| `eventType` | string | Type of the trigger event, [see Events](/platform/integrations/webhooks/events). |
| `eventData` | Object | Data associated with the trigger event, [see Events](/platform/integrations/webhooks/events). |
| `eventType` | string | Type of the trigger event, see [Events](/platform/integrations/webhooks/events). |
| `eventData` | Object | Data associated with the trigger event, see [Events](/platform/integrations/webhooks/events). |
| `resource` | Object | The resource that caused the trigger event. |
| `globals` | Object | Data available in global context. Contains `dateISO` (date of webhook's trigger event in ISO 8601 format) and `dateUnix` (date of trigger event in Unix time in seconds) |

Expand Down
Loading