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 integrates with the AdBlast API to retrieve the configuration details of a "Score" resource. Specifically, it supports an operation to get the score configuration for a given project. This is useful in scenarios where you want to programmatically fetch scoring settings or parameters related to a project managed within AdBlast, such as for analytics, reporting, or further processing in an automation workflow.
Practical examples include:
- Automatically retrieving the current scoring configuration before running a campaign analysis.
- Syncing score configurations from AdBlast into another system for consistency.
- Triggering workflows based on specific score configuration values.
Properties
| Name | Meaning |
|---|---|
| Authentication Method | Method to authenticate API requests: - Predefined Credentials: Use saved API credentials. - Dynamic API Key: Enter API key dynamically using expressions. |
| AdBlast Base URL | The base URL for the AdBlast API (required if using Dynamic API Key authentication). |
| API Key | The API key for authenticating requests (required if using Dynamic API Key authentication). |
| Project Id | The unique identifier of the project whose score configuration you want to retrieve. |
Output
The node outputs JSON data representing the score configuration retrieved from the AdBlast API for the specified project. The exact structure depends on the API response but typically includes all relevant configuration details about scoring rules, thresholds, or parameters defined in the project.
No binary data output is indicated by the source code.
Dependencies
- Requires access to the AdBlast API.
- Requires either saved API credentials or a dynamically provided API key.
- The node expects the base URL and API key to be correctly configured depending on the chosen authentication method.
- No additional external dependencies beyond standard HTTP request capabilities.
Troubleshooting
- Authentication errors: Ensure that the API key is valid and has sufficient permissions. If using dynamic API key input, verify the expression resolves correctly.
- Invalid Project Id: Confirm that the provided project ID exists and is accessible with the given credentials.
- Base URL issues: When using dynamic authentication, ensure the base URL is correct and reachable.
- API rate limits or downtime: Check AdBlast service status if requests fail unexpectedly.
- Error messages: Typically will relate to HTTP status codes like 401 Unauthorized, 404 Not Found (invalid project), or 500 Server Error. Review credentials, project ID, and network connectivity accordingly.
Links and References
- AdBlast API Documentation (assumed base URL)
- n8n documentation on HTTP Request Node for understanding API integrations
- General best practices for managing API keys and credentials in n8n workflows