Actions80
- 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
- Todos Actions
Overview
This node interacts with the Basecamp API to retrieve recordings of various types such as comments, documents, messages, and more. It is useful for automating workflows that require fetching specific recorded data from Basecamp projects, for example, gathering all active comments or archived documents within certain projects. Practical applications include generating reports, syncing Basecamp data with other tools, or monitoring project communications.
Properties
| Name | Meaning |
|---|---|
| Type | Type of recording to retrieve. Options: Comment, Document, Message, Question Answer, Schedule Entry, Todo, Todolist, Upload, Vault. |
| Bucket | Single or comma-separated list of project IDs (buckets) to filter recordings by. |
| Status | Status of the recordings to fetch. Options: Active, Archived, Trashed. |
| Sort | Field to sort the results by. Options: Created At, Updated At. |
| Direction | Sort direction. Options: Asc (ascending), Desc (descending). |
Output
The node outputs JSON data representing the recordings fetched from Basecamp according to the specified filters. Each item in the output corresponds to a recording object containing details such as its type, status, creation and update timestamps, and associated project information. The node does not output binary data.
Dependencies
- Requires an API authentication token credential configured in n8n to access the Basecamp API.
- Needs the Basecamp account ID to construct the API base URL dynamically.
- Relies on the Basecamp REST API endpoint
https://3.basecampapi.com/{basecampId}.
Troubleshooting
- Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect or empty project bucket IDs may result in no recordings returned.
- Using unsupported recording types or statuses might yield empty responses.
- Error messages:
- Authentication errors typically indicate invalid or expired API tokens; re-authenticate or update credentials.
- HTTP 404 or 400 errors suggest incorrect parameters like bucket IDs or type values; verify input correctness.
- Rate limiting errors from Basecamp API require waiting before retrying or adjusting request frequency.