AdBlast icon

AdBlast

Interact with AdBlast API

Actions56

Overview

This node integrates with the AdBlast API to update a specific visual element within a scene of a project. It is useful for automating modifications to visuals in multimedia projects, such as changing descriptions, playback durations, or ordering of visuals inside scenes. Practical applications include dynamically updating video or animation content based on external triggers or workflows, like adjusting scene visuals in response to user input or scheduled events.

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 for the AdBlast API (required if using dynamic API key authentication).
API Key The API key for authenticating requests when using dynamic API key authentication.
Project Id The unique identifier of the project containing the scene and visual to update.
Scene Id The identifier of the scene where the visual resides.
Visual Id The identifier of the visual element to update within the scene.
Number The visual's position number inside the scene, starting from 1.
Duration Seconds Playback duration of the visual in seconds; fractional values are supported.
Description A short textual description of the visual.

Output

The node outputs JSON data representing the updated visual object as returned by the AdBlast API. This typically includes confirmation of the updated fields such as number, duration, description, and identifiers confirming the visual was successfully modified. There is no indication that binary data is output by this node.

Dependencies

  • Requires access to the AdBlast API.
  • Needs either predefined API credentials stored in n8n or a dynamically provided API key.
  • The base URL for the API must be correctly set if using dynamic authentication.
  • Proper permissions on the AdBlast API to update visuals in projects/scenes.

Troubleshooting

  • Authentication errors: Ensure the API key or credentials are valid and have sufficient permissions.
  • Invalid IDs: Errors may occur if the project ID, scene ID, or visual ID do not exist or are mistyped.
  • Network issues: Verify the base URL is reachable and correct, especially when using dynamic URLs.
  • Incorrect property types: For example, providing non-numeric values for "Number" or "Duration Seconds" can cause request failures.
  • API limits or restrictions: Check if the AdBlast API enforces rate limits or other constraints that might block updates.

Links and References

  • AdBlast API Documentation (assumed base URL for API docs)
  • n8n documentation on HTTP Request nodes for understanding API integrations
  • General best practices for API authentication and error handling in n8n workflows

Discussion