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 details about a specific webhook configured in a Basecamp project. It is useful when you want to programmatically fetch information about a webhook, such as its configuration or status, without manually checking the Basecamp interface. For example, you might use this node to verify that a webhook exists before attempting to update or delete it, or to audit webhook settings across multiple projects.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The numeric identifier of the Basecamp project (bucket) where the webhook is registered. This specifies the scope for the webhook retrieval. |
| Webhook Id | The numeric identifier of the specific webhook to retrieve within the given bucket. |
Output
The node outputs JSON data representing the webhook's details as returned by the Basecamp API. This typically includes properties such as the webhook's URL, events it listens to, creation date, and other metadata. The output does not include binary data.
Example structure of the output JSON might look like:
{
"id": 123456,
"url": "https://example.com/webhook",
"events": ["event1", "event2"],
"created_at": "2023-01-01T12:00:00Z",
...
}
Dependencies
- Requires an API authentication token credential for Basecamp (OAuth2 or similar).
- The node depends on the Basecamp API being accessible and the provided credentials having permission to read webhook information.
- No additional environment variables are required beyond the API credentials.
Troubleshooting
- Invalid Bucket Id or Webhook Id: If either ID is incorrect or does not exist, the API will return an error indicating the resource was not found. Verify the IDs are correct.
- Authentication Errors: If the API credentials are missing, expired, or invalid, the node will fail with an authentication error. Ensure the API key/token is valid and has sufficient permissions.
- Network Issues: Connectivity problems can cause timeouts or failures. Check network access to the Basecamp API endpoint.
- Permission Denied: If the authenticated user does not have access to the specified bucket or webhook, the API will reject the request. Confirm user permissions.