Integration of amoCRM with website web forms and online store orders

Requests from any forms that send emails go to amoCRM. The "Send Test Request" button immediately shows how the settings work in amoCRM. A repeat request from a client can be added to their open deal instead of creating a new one. Form settings and the amoCRM connection are saved, so no reconfiguration is needed after an update.

Email Forms in amoCRM

A new "Email Forms" page in the "Services" section: requests from forms that send emails — the feedback component (main.feedback), forms from ready-made solutions, and custom forms — go to amoCRM.

Configuration is by email event type: select the type, enable sending, and map fields just like in the Web Forms tab. Available email fields are as tags — [AUTHOR], [AUTHOR_EMAIL], etc., and all fields at once — [ALL_FIELDS].

The email is sent as before: the module does not change or delay it.

Emails from web forms do not appear in the list — they are configured in the Forms tab, and there will be no duplicate deals. On order emails, the page warns about duplicates with "Store Orders".

Such requests are visible in the sending log; they can be repeated and rebuilt with new settings.

Test Request

The "Send Test Request" button is on the Web Forms tab, the Orders page, and the Email Forms page.

The request is assembled based on the settings on the page, even if not yet saved: placeholder name, phone, and email; other fields show "Test: ...".

The response is a link to the created deal or a clear amoCRM error. The test deal has the tag "test formsync" and can be deleted.

Repeat Request to an Open Deal

In the contact section, a new setting "Contact's Open Deal" is available. It works together with contact search by phone and email.

If the found contact has an open deal in the selected funnel, the request is added to it: a note "Repeat Request", tags, and a task are created. No new deal is created.

The deal stage, budget, fields, and responsible person do not change. If there are multiple open deals, it is added to the last modified one.

In the sending log, such requests are marked "added to open".

Sending of email forms and adding to an open deal are disabled until they are enabled in settings.

amoCRM fields of all main types: numbers, dates, links, addresses, checkboxes, radio buttons, and multi-select lists. Form answers with option selection and tags in the task text are inserted into the deal. Form settings and the amoCRM connection are preserved; after an update, no reconfiguration is required.

amoCRM Fields

Numeric fields, dates, birthdays, links, and addresses are sent to amoCRM. Form answers can be inserted into them, for example, [Area] or [Date]: numbers and dates are recognized from text ("1 500.50", "20.10.2026", "2026-10-20").

A radio button saves the selected option, a multi-select list saves all selected options, and a checkbox is sent as checked.

If the inserted value is neither a number nor a date, the field is not sent, and an entry appears in the module log; the deal is still created.

Form Answers

Answers to questions with selection—dropdown lists, checkboxes, radio buttons—are inserted as text of the selected options; multiple options are separated by commas.

Tags work in the task text: "Call back [Name]".

A question the visitor did not answer and a tag the visitor does not have are inserted as an empty string.

Other

The "amoCRM Integration" tab of the web form and the store order page collect the deal in the same way: everything listed applies to orders as well.

Tab texts are moved to language files.

Only filled fields are stored in the form settings.

After an update: if a value for an amoCRM field of type "radio button" was selected in the form tab, open the form and click "Save"; until then, the radio button value is not sent to amoCRM.

amoCRM sending log: you can see which leads and orders were sent, which were not, and why; unsent items can be resent. A notification email about an unsubmitted lead is now sent to the administrator on any website. Form settings and amoCRM connection are preserved; no reconfiguration is needed after an update.

Sending Log

New page "Services → amoCRM Sending Log": each form lead and each order includes source, status, number of attempts, link to the deal, and error text. Filters by status and source with counters.

"Resend" — if a connection or integration failure occurred: the lead is sent immediately as is.

"Rebuild and send" — if amoCRM rejected the data due to settings (e.g., a field was deleted in amoCRM): after correcting the form or order settings, the lead is rebuilt according to the new settings. Visitor tags (UTM, landing page, traffic source) remain the same as when the lead was created.

"Close" — if the deal was created manually: the lead data is removed from the log. There is also a "Resend all unsubmitted" button.

As long as there are unsubmitted leads, a notification with a link to the log appears at the top of the control panel.

Visitor data is not displayed on the page — only source, status, and error are shown.

Administrator Emails

The module automatically creates the email event "Lead did not reach amoCRM" and an email template addressed to the website administrator. A template created previously manually remains unchanged.

An email is sent for each lead that ultimately failed to reach amoCRM: amoCRM rejection, retries exhausted, or internal error. The email contains what failed, the reason, and a link to the log; no lead data is included in the email.

Fixed

For orders created in the control panel or received via synchronization, visitor tags with no value no longer appear in amoCRM as text like "[utm_source]".

Online store orders are now also sent to amoCRM; form submissions are sent via a queue and are not lost if amoCRM is unavailable. Form settings and the amoCRM connection are preserved, so no reconfiguration is needed after an update.

Online store orders → amoCRM

A new page "Services → Store Orders → amoCRM" appears (if the "Online Store" module is installed on the site). Sending can be enabled separately for each payer type.

Every new order becomes a deal: the title is "Order No. ... from the site", the budget is the order amount, the contact is taken from the order properties (full name, phone, email), and the company is used for legal entities.

The deal note contains the order composition, amount, delivery, payment, coupons, buyer comment, and a link to the order in the control panel.

