Actions119
- 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
- Schedule Actions
- Schedule Entry Actions
- Template Actions
- Todo Actions
- Todolist Actions
- Todolist Group Actions
- Todoset Actions
- Upload Actions
- Vault Actions
- Webhook Actions
Overview
This node integrates with the Basecamp API to retrieve webhook information for a specified project (referred to as a "bucket" in Basecamp terminology). The "Get Webhooks" operation fetches all webhooks associated with a given project ID. This is useful for scenarios where you want to monitor or manage webhook subscriptions programmatically, such as syncing webhook data with other systems, auditing webhook configurations, or triggering workflows based on webhook events.
Practical examples:
- Automatically listing all webhooks configured for a project to verify their status.
- Fetching webhook details to update or audit webhook URLs and event subscriptions.
- Integrating webhook data into dashboards or monitoring tools.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project (bucket) for which to retrieve webhooks. Used in the API endpoint path. |
| Return All Results | Boolean option to either return all webhook results or limit the output to a default maximum. |
| Return Full Response | Boolean option to return the entire HTTP response including status code, headers, and body instead of just the response body. |
Output
The node outputs JSON data representing the list of webhooks retrieved from the Basecamp API for the specified project. The structure typically includes webhook identifiers, URLs, subscribed events, and metadata about each webhook.
If "Return Full Response" is enabled, the output will include the full HTTP response object containing status code, headers, and body.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Basecamp API using OAuth2 authentication with appropriate permissions to access project webhooks.
- The node expects the Basecamp account ID to be configured in credentials to construct the API base URL.
- No additional external dependencies beyond the Basecamp API and n8n's OAuth2 credential setup.
Troubleshooting
Common issues:
- Invalid or missing Project ID: Ensure the Project ID corresponds to an existing project in Basecamp.
- Authentication errors: Verify that the OAuth2 credentials are valid and have sufficient scopes to read webhooks.
- Pagination handling: If many webhooks exist, ensure "Return All Results" is enabled to paginate through all pages; otherwise, only a limited set will be returned.
Error messages:
- Unauthorized or 401 errors indicate invalid or expired credentials; re-authenticate the Basecamp connection.
- 404 Not Found may indicate the project ID does not exist or the user lacks access rights.
- Rate limiting errors require waiting before retrying or adjusting request frequency.