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 update the processing status of a specific score within a project. It is useful in workflows where you need to programmatically mark whether a score is currently being processed or not, enabling automation around score management and tracking.
Practical examples include:
- Automatically marking scores as "processing" when starting an analysis pipeline.
- Clearing the processing flag once downstream tasks complete.
- Integrating with other systems that require real-time updates on score processing states.
Properties
| Name | Meaning |
|---|---|
| Authentication Method | Choose how to authenticate with the AdBlast API: either using saved credentials ("Predefined Credentials") or by entering an API key dynamically at runtime ("Dynamic API Key"). |
| AdBlast Base URL | The base URL for the AdBlast API. Required only if using dynamic API key authentication. Defaults to https://dev.adblast.ai. |
| API Key | The API key for authenticating requests to the AdBlast API. Required only if using dynamic API key authentication. Supports expressions. |
| Project Id | The unique identifier of the project containing the score whose processing status you want to set. |
| Processing | Boolean flag indicating the processing status to set for the score (true for processing, false otherwise). |
Output
The node outputs JSON data representing the response from the AdBlast API after setting the processing status. This typically includes confirmation of the updated status or any relevant metadata returned by the API.
No binary data output is produced by this node.
Dependencies
- Requires access to the AdBlast API endpoint.
- Requires an API key credential for authentication, either predefined in n8n or provided dynamically.
- The node uses HTTP requests with JSON payloads and expects JSON responses.
- No additional external dependencies beyond standard HTTP and JSON handling.
Troubleshooting
- Authentication errors: If the API key is invalid or missing, the node will fail to authenticate. Ensure the correct API key is provided and matches the selected authentication method.
- Invalid Project Id: Providing a wrong or non-existent project ID will cause the API to reject the request. Verify the project ID is correct.
- Network issues: Connectivity problems or incorrect base URL configuration can lead to request failures. Confirm the base URL is reachable and correctly set.
- API rate limits: Excessive requests may be throttled by the AdBlast API. Implement retry logic or reduce request frequency if needed.
Common error messages usually relate to authorization failures (401 Unauthorized), resource not found (404), or bad requests (400). Checking the API response message helps identify the exact issue.
Links and References
- AdBlast API Documentation (assumed base URL; consult official docs for full API details)
- n8n documentation on HTTP Request Node for understanding underlying request mechanics