bitrix24_crm_activity_list
List CRM timeline activities with resolved attachment details and call metadata. Identify sent documents, call direction, and duration for any lead, deal, contact, or company.
Instructions
List timeline activities (calls, emails, SMS, meetings) on a CRM lead/deal/contact/company. Use this to see a lead's call log: each phone call is one activity. Key fields: TYPE_ID (2=call, 4=email, 6=SMS, 1=meeting, 3=task), PROVIDER_TYPE_ID ('CALL' for phone), DIRECTION (1=incoming, 2=outgoing), START_TIME/END_TIME (subtract for duration), RESPONSIBLE_ID (the manager). FILES are ATTACHMENTS, not just call recordings: on an email activity they are the documents that were sent or received (счёт, спецификация, смета, КП, договор, ТЗ, чертежи). Raw Bitrix returns them as bare {id, url} with no name, so this tool resolves each one and adds name/size/kind plus a per-activity FILES_SUMMARY {documents, document_names, call_recordings, signature_images, images, other}. ALWAYS read FILES_SUMMARY.document_names before concluding that a manager sent no calculation, no price or no КП — the price is routinely in the attached PDF while the email body says only «направляю расчёт». Inline Outlook signature logos (image001.png and similar) are classified as signature_image and carry no meaning. CALL TRANSCRIPTS: the activity record itself has no transcript field (DESCRIPTION/PROVIDER_DATA are empty on calls, and Bitrix's own BitrixGPT call scoring is UI-only), but this portal runs a local speech-to-text pipeline that writes finished transcripts into the call's TIMELINE NOTE. So a missing transcript here does NOT mean there is none: check bitrix24_crm_timeline_note_get (itemId = the call activity ID) before concluding anything about a call, then fall back to bitrix24_crm_timeline_comment_list. Coverage of the note pipeline is partial (~16% of call activities, skewed to longer calls), so an absent note is not evidence that no conversation happened. For call duration/direction/recording-file-id use bitrix24_voximplant_statistic_get, which is authoritative over anything written in a note header.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max activities to return (default cap 500 = 10 pages x 50; pass limit >= total to fetch all). | |
| order | No | Sort order, e.g. {CREATED: 'desc'} | |
| filter | No | Extra filter merged with the owner, e.g. {PROVIDER_TYPE_ID: 'CALL'} for calls only, {PROVIDER_ID: 'CRM_EMAIL'} for emails, {COMPLETED: 'Y'}, {DIRECTION: 2} for outgoing. Date-bound filters accept full ISO timestamps and are honoured: {'>=CREATED': '2026-07-20T00:00:00+03:00'}, {'<CREATED': '...'}, {'>CREATED': '...'} (verified 2026-07-28; the filter is posted as JSON so there is no key-encoding trap). | |
| select | No | Fields to return | |
| ownerId | Yes | ID of the lead/deal/contact/company | |
| ownerType | Yes | CRM entity type the activities belong to | |
| resolveFiles | No | Resolve attachment names/sizes/kinds via disk.file.get (default true). Costs one extra REST call per 50 attachments and nothing when the result set has none. Pass false only when attachments are irrelevant and latency matters; the raw {id, url} pairs are then useless for judging what was sent. |