Actions
Send HTTP Request
Execute an HTTP request with the chosen method on a provided URL.| Parameter | Description |
|---|---|
| Method | The HTTP method to use in the request. |
| URL | The URL to communicate with. |
| Body | The content of the request body. |
| Headers | Request Headers to be added to the request, as a string in the format of Name: Value, separated by new lines.For example: |
| Cookies | Web cookies to include in the request in the format Name: Value, separated by new lines.For example: |
| Retry On Rate Limit | When checked, and 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 | When checked, the SSL verification of the server’s certificate chain and host name will be skipped. This option 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 | The content of the request body. |
| Headers | Request Headers to be added to the request, as a string in the format of Name: Value, separated by new lines.For example: |
| 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 | Web cookies to include in the request in the format Name: Value, separated by new lines.For example: |
| Retry On Rate Limit | When checked, and 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 | When checked, the SSL verification of the server’s certificate chain and host name will be skipped. This option may increase security vulnerabilities, but can be useful for testing or when custom verification is employed. |
Learn about how Blink handles Rate Limits automatically in HTTP requests.
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
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.
