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 allows you to create a webhook in Basecamp by specifying the target bucket, the URL that Basecamp should call when the webhook is triggered, and the types of events that will trigger the webhook. It is useful for automating workflows that depend on real-time notifications from Basecamp, such as syncing project updates, triggering alerts, or integrating with other systems.
For example, you can use this node to set up a webhook that notifies your application whenever a new message is posted in a specific Basecamp project bucket.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The numeric identifier of the Basecamp bucket where the webhook will be created. |
| Payload Url | The HTTPS URL that Basecamp will call when the webhook is triggered. |
| Types | An array of event types that will trigger the webhook calls. Specify which events to listen for. |
Output
The node outputs JSON data representing the created webhook object returned by the Basecamp API. This typically includes details such as the webhook ID, associated bucket, subscribed event types, and the payload URL.
No binary data output is produced by this node.
Dependencies
- Requires an API authentication token credential for Basecamp (OAuth2 or similar).
- The node uses the Basecamp API endpoint constructed with the Basecamp account ID.
- Network access to Basecamp's API and the specified payload URL must be available.
Troubleshooting
- Invalid Bucket Id: If the bucket ID does not exist or is incorrect, the API will return an error. Verify the bucket ID is correct.
- Invalid Payload URL: The payload URL must be a valid HTTPS URL accessible by Basecamp. Ensure it is correctly formatted and publicly reachable.
- Insufficient Permissions: The API credentials used must have permission to create webhooks in the specified bucket.
- Malformed Types Array: The "Types" property expects a JSON array. Invalid JSON or unsupported event types may cause errors.
- Network Issues: Connectivity problems between n8n and Basecamp or the payload URL endpoint can cause failures.
Links and References
- Basecamp API Documentation - Webhooks
- Basecamp Developer Portal
- n8n Documentation - Creating Webhooks (general webhook usage)