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 configuration of a film score within a specified project. Specifically, it allows users to toggle whether the full film score is currently being generated (processing state). This can be useful in workflows where you want to programmatically control or monitor the scoring process of media projects managed by AdBlast.
Common scenarios:
- Automatically marking a film score as "processing" when a new video edit is uploaded.
- Integrating with other systems to update the status of scoring dynamically based on external triggers.
- Managing multiple projects and their scoring states from a centralized automation platform.
Properties
| Name | Meaning |
|---|---|
| Authentication Method | Choose how to authenticate with the AdBlast API: - Predefined Credentials - Dynamic API Key |
| AdBlast Base URL | The base URL for the AdBlast API; required only if using Dynamic API Key authentication |
| API Key | The API key for authenticating requests; required only if using Dynamic API Key authentication |
| Project Id | The unique identifier of the project whose score configuration will be updated |
| Processing | Boolean flag indicating whether the full film score is currently generating (true/false) |
Output
The node outputs JSON data representing the response from the AdBlast API after updating the score configuration. This typically includes confirmation of the updated processing state and any related metadata about the score configuration.
The node does not output binary data.
Dependencies
- Requires access to the AdBlast API.
- Needs either:
- Saved API credentials configured in n8n (an API key and base URL), or
- Dynamic entry of the API key and base URL via node parameters.
- Proper network connectivity to the specified AdBlast API endpoint.
Troubleshooting
Authentication errors:
If the API key is invalid or missing, the node will fail to authenticate. Ensure that the correct API key is provided either through saved credentials or dynamic input.Invalid Project Id:
Providing an incorrect or non-existent project ID will cause the API call to fail. Verify the project ID before running the node.API Endpoint issues:
If the base URL is incorrect or the AdBlast service is unreachable, the node will throw connection errors. Confirm the base URL and network access.Boolean value handling:
Theprocessingproperty must be a boolean. Passing other types may cause unexpected behavior.
Links and References
- AdBlast API Documentation (assumed base URL for API reference)
- n8n documentation on HTTP Request Node for understanding API integrations and authentication methods