Overview
This node acts as a webhook trigger for Teamleader events. It starts an n8n workflow whenever specified events occur in the Teamleader platform, such as creation, update, or deletion of various entities like calls, companies, contacts, deals, invoices, meetings, projects, tasks, tickets, and more.
Common scenarios where this node is beneficial include:
- Automating follow-up actions when a new deal is created or won.
- Syncing contact or company updates to other systems.
- Triggering notifications or workflows when invoices are sent or payments are registered.
- Managing project lifecycle events automatically.
- Tracking time entries or ticket status changes.
For example, you could use this node to start a workflow that sends a Slack notification every time a new meeting is created or a task is completed in Teamleader.
Properties
| Name | Meaning |
|---|---|
| Event | The Teamleader event(s) that will trigger the webhook. Multiple events can be selected from options including: Account Deactivated, Call Added, Company Updated, Contact Deleted, Deal Created, Invoice Sent, Meeting Completed, Project Deleted, Task Updated, Ticket Closed, Time Tracking Added, User Deactivated, and many others. |
Output
The node outputs the JSON payload received from the Teamleader webhook as the json field in the output data. This payload contains detailed information about the event that triggered the webhook, such as the entity involved and its current state.
No binary data output is produced by this node.
Dependencies
- Requires an API authentication token configured via OAuth2 credentials for Teamleader.
- Needs internet access to communicate with Teamleader's API endpoints at
https://api.focus.teamleader.eu. - The node registers and manages webhooks on Teamleader using these API calls.
Troubleshooting
- Webhook registration failure: If the node cannot register the webhook, check that the OAuth2 credentials are valid and have sufficient permissions.
- Webhook not triggering: Ensure the selected events match those configured in Teamleader and that the webhook URL is accessible publicly.
- API errors: Errors from Teamleader API calls will be thrown as node errors. Verify network connectivity and credential validity.
- Multiple events selection: Selecting no events or an empty array will result in no triggers; ensure at least one event is selected.
Links and References
- Teamleader Developer Documentation
- Teamleader API base URL:
https://api.focus.teamleader.eu