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 update project data. It allows users to modify existing projects by sending new JSON-formatted data to the specified project ID. This is useful in scenarios where project details need to be programmatically updated, such as syncing project information from other systems, automating updates based on external triggers, or managing project metadata dynamically.
For example, a marketing team could use this node to update campaign project details automatically when new data becomes available from analytics tools, ensuring that project information stays current without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Authentication Method | Choose how to authenticate requests: - Predefined Credentials: Use saved API credentials configured in n8n. - Dynamic API Key: Enter an API key dynamically using expressions at runtime. |
| AdBlast Base URL | The base URL for the AdBlast API. Required only if using Dynamic API Key authentication. Defaults to https://dev.adblast.ai. |
| API Key | The API key for authenticating with the AdBlast API. Required only if using Dynamic API Key authentication. Can be set using expressions to retrieve keys dynamically. |
| Project Id | The unique identifier of the project to update. This tells the node which project’s data should be modified. |
| Data | A valid JSON string representing the new data to update the project with. This must be properly formatted JSON and will be sent as the request body to the API. Example: ["architecto","architecto"] |
Output
The node outputs the response from the AdBlast API after attempting to update the project data. The output is structured as JSON and typically contains the updated project information or confirmation of the update operation.
If the API supports it, binary data output is not indicated in the provided code or properties, so the output is expected to be purely JSON.
Dependencies
- Requires access to the AdBlast API.
- Needs either:
- Predefined API credentials stored securely within n8n, or
- A dynamic API key provided at runtime.
- If using dynamic authentication, the user must specify the correct base URL for the AdBlast API.
- The node expects the API to accept JSON payloads and respond with JSON.
Troubleshooting
- Invalid JSON in Data Property: Since the
dataproperty must be a valid JSON string, malformed JSON will cause errors. Ensure the JSON string is correctly formatted. - Authentication Errors: Using incorrect or expired API keys will result in authorization failures. Verify that the API key is valid and has sufficient permissions.
- Incorrect Project ID: Providing a non-existent or invalid project ID will likely cause the API to return an error indicating the project was not found.
- Base URL Misconfiguration: When using dynamic API key authentication, ensure the base URL is correct and reachable; otherwise, connection errors will occur.
- API Rate Limits or Quotas: If the API enforces rate limits, excessive requests may lead to throttling errors.
Links and References
- AdBlast API Documentation (Assumed base URL for API docs)
- n8n Documentation on Creating Custom Nodes
- JSON Validation Tools (e.g., https://jsonlint.com/) to verify the correctness of the
datainput property.