CRM objects
- Lead — an unqualified inquiry; the entry point of the funnel before conversion to contact + deal
- Deal — a qualified sales opportunity moving through pipeline stages toward won or lost
- Contact / Company — the person and organization records that deals attach to
- SPA (Smart Process Automation) — a custom entity type you define, with its own fields, pipelines, and automation; used for units, policies, applications, vehicles, anything CRM doesn't model natively
- Pipeline / Funnel — a named sequence of stages; multiple pipelines separate distinct processes
- Custom field (UF_CRM_*) — a field you add to any CRM object; the UF_ prefix appears in API payloads
Automation
- Automation rule (robot) — a stage-scoped trigger-action rule: assign, task, message, change field
- Trigger — an event (call received, form filled, payment made) that moves a record to a stage
- Workflow (Business Process / bizproc) — a designed multi-step process with conditions and approvals, richer than automation rules
- Queue — ordered distribution of leads/calls among users
Integration & platform
- REST API — the HTTP interface for reading/writing Bitrix24 data (crm.lead.add, crm.deal.list…)
- Incoming webhook — a per-user URL that lets external systems call REST methods without OAuth
- Outgoing webhook / event — Bitrix24 notifying your endpoint when something happens (ONCRMLEADADD…)
- Local app — a private OAuth application registered in your portal, capable of embedded UI
- Placement — a slot in the Bitrix24 UI (deal tab, CRM widget) where an app can render
- batch — a REST method bundling up to 50 calls in one request; essential under rate limits
- Scope — the permission set (crm, tasks, telephony…) granted to a webhook or app
- BI Builder — Bitrix24's dashboard layer over CRM data with datasets and calculated fields
- Open Channels / Open Lines — the connector layer binding WhatsApp, Instagram, and chat to CRM