Kommo Make integrationAutomate Kommo with Make.

Adds a new company to Kommo from data that arrives in the scenario, so accounts exist in your CRM without anyone typing them in. The result is a company record you can later tie to contacts and leads.

Turns a person coming from another app into a Kommo contact, ready for your sales team to call or email. You map the details from the previous module and Kommo stores them as a new record.

Opens a new lead in Kommo, which puts a potential deal in front of your sales team without manual entry. It is the module that turns an inquiry from elsewhere into something your pipeline tracks.

Writes a note in Kommo, so the context gathered in another tool appears right where your reps look before they call. Think of it as a message left on the record for whoever opens it next.

Puts a to-do in Kommo for a teammate, so the follow-up is booked the instant something happens instead of relying on memory. The rep sees it in their task list like any task they created themselves.

Fetches one specific Kommo company so later modules can use its details, for example to fill an invoice or a message. You need to know which company you want; this module does not search.

Reads a single contact from Kommo and hands its details to the next module, which saves you from copying a phone number or an email address by hand. It works on one known person, not a list.

Pulls the full picture of one lead out of Kommo, so a later step can decide what to do based on it. That turns a bare reference into data you can map anywhere in the scenario.

Retrieves one product from your Kommo catalog, which lets you reuse its details in a quote, a message or another app. Make asks for the list ID the product belongs to, then the product you want.

Loads one Kommo task and exposes its details to the rest of the scenario, handy when you need to report on work that was promised to a client. It reads; it changes nothing.

Connects Kommo records to each other, one link or several at once, so a contact, a company and a lead stop floating on their own. Your team then sees who belongs to which deal without cross-checking.

Reaches any endpoint of the Kommo API from your scenario, reusing the connection you already made. This is the escape hatch when none of the ready-made Kommo modules does exactly what you need.

Removes links between Kommo records, one or several in a single run, so a contact no longer shows up on a deal it has left. It cleans the relationships without deleting the records themselves.

Changes the details of an existing Kommo company, so an account stays accurate when information moves in another tool. You point it at one company and map only the values that should change.

Refreshes a Kommo contact with new data, which keeps phone numbers and emails right without a rep chasing them. It edits the person you target and leaves everyone else alone.

Edits an existing lead in Kommo so the deal reflects what just happened outside the CRM. Your pipeline stays truthful without someone reopening every card by hand.

Rewrites a note that already sits in Kommo, useful when the status you logged earlier has moved on. Readers of the record then see the current version rather than a stack of outdated comments.

Modifies a Kommo task that exists already, so a reminder follows the real state of the work. Instead of creating a fresh task each time, you adjust the one your rep is watching.

Looks up companies in Kommo, or lists all of them, and sends each match to the next module as its own bundle. It answers the question “do we already have this account?” before you act.

Finds contacts in Kommo, or returns the whole list, so your scenario can tell a known person from a newcomer. Each match travels on as a separate bundle to the modules that follow.

Searches the customers stored in Kommo, or lists them all, which is where you go when you care about people who already buy from you rather than prospects. Every result becomes one bundle.

Returns the Kommo leads that match your query, or all of them, so you can act on a slice of your pipeline in one scenario. Each lead continues on its own to the next module.

Gathers notes from Kommo, filtered or all at once, to reuse what your team wrote in a report, a document or another app. It surfaces context that would otherwise stay buried in the CRM.

Lists the products of one Kommo catalog list, or searches inside it, so a scenario can reuse your products without you exporting the catalog. Make asks for the list ID first.

Pulls tasks out of Kommo, matching a query or not, so you can see and act on the follow-ups your team has open. Each task becomes a separate bundle for the steps that come after.