Deal, contact, and company fields are configured the same way as for web forms: order properties, order data, and visitor tags (UTM, Roistat, advertising IDs, traffic source) are available.

One order equals one deal: re-saving an order does not create a second deal. Orders created in the control panel or received via 1C exchange are not sent by default; this must be enabled separately.

Submissions are not lost

Form submissions and orders are sent to amoCRM after the visitor receives a response: the page no longer waits for amoCRM.

If amoCRM does not respond, the sending is automatically retried, with intervals ranging from one minute to one day between attempts. If the submission still cannot be sent, the administrator receives an email.

After sending, the submission data is removed from the queue; personal visitor data does not accumulate in the database.

Contacts and responsible persons

Search for an existing contact by phone and email: if the buyer already exists in amoCRM, the deal is linked to them instead of creating a duplicate. The contact itself is not modified. This is enabled by default for orders and via a checkbox in the "Contact Fields" tab for forms.

The responsible person for a deal in the "Deal Fields" tab is selected for forms and orders. The same responsible person is assigned to the new contact and company. If the selected user is deleted in amoCRM, the request will still be sent with the default responsible person.

In the "Adding Tasks" tab, the labels are clarified: "Task Text" and "Task Responsible"; a task is created only if its text is specified.

Connect amoCRM with one click, automatic form configuration, and reliable token operation. Connections made in previous versions are automatically migrated; reconnection is not required. This version includes all security fixes from 2.2.0.

Connect amoCRM with one click

The new page "Services → Connect amoCRM" features a "Connect amoCRM" button that opens the amoCRM window; simply log in to your account and click "Allow". The amoCRM integration is created automatically; there is no need to create anything in amoMarket or copy keys, codes, or addresses.

For websites not accessible from the internet, two methods remain: custom integration (only the ID and secret key are entered; the redirect address is displayed as a ready-made string with a "Copy" button; the authorization code does not need to be copied) and a long-term token.

The page shows which account the website is connected to, what permissions have been granted, and until when the token is valid; buttons for "Check connection", "Reconnect", and "Disconnect" are available.

After installation, the module immediately offers to connect amoCRM: a button on the final installation screen and a notification in the control panel, which disappears after the connection is established.

Reliable operation with amoCRM

The token is updated in advance, before expiration, rather than after amoCRM rejects it; in case of rejection, there is a single update and a re-request. The update is protected against simultaneous launches from multiple requests, which previously could break the connection.

The agent checks the token once an hour instead of once a day: on websites with infrequent visits, the connection no longer expires between runs.

amoCRM keys and tokens are stored in the database in encrypted form.

Accounts on amocrm.ru, amocrm.com, and kommo.com are supported.

Form configuration

The "amoCRM Integration" tab for the new form is automatically filled out based on form questions: deal name, contact name, phone, and email, company, and note text. You only need to verify, select the sales funnel, and save the form.

If "Deal name" is not filled in, the deal receives the name "Request from the website: [form name] #[number]" instead of being lost.

The tab now displays all account fields — previously only the first 50 were visible.

The "Unsorted" stage is not offered if it is disabled in the funnel settings: deals used to go there, but they were not visible in amoCRM. For forms where it is already selected, the first funnel stage is automatically assigned upon submission.

If a form does not contain a name but has a phone number or email, the contact is still created.

Fixes

Form field settings are no longer cleared when saving the form if amoCRM did not respond at that time: previously the tab opened empty, and saving overwrote the field mappings.

Deal name, contact name, and notes are no longer swapped with adjacent fields during submission if one of them is left empty.

When uninstalling the module, you can choose whether to save form settings and the amoCRM connection. Previously, form settings were always deleted, while amoCRM keys were never removed.

The module settings page no longer accepts setting records: authorization fields have been moved to the connection page.

Security and compatibility update. No reconfiguration is required: form settings are preserved, and no administrator actions are needed after installation.

Security

The module log has been moved to a secure location. The log is no longer stored in the site's public directory, is inaccessible from the outside, and contains only error information without application data. The previous file /log.html is deleted during the update if it was created by the module.

Saving form settings is available only to administrators. Authorization checks, module permissions, and session validation have been added; the set of accepted parameters is limited, and service details are not displayed in the response.

The service file check_last_form.php, which is no longer used, has been removed.

Escaping of values on the form settings page has been strengthened.

Module scripts are loaded via a relative path, and the page address for the deal card is taken from the site settings.

Connection to amoCRM is performed only when saving the form settings, with session and module permission checks.

Region determination by IP is performed over a secure connection and only when the region is used in the form settings.

Compatibility

Full support for PHP 8.2 without deprecation code warnings.

The module works correctly on hosting with the short_open_tag setting disabled.

The settings table is converted to utf8mb4: field mapping supports emojis and any characters.

Improvements

Saving form settings is more reliable over slow connections.

Protection against resending the same application has been improved.

Form submission is faster: the funnel list is cached.

The log specifies clear reasons if an application cannot be sent to the CRM: the deal name is not filled, the form has no integration settings, or mandatory field validation failed.

Module removal has been improved: event handlers are removed correctly.

Module code has been optimized.

Module integration update

Fixed an error that, in some cases, prevented applications from being sent to amoCRM when cookies were missing or blocked.