All nodes/Integrations/amoCRM

amoCRM Config

Selects a saved amoCRM connection (subdomain + long-lived API token) from the workspace. Credentials are configured in workspace settings, not in the graph.

Try it

When to use it

The node that holds an amoCRM connection. It earns its place when several REST calls talk to the same account: the account is chosen in one spot, and the canvas shows where the workflow reaches. A graph with a single call does not need it — the call node carries an “amoCRM connection” field of its own.

How it works

The credentials live in Settings → Integrations rather than in the graph: the account subdomain and the long-lived token issued in amoCRM’s own integration settings. This node references that record and, during a run, passes the resolved settings along the wire into the amocrm_config port.

It needs no execution input: the platform resolves the connection when the first consumer asks for it and reuses the result for the rest of the run. The run log shows only the connection name — the token never reaches it.

The subdomain is accepted in two shapes: a bare account name (mycompany, which becomes mycompany.amocrm.ru) or a full host, as long as it ends in amocrm.ru, amocrm.com or kommo.com. Other domains are refused when the integration is saved: the value goes into the request address together with the token.

Common mistakes

• An account outside the .amocrm.ru zone. For the international domain or Kommo, write the full host rather than the account name alone.
• A subdomain with a scheme or a slash. https://mycompany.amocrm.ru/ will not save — use either mycompany or mycompany.amocrm.ru.
• An empty “Connection” field. The node fails at run time; it will not guess an account.
• Expecting a connection check. amoCRM has no “Check connection” button — only mail and DAV do. A wrong or revoked token shows up on the first call as ACCESS_DENIED.
• One account, one node. Two accounts need two config nodes; a single one can feed any number of calls.

Inputs

—

Outputs

Configuration