amoCRM notifications in Telegram: new deals and stage changes

amoCRM notifications in Telegram take no code in nana800: amoCRM itself sends an event, such as a new deal, to the webhook address of your scheme, and the bot posts it to your private chat or team group. You need a bot from @BotFather and access to the amoCRM settings, with no server of your own. One notification is two runs at the basic block price.

Build it in the builder

What you can automate

  • Post every new deal to a team group: its name, budget and a button that opens the deal in amoCRM
  • Tell the manager when a deal reaches the won stage: the free condition block lets only that stage through
  • Route deals to different chats: the condition block compares the pipeline ID and sends the message to the right team
  • Add the customer name and phone to the message: the amoCRM request block reads the deal and its contact by ID
  • Get new contacts and tasks in Telegram: tick these events in the amoCRM webhook settings

How to set it up

  1. 1

    Create a scheme with a webhook

    Create a scheme in the builder and add the webhook trigger. Choose the POST method, which is how amoCRM sends events. Any path works, for example /amo. Turn the scheme on, press the API button in the builder and copy the webhook address.

  2. 2

    Enter the address in amoCRM

    A webhook is an address amoCRM calls by itself with the data of an event. In amoCRM open amoMarket and find the Web hooks item there. Paste the nana800 address and tick the events you need, for example a new deal or a deal stage change.

  3. 3

    See what amoCRM sends

    Create a test deal and open the run history of the scheme. The trigger body has a leads section: add holds new deals, status holds stage changes. Inside are the deal ID, name, budget (price), stage ID (status_id) and pipeline ID (pipeline_id), and account holds your account name.

  4. 4

    Add the Telegram message send block

    Paste the bot token from @BotFather and the chat ID: your own from @getmyid_bot or the ID of a group the bot was added to. Put the deal name and budget from the trigger into the text and pick the plain_text format. You can add a button with a link to the deal: the account address, /leads/detail/ and the deal ID.

  5. 5

    Read the customer contact (optional)

    The webhook has no customer phone. Put the amoCRM request block before Telegram: account address, long-lived token, GET, the leads section, the deal ID from the trigger and the parameter with = contacts. It returns the contact ID of the deal, and a second such block with the contacts section returns the name and the contact fields with the phone.

  6. 6

    Test and keep the scheme on

    Create one more test deal: the message arrives in Telegram. The scheme has to stay on all the time, otherwise amoCRM events are not processed. While it is on, it costs $0.0042 per hour.

Pricing

A run of a amoCRM block costs $0.002, a run of a Telegram block costs $0.001. Every month the balance is topped up to $3.50 for free, an enabled scheme costs $0.0042 per hour.

Services in this connection

  • amoCRM

    Automate amoCRM without code: website and Telegram leads become deals, and tasks and notes are added for you. Free balance every month, no card needed.

  • Telegram

    Build a Telegram bot without code: reply to messages, add buttons, send leads and alerts to a chat, group or channel. Free balance every month, no card needed.

Frequently asked questions

One notification is a webhook trigger run and a Telegram send, both at the basic block price ($1 per 1,000 runs). Each amoCRM request block run costs twice as much, and the condition block is free. A webhook scheme stays on all the time, which is $0.0042 per hour. Your balance is topped up to $3.50 for free every month, and most of it goes to scheme hours.

Not for the notifications themselves: amoCRM sends events to the webhook address without any keys. A long-lived integration token from amoMarket is needed only if the scheme reads more data with the amoCRM request block, such as the customer contact and phone.

Create two webhooks in amoCRM with different addresses, for example with the paths /amo/new and /amo/stage. In the scheme add two webhook triggers with these paths, each with its own send block: new deal data is in leads.add, stage change data is in leads.status.

Yes. Put the free condition block after the trigger and compare pipeline_id or status_id from the webhook with the number you need. You will see the IDs in the run history after moving a test deal. The won and lost stages have the same IDs in every pipeline: 142 and 143.

Check that the scheme is on: a disabled scheme answers amoCRM with an error and the event is not processed. The trigger must use POST, and the address in amoCRM must match the one from the API button, path included. If the run history has the run but no message came, open the Telegram block result to see the error text.

Build your first scheme for free

Sign-up is free and needs no card. Every month the balance is topped up to $3.50 for free, enough for about 3,500 runs of basic blocks.

Build it in the builder