Introduction
Send an HTTP request to any endpoint during an automation run. Use this action to integrate Level automations with external systems — trigger webhooks, post data to an API, or call any HTTP endpoint as part of a workflow.
HTTP Request Action
From the automation pipeline in edit mode, click + and select HTTP request from the Other category.
URL
The endpoint to send the request to. Required. Click (x) to insert a variable, system variable, or custom field reference.
Example: https://hooks.example.com/services/webhook
Method
The HTTP method for the request.
Supported methods: GET, POST, PUT, DELETE, PATCH.
Content type
The content type of the request body.
Option | Use |
| JSON payloads |
| Plain text |
| Form submissions |
Body
The request body. Click (x) to insert variable references to include dynamic data from the pipeline.
Headers
Click + Add request headers to add custom key-value header pairs. Click (x) on either field to insert a variable reference. Click × to remove a header row.
Common headers:
Authorization: Bearer {{api_token}}X-API-Key: {{api_key}}
Conditions
The Conditions section lets you restrict when this action runs based on device attributes or the outcome of a previous action.
See Action Conditions for the full reference on condition types, operators, and values.
Additional Options
Expand Additional options for action name, failure behavior, output variable assignment, retries, and the enabled toggle.
💡 TIP: Use Assign action output to variable in Additional options to capture the HTTP response body into an automation variable. This lets subsequent actions act on the response — for example, checking a status field returned by an API.
See Actions Overview for the full reference on additional options available on every action.
FAQ
What counts as a successful request? A request is considered successful when the endpoint returns a 2xx HTTP response code. Any non-2xx response (4xx or 5xx) is treated as an error and the action will be marked as failed.
Can I send JSON in the body? Yes — set
Content-Type: application/jsonin the Headers section and write your JSON payload in the Body field.Can I authenticate to a protected endpoint? Yes — include an
Authorizationheader with your token or credentials. Use (x) to reference a stored automation variable or custom field rather than hardcoding the value.Who can add or modify HTTP Request actions? Technicians with permission to edit automations in the relevant group. See Workspace → Permissions for access control configuration.