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 video within a specified project. It is particularly useful for workflows that need to programmatically control or modify video processing states, such as toggling whether a full stitched video is being generated.
Typical use cases include:
- Automating video processing pipelines where you want to start or stop the generation of a stitched video.
- Managing video configurations dynamically based on external triggers or conditions.
- Integrating AdBlast video management into broader marketing or content workflows.
For example, you could use this node to set the processing flag to true when a new video upload is detected, triggering downstream processes that depend on the video being processed.
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 ("Dynamic API Key"). |
| AdBlast Base URL | The base URL of the AdBlast API endpoint. Required only if using dynamic API key authentication. Default is https://dev.adblast.ai. |
| API Key | The API key used for authenticating requests when using dynamic API key authentication. Can be set via expressions. |
| Project Id | The unique identifier of the project containing the video to update. |
| Processing | Boolean flag indicating whether the full stitched video is currently generating (true) or not (false). |
Output
The node outputs JSON data representing the response from the AdBlast API after updating the video configuration. This typically includes confirmation of the updated state or any relevant metadata returned by the API.
No binary data output is indicated in the source code.
Dependencies
- Requires access to the AdBlast API.
- Needs either predefined API credentials stored securely in n8n or a dynamically provided API key.
- The base URL for the API can be customized if using dynamic authentication.
- Proper network connectivity to the AdBlast service endpoint.
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 an incorrect or non-existent project ID will cause the API call to fail. Verify the project ID before running the node.
- Network issues: Connectivity problems to the AdBlast API base URL will result in request failures. Check network settings and firewall rules.
- Incorrect property usage: Make sure the
processingproperty is a boolean; otherwise, the API may reject the request.
Common error messages might include unauthorized access, resource not found, or bad request due to malformed input. Resolving these usually involves verifying credentials, project IDs, and input data formats.
Links and References
- AdBlast API Documentation (assumed base URL for API reference)
- n8n documentation on API Authentication and HTTP Request Node for general guidance on API integrations.