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 finalize the upload of an environment image. It is designed to be used after an image has been uploaded to a storage service (such as S3) and the upload process needs to be confirmed or finalized within the AdBlast system.
Common scenarios include:
- Completing an image upload workflow where images are first uploaded to a cloud storage, then registered or finalized in AdBlast.
- Automating environment setup processes that require associating uploaded images with specific projects and environments in AdBlast.
- Managing environment assets programmatically in CI/CD pipelines or content management workflows.
Practical example:
- After uploading an environment image to S3, use this node to send the upload UUID, CDN URL, and relative path to AdBlast to mark the upload as complete and make the image available for use in the specified project and environment.
Properties
| Name | Meaning |
|---|---|
| Authentication Method | Choose how to authenticate with the AdBlast API: - Predefined Credentials: Use saved API credentials configured in n8n. - Dynamic API Key: Enter the API key dynamically using expressions. |
| AdBlast Base URL | The base URL for the AdBlast API. Required only if using Dynamic API Key authentication. Default is https://dev.adblast.ai. |
| API Key | The API key for authenticating with AdBlast. Required only if using Dynamic API Key authentication. Can be set via expressions. |
| Project Id | The ID of the AdBlast project to which the environment belongs. |
| Environment Id | The identifier of the environment within the project. |
| Uuid | The unique upload identifier returned from the S3M finalize response. This confirms which upload is being finalized. |
| Cdn Url | The CDN URL of the uploaded image, obtained from the S3M finalize response. |
| Path | The relative path of the uploaded image, also from the S3M finalize response. |
Output
The node outputs JSON data representing the response from the AdBlast API after finalizing the environment image upload. This typically includes confirmation details about the finalized upload, such as status, identifiers, or metadata related to the environment image.
If the API returns binary data (not indicated here), it would represent the finalized image or related asset, but based on the properties and typical API usage, the output is expected to be JSON confirming the upload finalization.
Dependencies
- Requires access to the AdBlast API endpoint, either via predefined credentials stored securely in n8n or by providing a dynamic API key and base URL.
- Network connectivity to the specified AdBlast base URL.
- Proper permissions associated with the API key to finalize environment image uploads.
- No additional external libraries beyond those bundled with n8n and the included OpenAPI client.
Troubleshooting
- Authentication errors: If the node fails due to invalid API keys or missing credentials, verify that the correct authentication method is selected and that the API key or credentials are valid and have sufficient permissions.
- Invalid project or environment IDs: Ensure that the provided
project_idandenvironmentIdcorrespond to existing entities in AdBlast. - Incorrect UUID, CDN URL, or path: These values must come from a successful prior upload finalize response; incorrect or missing values will cause the API call to fail.
- Network issues: Confirm that the base URL is reachable and that there are no firewall or proxy restrictions blocking the request.
- API errors: Review the error message returned by the API for hints; common issues include rate limiting, malformed requests, or expired tokens.
Links and References
- AdBlast API Documentation (assumed URL based on default base URL)
- n8n documentation on HTTP Request Node for understanding API integrations
- General best practices for managing API keys and credentials in n8n: Managing Credentials
Note: This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.