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 creates a new lineup marker by sending the specified name and date to an external service. It is useful in scenarios where you need to mark or tag specific dates with meaningful labels, such as scheduling events, milestones, or checkpoints within a timeline or project plan.
For example, you might use this node to create markers for important deadlines, product launch dates, or team meeting days, helping to organize and visualize key moments in your workflow.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the lineup marker. This is a required string that identifies the marker. |
| Date | The date of the lineup marker in ISO8601 format (without the time part). This is a required string specifying when the marker applies. |
Output
The node outputs JSON data representing the created lineup marker. This typically includes details such as the marker's unique identifier, name, date, and possibly other metadata returned by the API after creation.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to authorize requests to the external service managing lineup markers.
- The node sends HTTP requests with JSON payloads containing the marker's name and date.
- Proper configuration of the base URL and authentication credentials is necessary for successful communication.
Troubleshooting
- Missing Required Fields: If "Name" or "Date" is not provided, the node will likely throw an error indicating missing required parameters. Ensure both fields are filled correctly.
- Invalid Date Format: The "Date" must be in ISO8601 format without the time part (e.g.,
2024-06-01). Providing an incorrect format may cause the API to reject the request. - Authentication Errors: If the API key or authentication token is invalid or missing, the node will fail to connect. Verify that credentials are properly set up in n8n.
- API Endpoint Issues: Network problems or incorrect base URL configurations can lead to request failures. Check connectivity and endpoint correctness.
Links and References
- ISO 8601 Date Format
- Refer to the external service’s API documentation for detailed information on lineup marker creation endpoints and expected request/response formats.