Getting started

The amoCRM application connects a Senler project to one CRM account. Once connected, agents and automations can safely create and update contacts and deals, change stages and owners, read data, add notes, and create tasks. No amoCRM keys are required: an account owner grants access through the regular OAuth window.

What you need

Before setup, prepare:

• a Senler project where the amoCRM application is installed;
• an amoCRM user who can grant the application access to CRM data;
• a Senler agent or automation that needs amoCRM data.

The connection belongs to one Senler project. Connect it separately in every other project.

1. Open the application

Open the installed amoCRM application from the required Senler project. Do not use a direct link to the embedded page: Senler provides the secure session and project identifier only when it launches the application.

2. Authorize the Senler project

On the first screen, click Sign in and grant the application access to the current Senler project. This authorization is normally required once; if application permissions change, an Update token button appears instead.

3. Connect an amoCRM account

Click Connect. In the window that opens, sign in to amoCRM, select the account, and grant access. Use an amoCRM administrator to connect stage-change events automatically; webhook API availability also depends on the plan.

After a successful return, the status changes to Connected, while the connection card shows the account name and domain.

4. Add an action in Senler

Choose the suitable mode:

• add an application tool to an agent when the agent should decide whether to use CRM during a conversation;
• add an application step to an automation when the action must run at a fixed point in a workflow.

Both modes use the current project's single amoCRM connection and the same rules for contacts, deals, notes, and tasks.

5. Optionally react to a stage change

Enable the application's Deal stage changed event for an agent when that agent should continue the conversation after a stage change. For a multi-step flow, create a contextual automation with the event as its start step. You can use both modes; there is no separate webhook toggle in the embedded page.

If the deal was already used in a dialog, the agent event and automation run in that exact dialog. Only when there is no exact link does Senler select the linked lead's latest active private dialog. If none exists and the lead can receive messages, Senler creates a private dialog.

Result

After setup, the application can:

• create a contact and deal separately in amoCRM; check the current lead's contact and its deals first to avoid duplicates;
• list the contact's open or closed deals and select the right one by ID, name, and stage;
• create a new deal or update one explicitly selected by deal_id;
• change a deal's stage, pipeline, value, owner, loss reason, and tags;
• read current contact and deal fields;
• add a note or task to a contact or deal;
• send a deal stage change to an assigned agent and/or start an automation in the appropriate dialog.

The application does not delete amoCRM entities and never exposes OAuth tokens to the agent, automation, or browser.