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 operation allows you to create a webhook in Basecamp for a specific bucket. When certain events (types) occur within that bucket, Basecamp will send an HTTP POST request to the specified payload URL. This is useful for integrating Basecamp with other systems or automating workflows based on project updates.
Common scenarios include:
- Triggering notifications or actions in external systems when new messages or to-dos are added to a Basecamp project.
- Synchronizing data between Basecamp and other project management tools.
- Automating reporting or logging by capturing real-time event data from Basecamp.
Example: You want to receive a notification in your app whenever a new comment is posted in a particular Basecamp bucket. You create a webhook with the bucket ID, specify the URL of your app’s endpoint, and select the event types to listen for.
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 which event types should 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 target URL.
If the node supports binary data output, it would represent any file or media content returned by the API, but in this case, the output is purely JSON.
Dependencies
- Requires an API authentication token credential for Basecamp (OAuth2 or similar).
- Needs network access to Basecamp’s API endpoints.
- The node uses a bundled OpenAPI specification to define properties and requests.
Troubleshooting
- Invalid Bucket Id: If the bucket ID does not exist or is incorrect, the API will return an error. Verify the bucket ID before creating the webhook.
- Invalid Payload URL: The URL must be HTTPS and publicly accessible. Using HTTP or a local URL will cause failures.
- Permission Issues: Ensure the API credentials have permission to create webhooks on the specified bucket.
- Malformed Types JSON: The "Types" property expects a valid JSON array. Invalid JSON syntax will cause errors.
- Network Errors: Check connectivity to Basecamp API endpoints if requests time out or fail.