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
This node interacts with the Basecamp API to manage "Lineup Markers," specifically allowing users to delete a marker by its ID. It is useful in scenarios where you need to programmatically remove markers from a lineup within Basecamp projects, such as cleaning up outdated or incorrect markers.
For example, if you have a workflow that tracks project milestones or events marked by lineup markers, and one of these markers becomes irrelevant or was created by mistake, this node can be used to delete it automatically based on its ID.
Properties
| Name | Meaning |
|---|---|
| Marker ID | The unique numeric identifier of the marker to delete. This is required and used in the API endpoint path. |
| Return Full Response | Boolean option to return the full HTTP response including status code, headers, and body instead of only the response body. |
Output
The node outputs JSON data representing the response from the Basecamp API after attempting to delete the specified lineup marker. If the deletion is successful, the output typically contains confirmation details or an empty object depending on the API's behavior.
If the "Return Full Response" property is enabled, the output will include the entire HTTP response, which consists of:
- Status code (e.g., 200 for success)
- Headers returned by the API
- Body content (usually empty or confirmation message)
No binary data is involved in this operation.
Dependencies
- Requires an active connection to the Basecamp API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The base URL for API calls is constructed using the user's Basecamp account ID.
Troubleshooting
- Invalid Marker ID: If the provided Marker ID does not exist or is incorrect, the API may return a 404 Not Found error. Verify the Marker ID before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key/token is correctly set up in n8n.
- Permission Issues: The authenticated user must have permission to delete markers in the relevant Basecamp project; otherwise, the API will reject the request.
- Network Issues: Connectivity problems can cause timeouts or failed requests. Check network access and Basecamp service status.
Links and References
- Basecamp API Documentation – Official API docs for understanding endpoints and responses.
- n8n Documentation – For general guidance on setting up credentials and using HTTP request nodes.