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 updates an existing lineup marker by modifying its properties such as name and date. It is useful in scenarios where you need to maintain or correct metadata associated with specific markers in a lineup, for example, updating event markers on a schedule or timeline after changes occur.
Practical examples include:
- Changing the name of a marker to reflect updated event details.
- Adjusting the date of a marker to correct scheduling errors or reflect rescheduling.
Properties
| Name | Meaning |
|---|---|
| Marker Id | The unique identifier (ID) of the lineup marker that you want to update. |
| Name | The new name to assign to the marker. |
| Date | The new date for the marker, formatted as an ISO8601 string without the time component. |
Output
The output contains a JSON object representing the updated lineup marker. This typically includes the marker's ID, updated name, 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 API key credential for authentication with the external service managing lineup markers.
- The node uses HTTP requests to communicate with the Basecamp API endpoint configured with the appropriate base URL and headers.
- Proper configuration of credentials and permissions to update lineup markers is necessary.
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 Marker Id before running the update.
- Invalid Date Format: The date must be in ISO8601 format without the time part (e.g., "2024-06-01"). Providing an incorrectly formatted date may cause the request to fail.
- Authentication Errors: Ensure that the API key or OAuth token is valid and has sufficient permissions to perform update operations.
- Empty Update Fields: If no fields (name or date) are provided to update, the operation might result in no changes or an error. Always provide at least one field to update.
Links and References
- Basecamp API Documentation (for general API usage and endpoints)
- ISO 8601 Date Format (for correct date formatting)