Actions80
- 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
- Todos Actions
Overview
This node operation updates an existing lineup marker by specifying its unique identifier and optionally changing its name and date. It is useful in scenarios where you need to modify metadata or scheduling information related to markers in a lineup, such as updating event markers, timeline points, or checkpoints in a project or media timeline.
Practical examples include:
- Changing the name of a marker to reflect updated status or description.
- Adjusting the date of a marker to correct scheduling errors or reflect new timelines.
Properties
| Name | Meaning |
|---|---|
| Marker Id | The unique numeric ID of the lineup marker to update (required). |
| Name | The new name for the marker. If provided, this will update the marker's display name. |
| Date | The new date for the marker in ISO8601 format (without time part). Updates the marker's date. |
Output
The node outputs JSON data representing the updated lineup marker object as returned by the API. This typically includes the marker's ID, updated name, updated date, and possibly other metadata fields reflecting the current state after the update.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential or OAuth2 token configured in n8n to authenticate requests to the external service managing lineup markers.
- The node uses a base URL constructed dynamically from credentials, indicating it interacts with a RESTful API endpoint.
- Proper network access to the API endpoint is necessary.
Troubleshooting
- Invalid Marker Id: If the specified marker ID does not exist, the API may return a "not found" error. Verify the marker ID before running the node.
- Invalid Date Format: The date must be in ISO8601 format without a time component (e.g.,
YYYY-MM-DD). Providing an incorrect format may cause validation errors. - Authentication Errors: Ensure that the API authentication credentials are correctly set up and have sufficient permissions to update markers.
- Empty Update Fields: If neither name nor date is provided, the API might reject the request or perform no changes. Always provide at least one field to update.
Links and References
- Refer to the external API documentation for lineup markers to understand the full schema and constraints on marker updates.
- ISO8601 date format specification: https://en.wikipedia.org/wiki/ISO_8601