🌐HTTP Request
Connect to external APIs
Last updated
Connect to external APIs
Last updated
The HTTP request node allows you to make external API calls to services not yet listed in our integrations marketplace. For example you could make a request to the OpenAI API or if you would like to send an email via SendGrid you can.
A reference to the connection (API Token) you would like to use within the request.
The URL for the endpoint to would like to make a request to.
Each method has a specific purpose, such as requesting data from a server (GET) or submitting data to a server for processing (POST) view the table below for a list of the supported HTTP methods.
Verb | Description |
---|---|
A header is a piece of information included in a HTTP request that provides additional context about the content or about the client/server communication. APIs that require headers often specify this in their documentation using the notation "-H".
In most instances you will need to include an authorisation header when connecting to a third-party service. To do this you can reference the connection epecified above.
A query parameter is a way to pass extra information in a HTTP request, often used to filter or sort the results.
Whilst query parameters are encrypted during transit when using HTTPS it is very poor practice to include sensitive data such as a password in query parameters especially 'GET' requests.
Body parameters are not available for GET
requests.
A body parameter is also a way to pass extra information in a HTTP request, unlike query parameters which are included in the URL, body parameters are sent in the requests body.
Unlike query parameters, body parameters support data types allowing you specify the type of the data included in the request. If the data passed is not in the correct format the data will be cast to the correct type or null if an exception occurs.
A cookie is also a way to pass extra information in a HTTP request, often used to send authorisation tokens.
Caching is a technique used to store frequently accessed data in a temporary storage location, called a cache, so that it can be quickly retrieved without the need to access the original data source. This can significantly improve performance and reduce the load on the original data source.
This option enabled the cache.
This option determines the lend of time the data will be stored in the cache.
Requires an active authentication integration
In addition to caching based on the query parameters defined, user-based caching ensures the data cached for one logged-in user cannot be returned to another logged-in user.
The response returned from the HTTP request.
This property equals the status code returned from the server.
This property contains the HTTP headers returned from the server.
This property contains the cookies returned from the server.
We recommend adding the Logic node after the HTTP request node to check for unexpected errors.
Key | Value |
---|---|
GET
Receive data
POST
Create new data
PUT
Update existing data
PATCH
Modify a specific portion of the data
DELETE
Delete data
Authorization
Bearer {{connection.key}}