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 visual element within a video project. Specifically, it sets whether an image-to-video conversion process is currently active or not for a given visual asset.
Common scenarios where this node is useful include:
- Automating workflows that manage video content creation pipelines.
- Tracking and updating the processing state of visuals in video projects.
- Integrating with external systems to reflect real-time processing statuses.
For example, after triggering a video rendering job, you can use this node to mark the related visual as "processing" to inform downstream systems or users about the current state.
Properties
| Name | Meaning |
|---|---|
| Authentication Method | Choose between using saved API credentials or entering an API key dynamically via expressions. |
| AdBlast Base URL | The base URL of 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 containing the visual to update. |
| Scene Id | The identifier of the scene within the project. |
| Visual Id | The identifier of the specific visual element whose processing status will be updated. |
| Processing | Boolean flag indicating the processing status: true means processing is ongoing, false means not. |
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.
If the node supports binary data output, it would relate to media content or status reports, but based on the provided code and properties, the primary output is JSON confirming the status update.
Dependencies
- Requires access to the AdBlast API endpoint.
- Needs either predefined API credentials stored securely in n8n or a dynamically provided API key.
- Network connectivity to the specified AdBlast Base URL.
- Proper configuration of authentication method and API keys within the node parameters.
Troubleshooting
- Authentication errors: Ensure the API key is valid and has sufficient permissions. If using dynamic API key input, verify the expression correctly resolves to a valid key.
- Invalid project, scene, or visual IDs: Confirm that the IDs correspond to existing resources in your AdBlast account.
- Network issues: Check connectivity to the AdBlast Base URL and ensure no firewall or proxy blocks the requests.
- Incorrect processing value: The
processingproperty must be a boolean; passing other types may cause errors. - API rate limits or quota exceeded: Monitor usage to avoid hitting limits imposed by AdBlast.
Links and References
- AdBlast API Documentation (Base URL and API reference)
- n8n documentation on HTTP Request Node for understanding API integrations
- General best practices for managing API keys and credentials in n8n workflows