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 version information for a specific project. It is useful when you need to programmatically access all versions associated with a given project in AdBlast, such as for auditing, reporting, or synchronization purposes.
Typical use cases include:
- Fetching all versions of a project to display or process downstream.
- Automating workflows that depend on project version data.
- Integrating AdBlast project version data into other systems or dashboards.
For example, you might use this node to get all versions of a marketing campaign project to analyze changes over time or trigger actions based on version updates.
Properties
| Name | Meaning |
|---|---|
| Authentication Method | Choose how to authenticate: "Predefined Credentials" (use saved API credentials) or "Dynamic API Key" (enter key dynamically via expressions). |
| AdBlast Base URL | The base URL of the AdBlast API. Required only if using dynamic API key authentication. |
| API Key | The API key for authenticating requests. Required only if using dynamic API key authentication. |
| Project Id | The unique identifier of the project whose versions you want to retrieve. |
Output
The node outputs JSON data containing the list of versions for the specified project. Each item in the output corresponds to a project version object returned by the AdBlast API. The exact structure depends on the API response but typically includes version identifiers, metadata, timestamps, and related details.
No binary data output is produced by this node.
Dependencies
- Requires access to the AdBlast API endpoint.
- Requires an API key credential for authentication, either predefined in n8n or provided dynamically.
- The base URL defaults to
https://dev.adblast.aibut can be customized if needed.
Troubleshooting
- Authentication errors: Ensure the API key is valid and has sufficient permissions. If using dynamic API key input, verify the expression correctly resolves to a valid key.
- Invalid Project Id: Confirm the project ID exists in AdBlast and is correctly entered.
- Network issues: Check connectivity to the AdBlast API base URL.
- API rate limits: If receiving rate limit errors, consider adding delays or retries in your workflow.
Common error messages may include unauthorized access, not found errors for invalid project IDs, or connection timeouts. Resolving these usually involves verifying credentials, project ID correctness, and network availability.
Links and References
- AdBlast API Documentation (replace with actual docs URL if available)
- n8n documentation on HTTP Request Node for understanding API integrations
- General API authentication best practices