amoCRM

amoCRM is a cloud CRM for sales. The block talks to REST API v4: it reads and updates leads, contacts, tasks, and notes. Stable operation needs a long-lived private-integration token and the account subdomain.

With amoCRM in Pailot you can:

• List leads — search, pipeline filter, pagination
• Create and update leads — name, budget, pipeline, stage, owner, custom fields (JSON)
• Work with contacts — search list, create with phone and email
• Create tasks — text, Unix deadline, type (call / meeting / email), link to a lead, contact, or company
• Add notes — on a lead, contact, or company

The integration supports an amoCRM webhook trigger (a webhook is an inbound HTTP request from the service). The workflow runs on the events you tick, if amoCRM has the URL from the block.

How to connect

1. In amoCRM open Settings → Integrations and create an integration (or reuse one).
2. Create a private integration, open Keys and access, and issue a long-lived token. Use that token: a normal OAuth access token (sign-in by granting the app permission) lasts about 24 hours, and the block does not refresh it — Pailot has no refresh-token flow, so a short token dies after a day.
3. In the block set Subdomain — the host part before .amocrm.ru (for mycompany.amocrm.ru that is mycompany).
4. Paste the token into the block Access token field.

Trigger (webhook)

1. Turn on Trigger on the block and save.
2. Copy the generated webhook URL.
3. In amoCRM: Settings → Integrations → Webhooks — add the URL and tick events (add_lead, update_lead, status_lead, add_contact, and others).

Trigger outputs. amoCRM sends x-www-form-urlencoded bodies with bracket keys such as leads[add][0][id]. Pailot unfolds them, so leads, contacts, tasks, and account arrive as objects. Reference fields as <Trigger.leads.add[0].id>.

amoCRM does not send an event field: the action lives in the key nesting. Pailot derives the name — leads[add] becomes add_lead, leads[status] becomes status_lead, task[add] becomes add_task. Provider names are asymmetric: leads are plural leads, tasks are singular task.

API docs: reference, webhooks.

Tools

amocrm_get_leads

List leads with optional search and pipeline filter.

Output: total, items (lead array), message.

amocrm_create_lead

Create a lead.

Output: id, name, message.

amocrm_update_lead

Update a lead by ID. Other fields match create (partial update).

Output: id, name, message.

amocrm_get_contacts

List contacts: query, limit, page. Output: total, items, message.

amocrm_create_contact

Create a contact (name, phone, email; extra fields as JSON). Output: id, name, message.

amocrm_create_task

Output: id, text, message.

amocrm_add_note

Output: id, entityType, entityId, message.