Actions68
- Recordings Actions
- Card Tables Actions
- Forwards Actions
- Events 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
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 names, such as scheduling events, milestones, or checkpoints within a timeline or project plan.
For example, you might use this node to create a marker named "Project Kickoff" on a particular date to highlight the start of a project phase.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the lineup marker to create. This is a required string that identifies the marker. |
| Date | The date associated with the marker, formatted as an ISO8601 string without the time part (e.g., "2024-06-01"). This is a required field 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 any other metadata returned by the API after creation.
No binary data output is involved.
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 headers is necessary for successful communication.
Troubleshooting
- Missing Required Fields: If either the "Name" or "Date" property 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., "YYYY-MM-DD"). Providing an incorrect format may cause the API to reject the request.
- Authentication Errors: Failure to provide valid credentials or expired tokens will result in authorization errors. Verify that the API key or authentication method is correctly set up.
- API Endpoint Issues: Network problems or incorrect base URL configurations can lead to connection failures. Check network connectivity and endpoint settings.
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 responses.