Actions76
- Campfire Actions
- Card Table Actions
- Chatbot Actions
- Client Approval Actions
- Client Correspondence Actions
- Client Reply Actions
- Client Visibility Actions
- Comment Actions
- Document Actions
- Event Actions
- Forward Actions
- Inbox Actions
- Inbox Reply Actions
- Lineup Marker Actions
- Message Actions
- Message Board Actions
- Message Type Actions
- Person Actions
- Project Actions
- Question Actions
- Question Answer Actions
- Questionnaire Actions
- Recording Actions
Overview
The "Update a Marker" operation for the Lineup Marker resource allows users to modify an existing marker's details in Basecamp. This node is useful when you need to update specific attributes of a marker, such as its date or name, without creating a new marker. Common scenarios include adjusting event markers on a project timeline or correcting marker information after initial creation.
For example, if a project milestone date changes, you can use this node to update the marker's date accordingly. Similarly, if the marker's name needs correction or clarification, this operation facilitates that update seamlessly.
Properties
Name | Meaning |
---|---|
Marker ID | The unique identifier of the marker to update. Used in the API endpoint path. |
Marker Date | The date for the marker in ISO8601 format (YYYY-MM-DD). Leave empty to keep the existing date. |
Marker Fields - Name | The name of the marker to update. |
Return Full Response | Whether to return the full HTTP response (status code, headers, body) instead of only the response body. |
Output
The node outputs JSON data representing the updated marker object returned by the Basecamp API. If "Return Full Response" is enabled, the output includes the entire HTTP response with status code, headers, and body; otherwise, it returns only the response body containing the updated marker details.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Basecamp API using OAuth2 authentication.
- The node expects the Basecamp account ID to be configured in credentials to construct the API base URL.
- Proper permissions to update lineup markers in the Basecamp project are necessary.
Troubleshooting
- Invalid Marker ID: If the provided Marker ID does not exist or is incorrect, the API will return an error indicating the marker was not found. Verify the Marker ID before running the node.
- Date Format Issues: The Marker Date must be in ISO8601 format (YYYY-MM-DD). Providing an invalid date format may cause the request to fail.
- Insufficient Permissions: Ensure the API credentials have permission to update markers in the target Basecamp project.
- Empty Update Fields: If no fields are provided to update (e.g., both date and name are empty), the API might reject the request or make no changes. Provide at least one field to update.
- API Rate Limits: Frequent updates may hit Basecamp API rate limits; handle errors accordingly.