Actions80
- Todos Actions
- 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
Overview
This node operation allows you to create a webhook in Basecamp by specifying a target bucket, a payload URL, and the event types that should trigger the webhook. When an event matching one of the specified types occurs in the selected bucket, Basecamp will send an HTTP request to the provided payload URL with details about the event.
Common scenarios for this node include:
- Automating workflows by triggering external services when changes happen in a Basecamp project.
- Integrating Basecamp events with other applications such as notification systems, analytics platforms, or custom dashboards.
- Monitoring specific activities within a Basecamp bucket and reacting programmatically.
For example, you could use this node to create a webhook that notifies your team chat app whenever a new message is posted in a particular Basecamp 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 | A JSON array specifying the event types that will trigger the webhook calls. |
Output
The node outputs JSON data representing the response from the Basecamp API after creating the webhook. This typically includes details about the newly created webhook such as its ID, associated bucket, subscribed event types, and the configured payload URL.
No binary data output is involved in this operation.
Dependencies
- Requires an active Basecamp account and appropriate permissions to create webhooks on the specified bucket.
- Needs an API authentication token (OAuth2 or similar) configured in n8n credentials to authorize requests to the Basecamp API.
- The node uses the Basecamp API endpoint constructed dynamically based on the authenticated user's Basecamp ID.
Troubleshooting
- Invalid Bucket Id: If the bucket ID does not exist or the user lacks access, the API will return an error. Verify the bucket ID and permissions.
- Invalid Payload URL: The payload URL must be a valid HTTPS URL accessible by Basecamp. Ensure the URL is correct and publicly reachable.
- Malformed Types JSON: The "Types" property expects a valid JSON array. Invalid JSON syntax will cause errors. Use proper JSON formatting.
- Authentication Errors: Missing or invalid API credentials will prevent webhook creation. Confirm that the API key/token is correctly set up in n8n.
- API Rate Limits: Excessive webhook creation attempts may hit Basecamp API rate limits. Implement retry logic or reduce frequency.
Links and References
- Basecamp API Documentation - Webhooks
- n8n Documentation - Creating Webhooks (general webhook usage)