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 the processing status of a specific environment within a project. It is useful in workflows where you need to programmatically control or monitor the state of environments, for example, marking an environment as currently processing or not. Practical applications include automation pipelines that manage deployment states, trigger downstream processes based on environment readiness, or synchronize environment statuses across systems.
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 endpoint; required if using dynamic API key authentication. |
| API Key | The API key for authenticating requests; required if using dynamic API key authentication. |
| Project Id | The unique identifier of the project containing the environment to update. |
| Environment Id | The unique identifier of the environment whose processing status will be set. |
| Processing | Boolean flag indicating the desired processing status (true = processing, false = not processing). |
Output
The node outputs JSON data representing the response from the AdBlast API after setting the environment's processing status. This typically includes confirmation of the updated status and any relevant metadata returned by the API. The output does not include binary data.
Dependencies
- Requires access to the AdBlast API.
- Needs either saved API credentials configured in n8n or a dynamically provided API key.
- If using dynamic authentication, the user must provide the correct base URL and API key at runtime.
- The node sets HTTP headers including
Authorizationwith a Bearer token and expects JSON content.
Troubleshooting
- Authentication errors: Ensure the API key is valid and has sufficient permissions. If using predefined credentials, verify they are correctly saved and selected.
- Invalid Project or Environment IDs: Confirm that the provided IDs exist and are correctly spelled.
- Network issues: Check connectivity to the specified AdBlast base URL.
- API errors: Review the API response for error messages indicating issues such as rate limits or malformed requests.
- Missing required properties: Make sure all required fields (Project Id, Environment Id, Processing) are provided.
Links and References
- AdBlast API Documentation (assumed base URL for API reference)
- n8n documentation on HTTP Request Node for understanding API integrations