A chat message is written into the amoCRM deal
A customer writes about their deal and the scenario updates its card, then confirms what was recorded.
What the scenario looks like
- Execute + Data
- LLM
- Data
A customer writes “on deal 4821 we can go up to 250k”, a manager reads it and eventually copies it into the card. Between “said” and “recorded” lies a day and half the forgotten details.
What is inside
- A customer message — the entry.
- What matters here — the model pulls out the deal number, the gist and the amount.
- The request body assembles JSON for the CRM.
- Update the deal posts it to an address carrying the deal number: the path is a template too.
- Answer to the customer confirms what was written.
The “from chat” tag in the body is not decoration. It is how you later see which deals the bot touched itself; without it, working out who made a change means reading the card history.
The request body is assembled by a template
The Body field is a JSON object, and here it is assembled on the previous step. Values go
through | tojson: a name with a quote or a line break does not break the request, and
adding a field is one template edit.
The path and the body are the only things that change for a different CRM task. The node knows nothing about deals and contacts — it posts what you wrote to the address you named — so the wiring stays the same.
What to set up for yourself
- The connection on the amoCRM node.
- The fields.
priceand tags are an example. Your own fields (city, source, budget) have codes visible in the CRM settings and go into the same body. - A branch for “no number”. If the customer named no deal, the address assembles incomplete and the request goes nowhere. A real scenario checks for that first.
What to connect
An amoCRM account: add a connection in settings with the subdomain and a long-lived token (the integration is created inside the CRM). Test against a scratch deal: a badly assembled body changes a card, and undoing that is manual.