Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Kommo

Kommo integration for Flows360 workflows.

CategoryCommunication
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Kommo with Flows360

Kommo integration for Flows360 workflows.

Use the Kommo 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 8 actions and 4 triggers.

Available actions

  • Find Lead
  • Update Contact
  • Create New Lead
  • Update Lead
  • Create New Contact
  • Find Contact
  • Find Company
  • Custom API Call

Available triggers

  • Lead Status Changed
  • New Contact Added
  • New Lead Created
  • New Task Created

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: Kommo
  • Package: @activepieces/piece-kommo@0.2.0
  • Exact artifact digest: sha256:6552732b091a8b439cb9e307330471a91ff8d36ce2fd652021d717eef1c1768e
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

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

Action contracts

  • Find Lead (find_lead), Finds an existing lead. Classification: read.
  • Update Contact (update_contact), Updates an existing contact. Classification: read.
  • Create New Lead (create_lead), Creates a new lead. Classification: read.
  • Update Lead (update_lead), Update existing lead info. Classification: read.
  • Create New Contact (create_contact), Add a new contact. Classification: read.
  • Find Contact (find_contact), Finds an existing contact. Classification: read.
  • Find Company (find_company), Find an existing company. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • Lead Status Changed, webhook.
  • New Contact Added, webhook.
  • New Lead Created, webhook.
  • New Task Created, webhook.

Verification

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

Capability summary

Authenticationcustom
Supported objects12
Supported actions8
Triggers4

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Subdomain Required · protected credential
  • Token Required · protected credential

Supported objects

ObjectReadWriteNotes
Find Lead Yes No Finds an existing lead.
Update Contact Yes No Updates an existing contact.
Create New Lead Yes No Creates a new lead.
Update Lead Yes No Update existing lead info.
Create New Contact Yes No Add a new contact.
Find Contact Yes No Finds an existing contact.
Find Company Yes No Find an existing company.
Custom API Call Yes No Make a custom API call to a specific endpoint
Lead Status Changed Yes No webhook trigger declared by the pinned package.
New Contact Added Yes No webhook trigger declared by the pinned package.
New Lead Created Yes No webhook trigger declared by the pinned package.
New Task Created Yes No webhook trigger declared by the pinned package.

Supported actions

Find Lead · Read

Finds an existing lead.

find_lead · Risk: low · Retry: safe

Inputs

  • query · string · Required, Search query (Searches through the filled fields of the lead).
Update Contact · Read

Updates an existing contact.

update_contact · Risk: low · Retry: safe

Inputs

  • contactId · string · Optional
  • name · string · Optional
  • first_name · string · Optional
  • last_name · string · Optional
  • email · string · Optional
  • phone · string · Optional
  • responsible_user_id · string · Optional
  • tags_to_add · array · Optional, List of tag names or IDs to add.
  • tags_to_delete · array · Optional, List of tag names or IDs to remove.
Create New Lead · Read

Creates a new lead.

create_lead · Risk: low · Retry: safe

Inputs

  • name · string · Required
  • price · number · Optional
  • pipelineId · string · Required
  • statusId · string · Required
  • responsible_user_id · string · Optional
  • loss_reason_id · string · Optional
  • tags_to_add · array · Optional, List of tags to add.
Update Lead · Read

Update existing lead info.

update_lead · Risk: low · Retry: safe

Inputs

  • leadId · string · Required
  • name · string · Optional
  • price · number · Optional
  • pipelineId · string · Optional
  • statusId · string · Optional
  • responsible_user_id · string · Optional
  • loss_reason_id · string · Optional
  • tags_to_add · array · Optional
  • tags_to_delete · array · Optional
Create New Contact · Read

Add a new contact.

create_contact · Risk: low · Retry: safe

Inputs

  • name · string · Required
  • first_name · string · Optional
  • last_name · string · Optional
  • email · string · Optional
  • phone · string · Optional
  • responsible_user_id · string · Optional
  • tags_to_add · array · Optional
Find Contact · Read

Finds an existing contact.

find_contact · Risk: low · Retry: safe

Inputs

  • query · string · Required, Search query (Searches through the filled fields of the contact).
Find Company · Read

Find an existing company.

find_company · Risk: low · Retry: safe

Inputs

  • query · string · Required, Search query (Searches through the filled fields of the company).
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

Lead Status Changed · Webhook

Triggers when a lead status is changed.

New Contact Added · Webhook

Triggers when a new contact is added.

New Lead Created · Webhook

Triggers when a new lead is created.

New Task Created · Webhook

Triggered when a new task is created.

Setup

Setup

  1. Add the Kommo 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:
  • Subdomain (subdomain), required; stored as a sensitive connection value.
  • Token (apiToken), required; stored as a sensitive connection value.
  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-kommo@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 8 actions and 4 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 Kommo 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-kommo@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