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 a score. It is designed to confirm and complete the process of uploading scoring data, typically after an initial upload step has been performed and a response containing upload identifiers (UUID, CDN URL, path) has been received.
Common scenarios include:
- Finalizing the upload of scoring results or analytics data to AdBlast's platform.
- Confirming that the uploaded data is ready for further processing or analysis within AdBlast.
- Automating workflows where scores are generated externally and need to be registered in AdBlast via their API.
Practical example:
- After uploading raw score data to a temporary storage or staging area, this node finalizes the upload by sending the required identifiers back to AdBlast, ensuring the data is properly registered and accessible through their system.
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; used when dynamic API key authentication is selected. |
| Project Id | The identifier of the project within AdBlast to which the score upload belongs. |
| Uuid | The unique upload identifier received from the S3M finalize response, used to reference the upload. |
| Cdn Url | The CDN URL from the S3M finalize response, indicating where the uploaded content is hosted. |
| Path | The relative path from the S3M finalize response, specifying the location of the uploaded data. |
Output
The node outputs JSON data representing the response from the AdBlast API after finalizing the score upload. This typically includes confirmation details about the finalized upload, such as status or metadata returned by the API.
There is no indication that the node outputs binary data.
Dependencies
- Requires access to the AdBlast API endpoint.
- Needs either predefined API credentials stored securely in n8n or a dynamically provided API key.
- If using dynamic authentication, the user must provide the base URL and API key at runtime.
- No other external dependencies are indicated.
Troubleshooting
- Authentication errors: Ensure that the API key is valid and correctly provided, either via saved credentials or dynamic input.
- Invalid 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.
- Base URL misconfiguration: When using dynamic authentication, verify that the base URL is correct and reachable.
- API response errors: Check the API response message for specific issues like permission denied, invalid parameters, or server errors.
Links and References
- AdBlast API Documentation (assumed base URL for API docs)
- n8n documentation on HTTP Request Node for understanding API interactions (general reference).