Anodot Custom Action
Executes an HTTP request with the chosen method on the provided URL or API endpoint.
Basic Parameters
| Parameter | Description |
|---|---|
| Headers | Request Headers to be added to the request in the format Name: Value, separated by newlines. For example: Content-Type: application/json. |
| Method | Which HTTP method to use in the request. |
| Request Body | JSON data to send in the request body. |
| Request URL Or API Endpoint | The URL or API endpoint to communicate with. You may specify either a full URL or a relative endpoint path: For example, for an action in URL https://myapiaddress.com/api/path it is enough to specify only /path. |
Advanced Parameters
| Parameter | Description |
|---|---|
| Account Key | Which account key to use for authentication. Must be used with a valid Division ID. If not provided, will default to use the first Account Key and Division ID found. |
| Cookies | Web cookies to include in the request in the format Name=Value, separated by newlines. For example: JWT=Token. |
| 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. |
| Division ID | Which division ID to use for authentication. Must be used with a valid Account Key. If not provided, will default to use the first Account Key and Division ID found. |
| 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. |
Workflow Library Example
Anodot Custom Action and Send Results Via Email
Preview this Workflow on desktop