How to connect Facebook Messenger and Kommo
Create a New Scenario to Connect Facebook Messenger and Kommo
In the workspace, click the “Create New Scenario” button.

Add the First Step
Add the first node – a trigger that will initiate the scenario when it receives the required event. Triggers can be scheduled, called by a Facebook Messenger, triggered by another scenario, or executed manually (for testing purposes). In most cases, Facebook Messenger or Kommo will be your first step. To do this, click "Choose an app," find Facebook Messenger or Kommo, and select the appropriate trigger to start the scenario.

Add the Facebook Messenger Node
Select the Facebook Messenger node from the app selection panel on the right.


Facebook Messenger

Configure the Facebook Messenger
Click on the Facebook Messenger node to configure it. You can modify the Facebook Messenger URL and choose between DEV and PROD versions. You can also copy it for use in further automations.
Add the Kommo Node
Next, click the plus (+) icon on the Facebook Messenger node, select Kommo from the list of available apps, and choose the action you need from the list of nodes within Kommo.


Facebook Messenger
⚙
Kommo

Authenticate Kommo
Now, click the Kommo node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Kommo settings. Authentication allows you to use Kommo through Latenode.
Configure the Facebook Messenger and Kommo Nodes
Next, configure the nodes by filling in the required parameters according to your logic. Fields marked with a red asterisk (*) are mandatory.
Set Up the Facebook Messenger and Kommo Integration
Use various Latenode nodes to transform data and enhance your integration:
- Branching: Create multiple branches within the scenario to handle complex logic.
- Merging: Combine different node branches into one, passing data through it.
- Plug n Play Nodes: Use nodes that don’t require account credentials.
- Ask AI: Use the GPT-powered option to add AI capabilities to any node.
- Wait: Set waiting times, either for intervals or until specific dates.
- Sub-scenarios (Nodules): Create sub-scenarios that are encapsulated in a single node.
- Iteration: Process arrays of data when needed.
- Code: Write custom code or ask our AI assistant to do it for you.

JavaScript
⚙
AI Anthropic Claude 3
⚙
Kommo
Trigger on Webhook
⚙

Facebook Messenger
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Facebook Messenger, Kommo, and any additional nodes, don’t forget to save the scenario and click "Deploy." Activating the scenario ensures it will run automatically whenever the trigger node receives input or a condition is met. By default, all newly created scenarios are deactivated.
Test the Scenario
Run the scenario by clicking “Run once” and triggering an event to check if the Facebook Messenger and Kommo integration works as expected. Depending on your setup, data should flow between Facebook Messenger and Kommo (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Facebook Messenger and Kommo
Facebook Messenger + Kommo + Google Sheets: When a new message is received in Facebook Messenger, a new lead is created in Kommo. The lead's information is then added to a Google Sheet for tracking and analysis.
Kommo + Facebook Messenger + Slack: When a new lead is created in Kommo, a welcome message is sent to the lead via Facebook Messenger. Additionally, a notification is sent to a Slack channel to alert the team about the new lead.
Facebook Messenger and Kommo integration alternatives

About Facebook Messenger
Connect Facebook Messenger to Latenode to automate customer support or send personalized updates. Build flows to handle inbound messages, trigger actions in other apps, and route conversations intelligently. Use Latenode's visual editor and scripting tools to scale communication workflows with custom logic, without step-based pricing.
Related categories
About Kommo
Integrate Kommo with Latenode to automate sales processes. Trigger actions in other apps when deals change status, or create Kommo leads from form submissions. Build custom workflows with no-code tools or JavaScript, scaling your sales automation without complex coding. Use Latenode's visual editor to connect Kommo to your entire tech stack.
Similar apps
Related categories
See how Latenode works
FAQ Facebook Messenger and Kommo
How can I connect my Facebook Messenger account to Kommo using Latenode?
To connect your Facebook Messenger account to Kommo on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Facebook Messenger and click on "Connect".
- Authenticate your Facebook Messenger and Kommo accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically create Kommo leads from new Messenger messages?
Yes, you can! Latenode's visual editor makes this simple, even with custom logic. Automatically creating leads ensures no potential customer is missed, streamlining your sales process.
What types of tasks can I perform by integrating Facebook Messenger with Kommo?
Integrating Facebook Messenger with Kommo allows you to perform various tasks, including:
- Create new Kommo contacts from Facebook Messenger leads.
- Update Kommo deal stages based on Messenger interactions.
- Send automated Messenger replies for new Kommo leads.
- Log Messenger conversations as notes in Kommo.
- Trigger Kommo tasks based on keywords in Messenger chats.
Can I use JavaScript to extend my Facebook Messenger and Kommo workflows?
Yes! Latenode supports custom JavaScript code, allowing you to add sophisticated logic and data transformations to your Facebook Messenger and Kommo workflows.
Are there any limitations to the Facebook Messenger and Kommo integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Attachments from Messenger may have size limitations.
- Kommo's API rate limits might affect high-volume workflows.
- Custom field mapping requires precise configurations.