Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Teamleader

Teamleader integration for Flows360 workflows.

CategorySales And Crm
AuthenticationOAuth 2.0
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 24, 2026

Overview

Connect Teamleader with Flows360

Teamleader integration for Flows360 workflows.

Use the Teamleader connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 13 actions and 5 triggers.

Available actions

  • Create Contact
  • Update Contact
  • Create Company
  • Update Company
  • Link Contact to Company
  • Unlink Contact from Company
  • Create Deal
  • Update Deal
  • Plus 5 additional declared actions.

Available triggers

  • New Contact
  • New Company
  • New Deal
  • Deal Won
  • New Invoice

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Teamleader
  • Package: @activepieces/piece-teamleader@0.2.0
  • Exact artifact digest: sha256:5b524e81810cecbbc99f6fae862c930025f6ac81ccc37de510bed2a914355b2f
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

OAUTH2. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Contact (create_contact), Create a new contact record Classification: read.
  • Update Contact (update_contact), Modify existing contact data Classification: read.
  • Create Company (create_company), Add a new company record Classification: read.
  • Update Company (update_company), Modify company information Classification: read.
  • Link Contact to Company (link_contact_to_company), Associate a contact with a company Classification: read.
  • Unlink Contact from Company (unlink_contact_from_company), Remove the association between contact and company Classification: read.
  • Create Deal (create_deal), Create a new deal/opportunity Classification: read.
  • Update Deal (update_deal), Modify deal properties Classification: read.
  • Search Companies (search_companies), List or filter companies Classification: read.
  • Search Contacts (search_contacts), List or filter contacts Classification: read.
  • Search Deals (search_deals), List or filter deals Classification: read.
  • Search Invoices (search_invoices), List or filter invoices Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Contact, webhook.
  • New Company, webhook.
  • New Deal, webhook.
  • Deal Won, webhook.
  • New Invoice, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

AuthenticationOAuth 2.0
Supported objects18
Supported actionsNot published
Triggers5

Authentication

Authentication method: OAuth 2.0

Authentication profiles

connection · oauth2

Supported objects

ObjectReadWriteNotes
Create Contact Yes No Create a new contact record
Update Contact Yes No Modify existing contact data
Create Company Yes No Add a new company record
Update Company Yes No Modify company information
Link Contact to Company Yes No Associate a contact with a company
Unlink Contact from Company Yes No Remove the association between contact and company
Create Deal Yes No Create a new deal/opportunity
Update Deal Yes No Modify deal properties
Search Companies Yes No List or filter companies
Search Contacts Yes No List or filter contacts
Search Deals Yes No List or filter deals
Search Invoices Yes No List or filter invoices
Custom API Call Yes No Make a custom API call to a specific endpoint
New Contact Yes No webhook trigger declared by the pinned package.
New Company Yes No webhook trigger declared by the pinned package.
New Deal Yes No webhook trigger declared by the pinned package.
Deal Won Yes No webhook trigger declared by the pinned package.
New Invoice Yes No webhook trigger declared by the pinned package.

Triggers

New Contact · Webhook

Triggers when a new contact is created

New Company · Webhook

Triggers when a new company is created

New Deal · Webhook

Triggers when a new deal is created

Deal Won · Webhook

Triggers when a deal is won/accepted

New Invoice · Webhook

Triggers when a new invoice is drafted

Setup

Setup

  1. Add the Teamleader connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-teamleader@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 13 actions and 5 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Teamleader connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-teamleader@0.2.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com