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 an existing scene within a specified project. It allows users to modify key attributes of a scene such as its number, narrative label, and visible goal. This is useful in scenarios where story or project scenes need to be programmatically adjusted or refined based on evolving requirements or dynamic inputs.
Practical examples include:
- Updating the sequence number of a scene to reorder it within a project.
- Changing the narrative function label to reflect a different storytelling role.
- Modifying the visible goal text to clarify or update the scene's objective.
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 (required if using dynamic API key authentication). |
| Project Id | The unique identifier of the project containing the scene to update. |
| Scene Id | The unique identifier of the scene to update. |
| Number | The sequential number of the scene starting from 1; used to order scenes. |
| Label | The narrative function of the scene. Options: HOOK, FORESHADOW VALUE DISCOVERY, ALL IS LOST SOLUTION TRIGGER, CLIMAX TWIST PAYOFF, TRANSFORMATION CTA. |
| Visible Goal | A string describing the visible goal or objective of the scene. |
Output
The node outputs JSON data representing the updated scene object returned by the AdBlast API. This typically includes the updated properties such as scene ID, number, label, visible goal, and any other metadata provided by the API response.
No binary data output is produced by this node.
Dependencies
- Requires access to the AdBlast API endpoint.
- Requires either predefined API credentials stored 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.
- Proper network connectivity to the AdBlast service is necessary.
Troubleshooting
- Authentication errors: Ensure that the API key is valid and has sufficient permissions. If using dynamic API key input, verify the expression syntax and that the key is correctly passed.
- Invalid Project or Scene IDs: Confirm that the provided project and scene identifiers exist and are accessible with the given credentials.
- Incorrect property values: For example, the scene number should be a positive integer starting from 1; labels must be one of the predefined options.
- API endpoint issues: If using a custom base URL, ensure it is correct and reachable.
- Error messages from API: Typically indicate invalid parameters or authorization failures; review the error details and adjust inputs accordingly.
Links and References
- AdBlast API Documentation (Assumed base URL for API reference)
- n8n Documentation on Creating Custom Nodes