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 its unique identifier. It allows users to modify properties such as the marker's name and date. This is useful in scenarios where lineup markers represent scheduled events, milestones, or checkpoints that need to be kept current within a system managing timelines or schedules.
For example, if you have a project timeline with various markers indicating key dates, this operation lets you update the name or date of a specific marker without creating a new one.
Properties
| Name | Meaning |
|---|---|
| Marker Id | The unique numeric ID of the lineup marker to update. This is required to identify which marker to modify. |
| Name | The new name for the lineup marker. |
| Date | The new date for the lineup marker, formatted as an ISO8601 string without the time part (e.g., "2024-06-01"). |
Output
The node outputs JSON data representing the updated lineup marker. This typically includes the marker's ID, updated name, updated date, and possibly other metadata returned from the API after the update operation.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the external service managing lineup markers.
- Needs appropriate API authentication credentials configured in n8n (such as an API key or OAuth2 token).
- The base URL for API requests is dynamically constructed using credential information.
Troubleshooting
- Invalid Marker Id: If the provided Marker Id does not exist, the API will likely return an error indicating the marker was not found. Verify the ID before running the update.
- Date Format Issues: Ensure the date is in ISO8601 format without time (YYYY-MM-DD). Incorrect formatting may cause validation errors.
- Authentication Errors: Missing or invalid API credentials will prevent the request from succeeding. Confirm credentials are correctly set up.
- Empty Update Fields: If neither Name nor Date is provided, the update request might fail or have no effect. Provide at least one field to update.
Links and References
- Refer to the external API documentation for lineup markers to understand all possible fields and constraints.
- ISO8601 date format reference: https://en.wikipedia.org/wiki/ISO_8601