Connecting amoCRM

One amoCRM connection is active in each Senler project. Every agent tool and automation step in that project uses it.

Authorize the Senler project

On first launch, the application shows only the authorization screen. Click Sign in and grant access to the current project. The amoCRM account setup opens after the redirect.

Senler OAuth lets the application deliver targeted events and keep the amoCRM contact ID in the current lead's variable. If the stored token lacks current permissions, the application requires a token update before setup can continue.

Connect an account

After Senler authorization, use the account card and click Connect.

In the amoCRM window:

1. Sign in as a user of the required account.
2. Check the selected account.
3. Grant the requested access to CRM data.

After authorization, the window closes and the application refreshes the status. OAuth tokens are encrypted on the server and never displayed in the interface.

Reconnect an account

If access was revoked, the amoCRM user changed, or you need a different account, click Reconnect and authorize again.

A successful connection replaces the current project's tokens. It does not delete contacts, deals, notes, or tasks in amoCRM.

Disconnect an account

Click Disconnect and confirm. The application first removes its amoCRM webhook and then deletes the project's saved connection.

Disconnecting in Senler does not delete amoCRM data. If the integration is removed in amoCRM, its signed notification also disconnects the corresponding Senler project.

Projects and accounts

The same amoCRM account can be connected to several Senler projects, but each connection must be authorized separately. A user opening the embedded application sees only the current project's state.

The account name and domain in the connection details help confirm that you selected the right account. Reconnect if the domain is incorrect.

Deal stage events

After the account is connected, the application automatically subscribes amoCRM to status_lead. There is no separate setting or toggle in the embedded page. The amoCRM user must be an administrator, and the plan must support the webhook API.

To process a stage change, enable the Deal stage changed application event for an agent, add it as the start step of a contextual automation, or use both. Senler first uses the dialog explicitly linked to the deal; it selects the lead's latest active private dialog only when that exact link is missing. Only agents assigned to the resolved dialog and subscribed to this event react to it. Disconnecting the amoCRM account automatically removes the webhook without deleting deals or other CRM data.