Actions56
- Health Actions
- Project Actions
- Score Actions
- Characters Actions
- Environments Actions
- Scenes Actions
- Visuals Actions
- Visual Voiceover Actions
- Visual Image Actions
- Visual Video Actions
- Visual Sound Actions
- Video Actions
Overview
This node provides an interface to interact with the AdBlast API, specifically supporting a Health Check operation under the "Health" resource. The Health Check operation is typically used to verify that the AdBlast service is reachable and operational. This can be useful in workflows where you want to ensure the external service is up before proceeding with further actions, or for monitoring purposes.
Practical examples include:
- Running a periodic health check to monitor the status of the AdBlast API.
- Validating connectivity during workflow initialization.
- Triggering alerts or fallback logic if the service is down.
Properties
| Name | Meaning |
|---|---|
| Authentication Method | Method to authenticate requests: - Predefined Credentials: Use saved AdBlast API credentials. - Dynamic API Key: Enter API key dynamically using expressions. |
| AdBlast Base URL | The base URL for the AdBlast API. Required only when using Dynamic API Key authentication method. Defaults to https://dev.adblast.ai. |
| API Key | The API key for authenticating requests. Required only when using Dynamic API Key authentication method. Can be set dynamically via expressions. |
Output
The node outputs JSON data representing the response from the AdBlast API's health check endpoint. This typically includes status information indicating whether the service is healthy or not. The exact structure depends on the API but generally contains fields such as status codes, messages, or timestamps confirming service availability.
No binary data output is produced by this node.
Dependencies
- Requires access to the AdBlast API.
- Needs either saved API credentials configured in n8n or a dynamically provided API key.
- The base URL defaults to
https://dev.adblast.aibut can be customized when using dynamic authentication. - Proper network connectivity to the specified AdBlast API endpoint.
Troubleshooting
- Authentication errors: Ensure the API key is valid and correctly provided according to the selected authentication method.
- Connection issues: Verify the base URL is correct and the AdBlast API is reachable from your environment.
- Invalid responses: Confirm that the API has not changed its health check endpoint or response format.
- Missing credentials: If using predefined credentials, make sure they are properly set up in n8n; if using dynamic keys, confirm the expression resolves correctly.
Common error messages might include unauthorized access (401), not found (404) if the endpoint is incorrect, or network timeouts. Resolving these usually involves checking credentials, URLs, and network settings.
Links and References
- AdBlast API Documentation (assumed base URL for API docs)
- General n8n documentation on HTTP Request nodes and authentication