Actions80
- Todos Actions
- Card Tables Actions
- Forwards Actions
- Events Actions
- Recordings Actions
- Projects Actions
- People Actions
- Chatbots Actions
- Webhooks Actions
- Attachments Actions
- Templates Actions
- Uploads Actions
- Documents Actions
- Lineup Markers Actions
- Subscriptions Actions
- Schedules Actions
- Schedule Entries Actions
- Todo Sets Actions
- Todo Lists Actions
Overview
This node operation, Destroy Lineup Marker, is designed to delete a specific lineup marker identified by its unique ID. It is useful in scenarios where you need to programmatically remove markers from a lineup or schedule, such as clearing outdated or incorrect markers in an event planning or broadcasting workflow.
For example, if you have a list of markers representing segments in a live show and one segment is canceled, this operation can be used to remove the corresponding marker automatically.
Properties
| Name | Meaning |
|---|---|
| Marker Id | ID of the marker to destroy |
The only required input property is the Marker Id, which specifies the numeric identifier of the lineup marker that should be deleted.
Output
The output JSON structure is not explicitly detailed in the provided source code snippet. However, typically for a "destroy" or "delete" operation, the output would confirm whether the deletion was successful, often returning a status message or the deleted marker's ID.
If the node supports binary data output, it would likely relate to any files or media associated with the marker, but no such indication is present here.
Dependencies
- This node requires an API key credential or OAuth2 token configured in n8n to authenticate requests to the external service managing lineup markers.
- The base URL for API requests is dynamically constructed using credentials (e.g., a Basecamp ID), indicating integration with an external API endpoint.
- The node depends on the
@devlikeapro/n8n-openapi-nodepackage for building properties and handling OpenAPI specifications.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Marker Id will likely result in an error response from the API.
- Missing or incorrect API authentication credentials will prevent the node from successfully deleting the marker.
- Network connectivity problems could cause request failures.
Error messages:
- Errors related to authorization usually indicate missing or invalid API keys or tokens; ensure credentials are correctly set up.
- "Marker not found" or similar errors suggest the specified Marker Id does not exist; verify the ID before running the node.
- Timeout or connection errors may require checking network settings or API availability.
Links and References
- No direct links were provided in the source code. For more information, consult the documentation of the external API managing lineup markers or the n8n community forums for usage examples.