Ready-made solutions for Bitrix24

Build me a Deal Radar for Bitrix24. For the company on a deal, generate a live briefing: what they do, a quick snapshot (headcount, funding, HQ), and recent signals (funding, hiring, launches, news) with sources — plus a “why call now” summary. Clean two-column layout, light styling.

Read the deal + linked company via GET /v1/deals/:id and GET /v1/companies/:id.
Find recent signals with POST /v1/search (AI Search) using the company name/domain; keep only on-topic results and show the source for each.
Write the “what they do” + “why call now” text with POST /v1/chat/completions.

API key: vibe_api_xxx (scopes: crm, vibe:search, vibe:ai)
API Discovery: https://vibecode.bitrix24.com/v1/me

Build me a Daily CRM Digest for Bitrix24. Every morning it reads my open deals and shows a one-line AI "focus for today", then four columns: deals closing this week, deals going stale (idle 7+ days), deals waiting on my reply, and new leads overnight — each with the amount and a short AI reason. Clean, light, scannable in 10 seconds.

Read deals with GET /v1/deals (filter by stage, close date, last activity date).
Group them into the four buckets in code; use POST /v1/chat/completions only to write the one-line focus summary and the short per-deal reasons. Compute all amounts/counts yourself.

API key: vibe_api_xxx (scopes: crm, vibe:ai)
API Discovery: https://vibecode.bitrix24.com/v1/me

Build me a Lead Scoring Board for Bitrix24. Score every open deal by likelihood to close and sort them into three columns — Hot, Warm, Cold — each card showing the company, amount, stage, a score ring, and a one-line AI reason for the score. Clean, light, scannable.

Read deals with GET /v1/deals. Compute the score in code from CRM signals (stage, days since last activity, number of contacts, amount) — don't let the model invent the number.
Use POST /v1/chat/completions only to write the short reason per deal.

API key: vibe_api_xxx (scopes: crm, vibe:ai)
API Discovery: https://vibecode.bitrix24.com/v1/me

Build me a Project Decomposition tool. I describe a goal in plain language and it breaks it into phases and tasks with time estimates, labels and dependencies, shown as a clean expandable tree with a summary of phases, tasks and total time. Add a button to push the plan into Bitrix24 Tasks.

