Teamleader currently provides 5 triggers that can start a workflow and 13 actions a workflow can run. Use those building blocks to keep account, contact, and deal context attached to the work around it.
New Contact
Triggers when a new contact is created
New Company
Triggers when a new company is created
New Deal
Triggers when a new deal is created
Deal Won
Triggers when a deal is won/accepted
New Invoice
Triggers when a new invoice is drafted
Create Contact
Create a new contact record
Update Contact
Modify existing contact data
Create Company
Add a new company record
Update Company
Modify company information
Link Contact to Company
Associate a contact with a company
Unlink Contact from Company
Remove the association between contact and company
Create Deal
Create a new deal/opportunity
Update Deal
Modify deal properties
Search Companies
List or filter companies
Search Contacts
List or filter contacts
Search Deals
List or filter deals
Search Invoices
List or filter invoices
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Teamleader event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Contact
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Teamleader action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Create Contact
Combine Teamleader with another integration and Coherence records to keep account, contact, and deal context attached to the work around it.
Starts with
New Contact
Finishes with
Create Contact, then preserve the outcome in Coherence
The exact authentication fields depend on Teamleader. The workflow structure stays straightforward:
Authorize the Teamleader account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Teamleader or provide a complementary trigger or action.
Teamleader currently provides 5 triggers that can start a workflow and 13 actions a workflow can run. Use those building blocks to keep account, contact, and deal context attached to the work around it.
Teamleader currently lists 5 triggers and 13 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Teamleader triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
