AdBlast

Interact with AdBlast API

Actions56

Overview

This node integrates with the AdBlast API to finalize the upload of a visual image associated with a specific scene in a project. It is designed to be used after an initial upload step (likely involving S3 or similar storage), where the upload process returns metadata such as a UUID, CDN URL, and relative path. This node sends these details to the AdBlast API to complete the upload process for a visual image within a scene.

Common scenarios:

Finalizing the upload of generated or edited images related to architectural or design projects.
Completing multi-step upload workflows where files are first uploaded to cloud storage and then registered/finalized via an API.
Automating asset management in creative or visualization pipelines.

Practical example:
After uploading a rendered image of a 3D scene to cloud storage, you use this node to notify AdBlast that the upload is complete by providing the upload UUID, CDN URL, and file path. This finalizes the image so it can be used or referenced in the project’s visual assets.

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 if using dynamic API key authentication)
API Key	The API key for authenticating requests (used if dynamic API key authentication is selected)
Project Id	The unique identifier of the project to which the visual image belongs
Scene Id	The unique identifier of the scene within the project
Visual Id	The unique identifier of the visual image being finalized
Uuid	The upload UUID returned from the S3M finalize response, used to identify the upload session
Cdn Url	The CDN URL from the S3M finalize response, pointing to the uploaded image
Path	The relative path of the uploaded image from the S3M finalize response

Output

The node outputs JSON data representing the response from the AdBlast API after finalizing the visual image upload. This typically includes confirmation details about the finalized upload, such as status, identifiers, or metadata confirming the image is now registered and accessible.

If the API supports binary data output (not indicated here), it would represent the finalized image or related assets, but based on the code and properties, the output is JSON only.

Dependencies

Requires access to the AdBlast API endpoint, either via predefined credentials stored securely in n8n or by dynamically providing the API key and base URL.
Network connectivity to the specified AdBlast Base URL.
Properly configured API key with permissions to finalize visual image uploads.
The node expects prior upload steps to provide the UUID, CDN URL, and path values needed to finalize the upload.

Troubleshooting

Authentication errors: Ensure the API key is valid and has the necessary permissions. If using dynamic API key input, verify the expression resolves correctly.
Invalid or missing parameters: The project_id, sceneId, visualId, uuid, cdn_url, and path must be accurate and correspond to existing resources and upload sessions.
Network issues: Confirm the base URL is reachable and correct, especially when using dynamic URLs.
API errors: Check the response message for details; common issues include expired upload UUIDs or mismatched project/scene IDs.
Expression errors: When using expressions for dynamic fields, ensure they resolve properly at runtime to avoid empty or malformed requests.

Links and References

AdBlast API Documentation (assumed base URL, check actual docs)
n8n documentation on HTTP Request Node for understanding API interactions
General guidance on handling API authentication in n8n

Note: This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.