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
Webhook → Get a Webhook
AI-generatedOverview
This node operation retrieves a specific webhook from a Basecamp project using the provided project ID (bucketId) and webhook ID. It is useful for scenarios where you need to fetch details about a particular webhook configured in a Basecamp project, such as for monitoring or managing webhook configurations.
Use Case Examples
- Fetch details of a webhook to verify its configuration.
- Retrieve webhook information to log or audit webhook events.
Properties
| Name | Meaning |
|---|---|
| Project ID | The ID of the project (bucket) used in the API endpoint path to specify which project the webhook belongs to. |
| Webhook ID | The ID of the webhook used in the API endpoint path to specify which webhook to retrieve. |
| Return Full Response | Whether to return the full HTTP response including status code, headers, and body instead of only the response body. |
| Request Options | Additional HTTP request options such as batching, SSL certificate validation, proxy settings, and timeout configuration. |
Output
JSON
id- The unique identifier of the retrieved webhook.projectId- The ID of the project (bucket) the webhook belongs to.url- The URL endpoint of the webhook.createdAt- Timestamp when the webhook was created.updatedAt- Timestamp when the webhook was last updated.events- List of events that trigger the webhook.
Dependencies
- Basecamp API access with OAuth2 credentials
Troubleshooting
- Ensure the provided Project ID and Webhook ID are correct and exist in the Basecamp account.
- Check that the OAuth2 credentials have sufficient permissions to access webhook data.
- If 'Return Full Response' is enabled, be prepared to handle the full HTTP response object instead of just the body.
- Verify network connectivity and proxy settings if requests fail or time out.
- If SSL certificate validation fails, consider enabling 'Ignore SSL Issues' only if safe to do so.