Basecamp icon

Basecamp

Interact with the Basecamp API
Join our community

Actions68

Overview

This node operation updates an existing webhook in the Basecamp service. It allows users to modify the webhook's target URL, specify which event types trigger the webhook, and toggle its active status. This is useful for maintaining or changing webhook configurations without deleting and recreating them, such as updating the callback URL after a server migration or adjusting which events should notify your application.

Practical examples:

  • Changing the payload URL to a new endpoint after infrastructure changes.
  • Adding or removing event types that trigger the webhook notifications.
  • Temporarily disabling a webhook by setting it inactive without deleting it.

Properties

Name Meaning
Bucket Id Numeric identifier of the Basecamp bucket (project) where the webhook exists.
Webhook Id Numeric identifier of the specific webhook to update within the given bucket.
Payload Url HTTPS URL that Basecamp will call when the webhook triggers; the destination endpoint.
Types JSON array specifying which event types will trigger the webhook calls.
Active Boolean flag indicating whether the webhook is currently active and should match events.

Output

The node outputs JSON data representing the updated webhook object returned from the Basecamp API. This typically includes details such as the webhook ID, associated bucket, configured URL, event types, and active status. The output can be used downstream to confirm the update or for logging purposes.

No binary data output is involved.

Dependencies

  • Requires an API authentication token credential for Basecamp with appropriate permissions.
  • The node uses the Basecamp API endpoint constructed dynamically using the user's Basecamp account ID.
  • Network access to Basecamp's API (https://3.basecampapi.com/) must be available.

Troubleshooting

  • Invalid Bucket or Webhook Id: If the provided IDs do not exist or are incorrect, the API will return an error. Verify the IDs before running the node.
  • Invalid Payload URL: The URL must be HTTPS and reachable. Invalid URLs may cause the update to fail.
  • Malformed Types JSON: The Types property expects a valid JSON array. Improper formatting will cause parsing errors.
  • Inactive Webhook Not Updating: Ensure the Active flag is set correctly if you want the webhook to respond to events.
  • Authentication Errors: Check that the API key or OAuth token is valid and has sufficient permissions.

Links and References

Discussion