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 retrieve detailed information about a specific visual asset within a project. It is particularly useful for workflows that need to fetch metadata or details of visuals used in advertising campaigns, presentations, or digital content managed via AdBlast.
Typical use cases include:
- Automating retrieval of visual asset details for reporting or auditing.
- Dynamically fetching visual data to feed into other systems or processes.
- Integrating visual metadata into marketing automation workflows.
For example, you might use this node to get the details of a particular visual by specifying its project, scene, and visual IDs, then use that data downstream to update a database or trigger notifications.
Properties
| Name | Meaning |
|---|---|
| Authentication Method | Choose how to authenticate: "Predefined Credentials" (use saved API credentials) or "Dynamic API Key" (enter key dynamically). |
| 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; required if using dynamic API key authentication. |
| Project Id | The unique identifier of the project containing the visual. |
| Scene Id | The identifier of the scene within the project where the visual resides. |
| Visual Id | The identifier of the specific visual to retrieve. |
Output
The node outputs JSON data representing the details of the requested visual. This typically includes all metadata and properties associated with that visual as returned by the AdBlast API.
If the visual contains binary data (e.g., image files), the node may also output binary data fields corresponding to those assets, allowing further processing or storage.
Dependencies
- Requires access to the AdBlast API.
- Needs either saved API credentials configured in n8n or a dynamically provided API key.
- If using dynamic API key authentication, the user must provide the AdBlast base URL and API key at runtime.
Troubleshooting
- Authentication errors: Ensure the API key is valid and has sufficient permissions. Check that the correct authentication method is selected and credentials are properly configured.
- Invalid IDs: Verify that the Project Id, Scene Id, and Visual Id are correct and exist in the AdBlast system.
- Network issues: Confirm that the base URL is reachable from the n8n instance and there are no firewall restrictions.
- Empty or unexpected responses: Check if the visual actually exists and the API endpoint is functioning correctly.
Links and References
- AdBlast API Documentation (replace with actual documentation link if available)
- n8n Documentation on HTTP Request Node (for understanding API calls)