Actions67
- User Actions
- Teams Actions
- Custom Fields Actions
- Tickets Actions
- Ticket Status Actions
- Deals Actions
- Webhooks Actions
- Contacts Actions
- Companies Actions
- Bussiness Types Actions
- Tags Actions
- Deal Phases Actions
- Invoices Actions
- Subscriptions Actions
- Products Actions
- Projects Actions
- Tasks Actions
- Files Actions
- Notes Actions
Webhooks → Register
AI-generatedOverview
This node operation registers a new webhook URL with the Teamleader API to listen for specific event types. It is useful for automating workflows that need to respond to real-time events such as account changes, call updates, deal status changes, invoice updates, and more. For example, a user can register a webhook URL to receive notifications when a deal is won or a ticket is created, enabling immediate processing or alerting within their automation.
Use Case Examples
- Register a webhook URL to listen for 'deal.created' and 'ticket.created' events to automate follow-up actions when new deals or tickets are created.
- Set up a webhook to monitor 'invoice.paymentRegistered' events to trigger accounting workflows upon invoice payments.
Properties
| Name | Meaning |
|---|---|
| URL | The URL of the webhook to register, where event notifications will be sent. |
| Types | The types of events to listen to for this webhook registration, such as 'deal.created', 'ticket.updated', or 'user.deactivated'. Multiple event types can be selected. |
Output
JSON
id- The unique identifier of the registered webhook.url- The URL of the registered webhook.types- The list of event types the webhook is registered to listen for.
Dependencies
- Teamleader API with OAuth2 authentication
Troubleshooting
- Ensure the webhook URL is accessible and publicly reachable to receive event notifications.
- Verify that the selected event types are valid and supported by the Teamleader API.
- Check OAuth2 credentials and permissions to confirm the node can register webhooks successfully.
- Common errors include invalid URL format, unauthorized access due to invalid credentials, or unsupported event types. Resolving these involves correcting the URL, updating credentials, or selecting valid event types.
Links
- Teamleader API Documentation - Official documentation for the Teamleader API including webhook registration details.