Prerequisites: This workflow item is only available via consultation with your account manager. Please talk to your account manager if you would like to have this activated for your organisation.
Send HTTP request is used to send HTTP requests from Automation to other systems. It accepts unique URLs and sends data to them in JSON format.
Endpoint: A HTTP or HTTPS address where the data will be sent to. E.g. https://staging.learninglocker.net/
Headers: Add HTTP headers into the HTTP request. You could use this to specify things like Content-Type, Authorization, or Content-Length.
Auth: Select which auth type is send in the HTTP request. Selecting "Basic Auth" will reveal Key and Secret fields.
- GET: Requests information which can then be used to populate a custom variable in .
- POST: Sends data to the server and creates a new resource.
- PUT: Most often used to update an existing resource.
- PATCH: Very similar to the PUT method because it modifies an existing resource as well. The difference between them is that for the PUT method, the request body contains the complete new version, whereas for the PATCH method, the request body only needs to contain the specific changes to the resource.
- DELETE: Used to delete a resource specified by its URL.
JSON: Build the JSON string to be sent in your request. The editor has validation so you will not be able to save unless it has been correctly formatted. You can use variables in the JSON data by placing them directly in the value string:
The editor allows variables wrapped in {{ }} to resolve to valid JSON (objects, arrays, numbers, booleans) to be used directly in the request body without triggering validation errors. Mixed payloads (static JSON + variables) are safely allowed. Final JSON validity is enforced at runtime, where actual values are known.
Potential use cases include:
- Passing API responses or transformed data directly into an HTTP request body
- Reusing variables that contain full JSON objects or arrays
- Building workflows that construct payloads dynamically at runtime
- Sending non-string JSON values (e.g., numbers or booleans) via variables
Outputs: Store the response from the HTTP request in custom variables. To do this, you'll need to be familiar with the kind of data your HTTP request returns.
For example: To get the ID of a user you have just sent a request for you can enter the following:
Tip: During testing if you just want to see what is returned enter the following in the outputs and then check the variables and you will be able to see what data is returned in the request.