HTTP Actions
The Blink platform offers various HTTP actions such as GET, POST, PATCH, PUT, DELETE, HEAD, OPTIONS, and GraphQL.
Actions
Send HTTP Request
Executes an HTTP request with the chosen method on a provided URL.
| Parameter | Description |
|---|---|
| Method | Which HTTP method to use in the request. |
| URL | The URL to communicate with. |
| Body | Request Body. |
| Headers | Request Headers should be Name: Value (Accept: application/json) |
| Cookies | Request Cookies should be Name=Value (jwt=TOKEN) |
| Retry On Rate Limit | If enabled, and when rate limits are reached, the system will retry the HTTP request after the designated time period specified in the rate limit headers or through the use of exponential backoff. |
| Disable SSL Enforcement | Enable this option to skip SSL verification of the server’s certificate chain and host name. This may increase security vulnerabilities, but can be useful for testing or when custom verification is employed. |
Send HTTP GraphQL Request
Executes GraphQL query on provided URL.
| Parameter | Description |
|---|---|
| URL | The URL to communicate with. |
| Query | GraphQL query. |
| Variables | GraphQL query variables. |
| Headers | Request Headers to be added to the request in the format Name: Value. For example: Content-Type: application/json. |
| Retry On Rate Limit | If enabled, and when rate limits are reached, the system will retry the HTTP request after the designated time period specified in the rate limit headers or through the use of exponential backoff. |
| Disable SSL Enforcement | Enable this option to skip SSL verification of the server’s certificate chain and host name. This may increase security vulnerabilities, but can be useful for testing or when custom verification is employed. |
Send HTTP Upload File Request
Uploads a file to the provided URL using an HTTP request.
| Parameter | Description |
|---|---|
| Method | Which HTTP method to use in the file upload request. The default value for the request is POST. |
| URL | The URL to communicate with. |
| Body | Request Body. |
| Headers | Request Headers should be Name: Value (Accept: application/json) |
| File Identifier | The identifier of the file. You can create a file identifier using the Set File Variable action. |
| File Param Name | The parameter name of the file to upload. |
| Cookies | Request Cookies should be Name=Value (jwt=TOKEN) |
| Retry On Rate Limit | If enabled, and when rate limits are reached, the system will retry the HTTP request after the designated time period specified in the rate limit headers or through the use of exponential backoff. |
| Disable SSL Enforcement | Enable this option to skip SSL verification of the server’s certificate chain and host name. This may increase security vulnerabilities, but can be useful for testing or when custom verification is employed. |
Standard non-authenticated HTTP requests
The most basic way to use HTTP Actions is without authentication.
Authenticated HTTP requests to existing service providers
HTTP Actions can be used with most of the Blink connection types to send authenticated requests to existing service providers in Blink. For example, to send an authenticated request to GitHub’s API, use a GitHub connection.
Authenticated HTTP requests to unsupported service providers
Blink adds support for additional service providers on a weekly basis. To use Actions with a service provider that is not currently supported, there are two options:
- Contact the Blink team to request integration with a new service provider. Contact us.
- Use generic HTTP Actions to communicate with unsupported service providers, as explained below.
Using generic HTTP actions to communicate with unsupported service providers
HTTP Actions can be used with one of the three HTTP connection types to send authenticated requests to service providers that aren’t currently supported by Blink:
- HTTP Basic Authentication
- HTTP Bearer Authentication
- HTTP Custom Authentication
For example, to communicate with a service provider called X that isn’t supported by Blink and requires Basic Authentication:
-
Create an
HTTP Basic Authenticationconnection with the required credentials.
-
Use the connection to perform the Action, and the outgoing HTTP request will be sent with the appropriate authentication headers.
Usage Via Paste
HTTP steps can easily be created using the paste feature on the edit screen. If a valid curl command is pasted, it will be parsed into an HTTP step with the appropriate request type, URL, body, headers, and cookies. If a URL is pasted, an HTTP GET step will be created using the provided URL.
The HTTP actions created this way will be added last to the list of actions that the Workflow may already have.