Troubleshooting

Check issues in this order: Senler project → amoCRM connection → tool or step parameters → amoCRM user permissions.

The application does not open

Open amoCRM from the installed applications list of the required project. A direct link to the embedded page has no one-time launch code and cannot create a session.

If the application has been open for a long time, close it and launch it again from Senler.

The amoCRM window does not open

Allow pop-ups for Senler and click the connection button again. If the window opened but access was not granted, reconnect and approve the permissions.

Authorization is valid for ten minutes. Do not return to an old window after that period; start a new connection instead.

The connection disappeared

Check the account status. A connection is removed after a manual disconnect in Senler or removal of the integration in amoCRM.

Reconnect if amoCRM revoked or no longer accepts the token. Existing CRM data remains unchanged.

A tool or step returns an error

Make sure the action runs in the project where the account is connected. Check required fields and types: names and text cannot be empty, while IDs must be positive integers.

Temporary amoCRM availability or request limits can fail a call. Retry only when you know that the previous operation did not create an entity; if the result is uncertain, first inspect amoCRM using known IDs.

An entity is missing or the wrong record changed

Tools read and update entities by exact ID, not by name. Make sure contact_id, deal_id, or entity_id belongs to the account shown in the connection card.

If a contact has several deals, call List contact deals first and select the correct deal_id by name, stage, and conversation context. The application intentionally does not pick the “latest” deal automatically.

For notes and tasks, use entity_type: leads for a deal and entity_type: contacts for a contact.

Deal stage events do not arrive

Authorize Senler first, then connect amoCRM. The application creates its webhook automatically; the amoCRM user must be an administrator and the account plan must support the webhook API. If automatic setup fails, the embedded page shows an error. Fix the permissions or plan and reopen the application.

Make sure the event is enabled for the intended agent and that this agent is assigned to the resolved dialog. If you use an automation, it must be enabled and start with Deal stage changed. When a tool or step already used the deal in a dialog, the event is routed to that exact dialog. Without an exact link, Senler searches for the contact's latest active private dialog. If no matching lead exists or it cannot receive messages, the event is marked unresolved.

Contacting support

Provide support with:

• the Senler project name;
• the amoCRM account domain;
• the tool or step name;
• contact_id, deal_id, note_id, or task_id when known;
• the exact error and time it occurred.

Do not send OAuth tokens, the integration secret, customer personal data, or the full conversation log unless necessary.