All nodes/Integrations/Bitrix24

Bitrix24 Config

Selects a saved Bitrix24 connection (incoming webhook) from the workspace. Credentials are configured in workspace settings, not in the graph.

Try it

When to use it

The node that holds a Bitrix24 connection. It is useful when several REST calls talk to the same portal: the portal is chosen once, and the canvas shows where the workflow reaches. A graph with a single call does not need it — the call node carries a “Bitrix24 connection” field of its own.

How it works

The Bitrix24 credential is the incoming webhook URL in its entirety (portal, user id and webhook code in one address). It is stored as a secret under Settings → Integrations; this node only references that record and passes the resolved settings along the wire into the bitrix24_config port.

The node 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. Only the connection name is left in the run log.

The integration form has an optional “Portal domain” field. When it is filled in, the domain is cross-checked against the webhook’s host — a guard against pasting a webhook from a different or stale portal.

Common mistakes

• A portal domain that disagrees with the webhook. The integration will not save until the two match; leaving the field empty is simpler than tuning it by hand.
• An empty “Connection” field. The node fails at run time.
• Expecting a connection check. Bitrix24 has no “Check connection” button — only mail and DAV do. A wrong webhook shows up on the first call.
• One portal, one node. Two portals need two config nodes; a single one can feed any number of calls.

Inputs

—

Outputs

Configuration