AmoCRM connection
Integration can accomplish three tasks:
- transmit messages from amoCRM channels;
- Provide data on transactions, contacts and companies;
- Manage the bot and automatic messages from the amoCRM interface.
Before connecting n
Log in to amoCRM under an administrator or user with the right to install integrations. Determine which account and which funnels should ChatRex use.
Installation of the widget
- Open Integrations in ChatRex.
- Press Connect integration and select amoCRM.
- Open Installation of connection.
- Press Install widget.
- In the amoCRM window that opens, select the appropriate account and confirm permissions.
- Return to ChatRex and check the status of Connected.
Use as a channel
- Open My Bots → Change → Channels and Launch.
- Add amoCRM.
- If necessary, set conditions for the funnel, stage and fields of the transaction, contact or company.
- Set up a wait for the manager's response if the bot doesn't need to turn on right away.
- Select the CRM data to be transmitted to the bot via
@variables. - Save the changes.
If the bot needs to take into account previous correspondence, turn on the transmission of messages and set a reasonable amount of history.
Management of the deal
Open the amoCRM deal and the ChatRex widget in the right panel. It shows the status of the bot. A working bot can be paused for 1 hour, 1 day or forever.
Digital Pipeline Trigger
In the funnel settings, add the trigger ChatRex to the desired stage. For Send a message:
- Choose a bot;
- Select the amoCRM channel;
- specify fixed text or enable generation through AI;
- When generating, write an instruction and add the transaction fields via
@; - Save the trigger.
- Check it out on a test deal.
Actions
To change the status and fields of entities or set tasks, configure Actions amoCRM.
Verification
Use the test deal. Send a message through the amoCRM channel, check the launch of the desired bot, transmitted fields and record in history. Then check each action separately.
The conditions of several bots in one funnel should not overlap. Otherwise, a single message can trigger multiple scenarios.