bxmaximum/bitrix-framework-skills

bitrix24-crm

D7 CRM in Bitrix24 on-premise: Container, Factory, Item, Operations, smart processes (dynamic types), stages, permissions, timeline, CRM events.

Vedi sorgente

Come usare

  1. Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
  2. Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
  3. Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/bxmaximum/bitrix-framework-skills --skill bitrix24-crm

Prima di iniziare

  • L’installazione non include abbonamenti, quote API o accesso ai file.
  • Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Documento Skill originale

Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.

Bitrix24 CRM (server side)

Scope: Bitrix24 on-premise · Verified: crm 26.800.0, main 26.800.0

PHP running inside the portal: /local/ modules, handlers, agents. Calling CRM over REST: bitrix24-rest-api.

TaskRead
Container, Factory, reading items, field names, phones/e-mailsrules/factory-items.md
Add/update/delete, Context, checks, custom actionsrules/operations.md
Smart processes, funnels, stages, smart invoicesrules/smart-processes.md
Rights checks, permission-filtered listsrules/permissions.md
Reacting to changes, factory override, robots, triggersrules/events-automation.md
Timeline comments, to-dos, activitiesrules/timeline-activities.md
Fields collection, user fieldsrules/fields-uf.md
CCrmDeal/CCrmLead/… replacements, D7 ↔ REST maprules/legacy-rest.md

Invariants

  • Loader::includeModule('crm') first; get services from Container::getInstance().
  • Write only through Factory operations: getAddOperation()/getUpdateOperation()/getDeleteOperation() → launch(). Never DealTable::add(), $factory->getDataClass()::update(), Item::save()/Item::delete(): they skip rights, required fields, events, timeline, search index and robots.
  • Use Item::FIELD_NAME_* names; the factory maps them to entity columns (lead STAGE_ID → STATUS_ID).
  • Dynamic entityTypeId, funnel and stage IDs differ per portal: resolve by code or semantics at runtime, never hardcode.
  • Agents, CLI and queues have no user: pass a Context with a user ID, or disable the access check on purpose.
  • Check isSuccess() of every launch() and pass its errors up.

Correlati per attività

dallo stesso repository

Altri Skills

Tutti gli Skills