Call POST /v1/chat/completions to turn the goal into phases[] and tasks[] with estimateDays, a label, and dependencies. Compute the phase/total estimates yourself from the task days (don't trust a model-supplied total).
Optionally create the tasks with POST /v1/tasks when the user clicks Push to Tasks.

API key: vibe_api_xxx (scopes: task, vibe:ai)
API Discovery: https://vibecode.bitrix24.com/v1/me

Build a Stale Task Monitor for my Bitrix24 portal. It reads my open tasks, scores each one for "risk of being forgotten", and shows the worst offenders in a single queue — with a plain-language reason why each task is stuck and one concrete next step. No boards, no charts to interpret: one screen, one ranked list, one decision per row.

Read open tasks with GET /v1/tasks. Compute a 0-100 risk score in code from three readable fields: days past deadline (0-40), age since planned start date (0-40), priority weight (0-20), and show the split as a stacked bar under the score.
Use POST /v1/chat/completions only for the reason and the next step. Activity timestamps are read-only on most portals, so measure staleness from the planned start date and label it that way in the UI. Never state a fact about a task that isn't in its title, status or dates.

API key: vibe_api_xxx (scopes: task, vibe:ai)
API Discovery: https://vibecode.bitrix24.com/v1/me

Turn meeting notes into Bitrix24 tasks without the copy-paste. Paste the notes, and the app pulls out the action items, guesses a due date and an owner only when the text actually says so, and links every draft task back to the line it came from. You tick what's real, fix what isn't, and press create once. It also shows what it deliberately didn't turn into a task — decisions, FYIs, context — so nothing gets silently invented or silently dropped.

Send the pasted text to POST /v1/chat/completions in one batched call, with a closed output format: title, source line index, due date (or null), owner (or null), plus a skip reason for anything that isn't an action item. Never infer a date or an owner that isn't in the text — render "No date mentioned" instead. Verify every draft against its source line and drop what doesn't match.
Create the ticked tasks with POST /v1/tasks, only on explicit click.

API key: vibe_api_xxx (scopes: task, vibe:ai)
API Discovery: https://vibecode.bitrix24.com/v1/me

Build me an HR Policy Bot for Bitrix24. An employee asks a question in plain language and it answers from our company handbook, showing the exact policy quote and section it's based on, plus a few related questions they can tap. Clean, centered, light styling.

Store the handbook as sections (title, §, text). For a question, call POST /v1/chat/completions with the relevant sections and ask it to answer ONLY from them, returning the answer, a verbatim quote, and the section reference. If the handbook doesn't cover it, say so — never invent policy.

API key: vibe_api_xxx (scopes: vibe:ai)
API Discovery: https://vibecode.bitrix24.com/v1/me

Build me a Team Leave Board for Bitrix24. It shows a two-week timeline of who on the team is on vacation, sick leave, or a day off — color-coded, with today highlighted. A sidebar lets me request time off and shows who's out today. Clean, light styling.

Call POST /v1/chat/completions to draft a short, polite one-line notice to the manager when a time-off request is submitted. Render everything else from data — no AI needed for the display itself.

API key: vibe_api_xxx (scopes: vibe:ai, vibe:infra)
API Discovery: https://vibecode.bitrix24.com/v1/me

Build me an Onboarding Tracker for Bitrix24. It shows a new hire's onboarding checklist grouped into four fixed categories (Access & Setup, Team & Culture, Tools & Training, First 30 Days), each with a progress ring, plus overdue reminders. A small form lets me generate a fresh plan for any role.

Call POST /v1/chat/completions to draft the checklist for a given role/department — ask for plain-text JSON (structured output isn't supported), parse it with a fallback, and validate categories + target-day buckets against a closed set.

API key: vibe_api_xxx (scopes: vibe:ai, vibe:infra)
API Discovery: https://vibecode.bitrix24.com/v1/me

Build me a Product Description Generator. I enter a product name, a few key details, pick a tone and the languages I sell in, and it writes ready-to-publish descriptions for each — matching the tone, with copy and regenerate buttons. Two-panel layout: inputs on the left, generated copy on the right.

For each selected language, call POST /v1/chat/completions with a system prompt like:
'You are an e-commerce copywriter. Write a {tone} product description (2-4 sentences) in {language}. Ready to publish, no preamble.'
Pass the product name + details as the user message. Render one result card per language.

API key: vibe_api_xxx (scopes: vibe:ai)
API Discovery: https://vibecode.bitrix24.com/v1/me

Show me the content plan the way it actually looks. It reads the calendar, lays five weeks out on a grid, colours each item by type — blog, social, email, webinar, launch — and dims what's already published. Then it points at what a calendar alone won't tell you: the five quiet days right before a launch, the two social posts scheduled for the same day, the week where one day carries three items. It reads only what's scheduled: an empty day is shown as empty, never filled in with a guess.

Read events with GET /v1/calendar-events — type and ownerId are required, or nothing comes back. Parse the content type from a prefix in the event title ([Blog], [Social], [Email], [Webinar], [Launch]); the entity has no type field of its own.
Watch the timezone: an offset sent as +03:00 comes back normalised, which can move an early-morning event to the previous day — normalise before bucketing by day.
Compute gaps, pile-ups and same-type collisions in code. Use POST /v1/chat/completions only to phrase each finding, and only from findings the code already established.

API key: vibe_api_xxx (scopes: calendar, vibe:ai)
API Discovery: https://vibecode.bitrix24.com/v1/me

Give it a list of competitors and it checks the web for what they've actually done lately — shipped a feature, changed pricing, moved people — and lays it out as a grid of who moved where. Every row is one source that passed the checks, and a card only appears if that page actually names the company. Earnings coverage and analyst commentary get tagged as market noise instead of being passed off as product news, and everything the filter threw out is shown as a count, so you can see what you're not seeing.

Search with POST /v1/search, one query per competitor, topic=news over a time range. Apply two gates before rendering anything: relevance score >= 0.35, and the company name must appear in the source title, text or URL — not just in the engine's summary. De-duplicate twice: at most one card per host, then again by headline, because one press release gets republished across many sites under the same title.
Classify each survivor with POST /v1/chat/completions into a closed set — Product, Pricing, People, Noise — defaulting to Noise when unsure. Never display the engine's own summary as fact: it carries no markers tying a sentence back to a source. A competitor with nothing verified is shown as quiet, not filled in.
Run an invented company name on every refresh as a control — it should return zero cards.

API key: vibe_api_xxx (scopes: vibe:search, vibe:ai)
API Discovery: https://vibecode.bitrix24.com/v1/me

Build me a Decision Doc Generator. I describe a decision and some context, pick the audience, and it produces a structured one-pager: problem, 2–3 options with pros and cons, a recommendation, risks with severity, and next steps with owners. Show it as clean document sections with copy and export. Light styling.

Call POST /v1/chat/completions to return the sections: problem, options[] (name, pros, cons, recommended), recommendation, risks[] (text, level), nextSteps[] (text, owner).
Adapt depth to the chosen audience. Ensure exactly one option is marked recommended.

API key: vibe_api_xxx (scopes: vibe:ai)
API Discovery: https://vibecode.bitrix24.com/v1/me

Build me an Announcement Writer for Bitrix24. I enter a few bullet points about what happened, pick a tone and one or more languages, and it writes a warm, ready-to-post company announcement in each language. Show input on the left, results on the right, with copy and regenerate buttons per language. Clean, light styling.

Call POST /v1/chat/completions once per selected language with a system prompt describing the tone and language. Pass the bullet points as the user message. Render each result with copy/regenerate; on a failed call, show a soft fallback instead of breaking the whole screen.

API key: vibe_api_xxx (scopes: vibe:ai, vibe:infra)
API Discovery: https://vibecode.bitrix24.com/v1/me

Build me a Smart File Organizer for Bitrix24. I have a messy list of files; it groups them into clean topic-based folders automatically, showing a map of clusters with the files inside each one. A button re-organizes everything fresh with AI.

Call POST /v1/chat/completions with the file list (name + type) and ask for a JSON array of {category, fileNames} groups — structured output isn't supported, so parse the response as text with a fallback, and keep a catch-all "Other" bucket for files that don't fit clean rather than dropping them.

API key: vibe_api_xxx (scopes: vibe:ai, vibe:infra)
API Discovery: https://vibecode.bitrix24.com/v1/me

Build me a Smart Intake tool for Bitrix24. As requests arrive from any channel, classify each by topic, sentiment and urgency, then route it to the right team — shown as a live queue with tags and destinations, plus counters for new, urgent and auto-routed. Clean, light styling.

For each request, call POST /v1/chat/completions asking it to return a fixed set of fields:
category, sentiment (positive/neutral/frustrated), priority (urgent/high/normal/low), route (team name).
Sort the queue by priority. Anything the model can't confidently route → mark for manual triage (don't guess).

API key: vibe_api_xxx (scopes: vibe:ai)
API Discovery: https://vibecode.bitrix24.com/v1/me

Build me a CSAT Pulse for Bitrix24. Show an overall customer-satisfaction gauge with avg rating, NPS and response count, a positive/neutral/negative split, a weekly trend, and an AI "what's driving it" panel that pulls the top praise and complaint themes from the comments. Clean, light, one screen.

Store survey responses (rating + comment) as demo data. Compute the gauge, splits, NPS and trend in code. Use POST /v1/chat/completions only to cluster the free-text comments into a few named themes with counts. Don't let the model invent the numbers.

API key: vibe_api_xxx (scopes: vibe:ai)
API Discovery: https://vibecode.bitrix24.com/v1/me

Build me a Ticket Deflection Radar for Bitrix24. Analyze support tickets, cluster the repetitive questions, and rank them by volume — each showing example phrasings, ticket count, estimated agent hours, and a suggested fix (Automate / Add FAQ / Reply macro). Add a summary of how many tickets are deflectable and the hours that could be saved. Clean, light, one screen.

Store tickets as demo data. Use POST /v1/chat/completions to cluster ticket texts into named recurring questions. Compute counts, %, and hour estimates in code — not by the model.

API key: vibe_api_xxx (scopes: vibe:ai)
API Discovery: https://vibecode.bitrix24.com/v1/me