Custom Vue.js interfaces for Bitrix24 Smart Processes

The standard Smart Process form in Bitrix24 is just a copy of the CRM form. It does not support dynamic steps, dependent fields, or visual progress. When a business requires multi-stage approvals with branching or custom validation, the standard interface falls short. Vue.js solves these problems: we create placement applications that completely replace the Smart Process form. Over 10 years, we have developed more than 50 interfaces for Bitrix24 — from simple single-step forms to complex CRM add-ons integrated with 1C, YooKassa, and CDEK. Each project starts with a business process audit and ends with documentation and administrator training. On average, development takes 4 to 20 working days, and the time saved on approvals reaches 40%. The cost of a basic interface starts at $4,000, and annual savings can reach $15,000. In this article, we'll break down how we design multi-step interfaces for Smart Processes: from retrieving stages to launching business processes, and why a custom Vue.js UI reduces modification costs by 2-3 times.

Problems we solve

• Non-standard step sequences. In the standard interface, stages are linear. For complex scenarios (leave request with branching, contract approval with multiple signatories), a dynamic step-by-step UI is required.
• Complex field logic. Dependent lists, conditional rendering, client-side validation — all go beyond the capabilities of UF field settings.
• Visual control. Clients want to see stage statuses, who approved, and which documents are attached. The standard interface does not provide this.

How Vue.js integration with Bitrix24 works?

Vue.js is an ideal choice for Bitrix24 placement applications. Lightweight framework, fast reactivity, and the ability to use components from the ecosystem. Unlike React, Vue is easier to embed in an iframe and does not require complex build configuration. The component architecture allows reusing form steps, and Pinia provides centralized state management.

A typical case is an approval form with multiple steps, each corresponding to a Smart Process stage:

<!-- SmartProcessWizard.vue -->
<template>
  <div class="wizard">
    <StepIndicator :steps="steps" :current="currentStep" />

    <Transition name="slide" mode="out-in">
      <component
        :is="currentStepComponent"
        :key="currentStep"
        :item="store.item"
        @next="handleNext"
        @back="handleBack"
        @save="handleSave"
      />
    </Transition>
  </div>
</template>

<script setup>
import { computed } from 'vue'
import { useSmartProcessStore } from '@/stores/smartProcess'

const store = useSmartProcessStore()

const steps = [
  { id: 'initial', label: 'Initial Data', component: StepInitial },
  { id: 'approval', label: 'Approval', component: StepApproval },
  { id: 'documents', label: 'Documents', component: StepDocuments },
  { id: 'completion', label: 'Completion', component: StepCompletion },
]

const currentStep = computed(() => store.currentStep)
const currentStepComponent = computed(
  () => steps.find(s => s.id === currentStep.value)?.component
)

async function handleNext(data) {
  await store.saveStepData(data)
  store.nextStep()
}
</script>

Technical aspects: stages, fields, rights

Retrieving the list of stages for a Smart Process is done via crm.status.list with a filter for ENTITY_ID = DYNAMIC_{entityTypeId}_STAGE. Each stage has a color and name — these can be used for visual indication. For example, a progress indicator displays the current stage with its color.

UF fields of Smart Processes have a prefix ufCrm_{entityTypeId}_. To work with enumerations, userfield.enumvalues.get is used. Example of retrieving and updating a field:

// Getting and updating UF field
const item = await callMethod('crm.item.get', {
  entityTypeId: 1040,
  id: itemId
})
const customDate = item.ufCrm_1040_1704067200   // type date
await callMethod('crm.item.update', {
  entityTypeId: 1040,
  id: itemId,
  fields: { ufCrm_1040_1704067200: '2023-01-01' }
})

Checking permissions is done via crm.type.get. The userPermissions field shows which actions are available to the current user. A simple check is implemented in the Vue component:

async function checkPermission(entityTypeId, action) {
  const result = await callMethod('crm.type.get', { id: entityTypeId })
  const userRole = result.userPermissions?.[action]
  return userRole !== 'NONE'
}

Automation and change history

Launching a BP from the interface is done via bizproc.workflow.start. The document is passed in the format ['crm', 'CCrmDocumentDynamic', '{entityTypeId}_{itemId}']. Template parameters are specified in PARAMETERS. The status of the running process is tracked via bizproc.workflow.instances.

await callMethod('bizproc.workflow.start', {
  TEMPLATE_ID: templateId,
  DOCUMENT_ID: ['crm', 'CCrmDocumentDynamic', `${entityTypeId}_${itemId}`],
  PARAMETERS: {
    approver_id: selectedApproverId,
    deadline: deadlineDate,
  }
})

To build an event timeline, methods crm.timeline.bindings.list and crm.activity.list are used. Each event contains a date, author, and description — this data is displayed in a custom timeline component.

What's included in the work

• Business process audit and technical specification
• Prototyping of a multi-step form
• Vue application development (Vue 3, Pinia, Vite, TypeScript)
• Integration with Bitrix24 REST API (crm.item, crm.status, userfield)
• Setting up access rights and BP triggering
• Documentation and administrator training
• 3-month warranty support

Comparison: standard interface vs custom Vue.js

Vue.js — one of the most popular frameworks for building reactive interfaces, confirming its reliability for enterprise solutions.

Development process and timelines

Custom interface development goes through five stages:

1. Analysis — study the business process, define stages, fields, and roles.
2. Design — create a multi-step form prototype.
3. Development — write the Vue application (Vue 3, Pinia, Vite, TypeScript), integrate with REST API.
4. Testing — test on 20+ scenarios including edge cases.
5. Deployment and training — deploy the placement application, hand over documentation.

Timelines:

• Simple interface (single-step form, basic logic) — from 4 to 6 working days.
• Complex solution (multi-step approval, BP, external integrations) — from 2 to 4 weeks.

Cost is calculated individually after project assessment. We guarantee code quality and adherence to deadlines.

Why choose custom interfaces?

A custom Vue.js interface solves problems that standard CRM cannot handle: it adapts to unique business processes, reduces approval time 2-3 times faster, and decreases the workload on managers. Built-in analytics and visual progress improve transparency.

Our company has over 10 years of experience and 50+ successful projects. For Bitrix24 Smart Processes, Vue.js provides the best custom interface. Our custom Vue UI is 3 times more efficient than standard forms. Starting from $4,000, you get a solution that saves up to $15,000 annually. Compare that to standard forms — our custom Vue.js interface is 3 times more efficient. Contact us for a free project assessment in 1 business day.

Why Does CIBlockElement::GetList Kill UX and What Does Vue Have to Do with It

We’ve seen standard bitrix:catalog.section component reload the entire page on every filter click. Full cycle: PHP parses the infoblock, collects properties from b_iblock_element_property, renders HTML, sends to client. On a catalog with 50,000 SKU, this takes 800–1200 ms. Customer clicks three filters — three reloads, 3 seconds of waiting. In e-commerce, this directly leads to up to 20% conversion loss. Vue.js solves this specific problem: the frontend fetches data via REST API, renders on the client, filtering is instant. Bitrix remains the backend: content, catalog, orders, 1С exchange. Our team has been implementing this approach for over 7 years and we consistently see a 3–5x speed improvement. According to Vue.js documentation, “Vue allows creating reactive user interfaces with minimal effort.”

Vue.js development for 1С-Битрикс is not a trendy framework but a way to turn a heavy monolithic interface into a responsive one. We apply it to projects with catalogs from 10,000 SKU and guarantee page load time under 400 ms after implementation. Certified Bitrix developers with 10+ years of experience ensure stable integration. Get in touch for a free project assessment — we’ll evaluate how much your site can benefit from Vue.js development.

When Is Vue Justified?

Not every site needs a frontend framework. Vue is justified when standard Bitrix components cannot keep up. Main scenarios:

• Catalogs with heavy filtering — catalog.smart.filter with AJAX works, but on complex SKU-property combinations it slows down. Vue + API = instant response. In one of our client projects, a catalog with 80,000 items loaded 60% faster after switching to Vue.
• Personal accounts — full-featured SPAs with dashboards, charts, reactive forms. sale.personal.section looks outdated.
• Configurators and calculators — visual editors, configuration selectors with real-time price calculations.
• Real-time — chats, notifications, stock updates via WebSocket.
• PWA — offline mode, push notifications, home screen installation.

How Does Vue.js Solve UX Problems in Bitrix?

Comparison: standard bitrix:catalog.section component filters 50,000 items in 800 ms + page reload. Vue widget based on REST API renders the same list in 200–300 ms without reload — that’s 3–4 times faster. In our practice, a client achieved a 35% increase in average session depth after implementation. Savings on server infrastructure can reach $3000 per month. The cost of such a project is calculated individually, and we will provide a detailed estimate after analyzing your site.

What Are the Three Architectural Approaches to Integrating Vue.js with Bitrix?

Island — Vue Widgets on Bitrix Pages

Individual Vue components are mounted into div#app-filter, div#app-cart on standard Bitrix pages. Routing and server-side rendering remain with Bitrix. Minimal intervention into the existing site.

Suitable for gradual modernization when you need to add interactivity without rewriting. A typical example is a reactive filter replacing catalog.smart.filter. In one of our projects, we replaced the filter with a Vue widget in 2 weeks, conversions increased by 18%.

SPA on Vue + Bitrix REST API

Frontend — a full-featured Vue application with Vue Router. Bitrix provides data via REST API: either the standard rest module or custom D7 controllers. Bitrix admin panel manages content; the editor sees no difference.

Ideal for personal accounts, B2B portals, and internal applications where SEO is not critical.

Nuxt.js + Bitrix as Headless CMS

Nuxt provides SSR/SSG for indexing. Bitrix is headless: it returns data via API and manages content. For stores and content-heavy sites where SEO is a priority. We use Nuxt 3 with Vue Router for hybrid rendering — catalog statically, cart SSR.

Applied to projects requiring maximum loading speed and full indexing. Savings on licenses and servers can be substantial.

What Bitrix REST API Features Matter for Vue Development?

This accounts for 70% of time when integrating Vue + Bitrix.

Standard REST Module

Infoblocks, catalog, cart (sale.basket.*), orders (sale.order.*), users — out of the box. Limitation: standard methods do not always cover custom logic. The catalog.product.list method does not return computed properties — a custom endpoint is needed.

Custom D7 Controllers

The Bitrix\Main\Engine\Controller class is the proper way to create an API for Vue. Automatic parameter validation, CSRF protection out of the box, typed responses. Not ajax.php with $_POST — that leads to injections.

namespace App\Controller;
use Bitrix\Main\Engine\Controller;

class CatalogController extends Controller
{
    public function getProductsAction(array $filter, int $page = 1): array
    {
        // ORM query to infoblock, not CIBlockElement::GetList
    }
}

Authorization and Caching

Authorization: OAuth 2.0 for SPA or session tokens. Rate limiting — via Bitrix\Main\Engine\Controller or nginx. Caching: API responses are cached at the D7 level with tagged invalidation. Product changed in infoblock — cache cleared by tag iblock_id_X. Without this, at 100 RPS the server will crash. We configure this in every project — guarantee of stability under load.

Example of configuring tagged caching for API:

use Bitrix\Main\Data\Cache;

$cache = Cache::createInstance();
$tag = 'iblock_id_' . $iblockId;
if ($cache->initCache(3600, md5($filter), $tag)) {
    return $cache->getVars();
}
// database query
$cache->startDataCache();
$cache->endDataCache($data);
\CIBlock::registerWithTagCache($iblockId);

Structure of Vue Application for Bitrix

• Vue Router — lazy loading routes via defineAsyncComponent. Catalog does not pull in personal account code.
• Pinia — state management: catalog, cart, user, filters. Modular store architecture. Vuex is legacy; new projects use Pinia.
• Axios with interceptors: automatic CSRF token refresh, retry on 503, error handling for authorization.
• Vue Query (TanStack Query) — caching API requests, automatic revalidation, optimistic updates. User adds item to cart — UI updates instantly, API request goes in background.

Catalog on Vue — Key Use Case Breakdown

The difference in UX is immediately noticeable. Specifics:

• Filter — checkboxes, range sliders, select with search. State synced with URL via vue-router query params — filter link can be shared.
• Product card — gallery with zoom, SKU switching (color/size), price recalculated via API catalog.product.offer.list, stock from catalog.store.product.list.
• Virtual scrolling — vue-virtual-scroller renders only visible items. Catalog of 10,000 items works smoothly.
• Smart search — debounced queries to search.title.search or ElasticSearch, autocomplete via dropdown. In our project, this reduced search time by 40% compared to the default Bitrix search.
• Comparison — dynamic characteristics table with difference highlighting. Storage in Pinia + localStorage for persistence.

How We Implement Vue.js: Step-by-Step Plan

1. Audit current Bitrix architecture and identify bottlenecks (filtering, cart, personal account).
2. Design API — define endpoints, data models, use Bitrix\Main\Engine\Controller.
3. Develop Vue widgets or SPA — build with Vite, Code Splitting, Pinia.
4. Integrate with Bitrix — tagged caching, OAuth, error handling.
5. Load testing (up to 100 RPS) and deploy with CI/CD.

Performance is achieved through code splitting, tree shaking, and lazy loading of heavy components (Chart.js, maps, WYSIWYG). Catalog page bundle is 80–120 KB gzip.

How Does Nuxt.js and SEO Preserve Indexing?

A pure Vue SPA returns an empty HTML with <div id="app"></div> to search engines. Google can render JS but with days-long delay. Yandex is unpredictable. Nuxt.js solves this:

• SSR — server returns full HTML, after hydration works as SPA.
• SSG — pages generated on nuxt generate, served from CDN. Maximum speed.
• Hybrid mode — catalog static, cart and personal account SSR.
• useHead() — dynamic title, description, Open Graph, Schema.org for each page.
• Sitemap — @nuxtjs/sitemap, routes from Bitrix API. This ensures full indexing — our guarantee for top-5 Google ranking.

Approach Comparison and Timelines

Full cycle: API design, D7 controller development, Vue application, Vite setup, testing, deployment. Code is reviewed, tested, documented — not "build and forget." The development cost is calculated individually and depends on integration complexity (typical range varies). You will receive a detailed estimate after analyzing your current site and technical specifications.

Common Mistakes When Integrating Vue.js and Bitrix

1. Using ajax.php instead of Bitrix\Main\Engine\Controller — leads to vulnerabilities and instability.
2. Lack of tagged API caching — server cannot handle high load.
3. Ignoring OAuth authorization for SPA — session tokens may expire, breaking UX.
4. Rewriting the entire site as SPA unnecessarily — increases timeline and budget.
5. Incorrect Nuxt SSR configuration — slow page generation on backend.

What We Deliver and Our Guarantees

• API documentation (Swagger/OpenAPI) for integration with your backend.
• Code repository access and CI/CD pipeline.
• Team training on Vue component usage and maintenance.
• 1 month post-release support — stability guarantee.
• Code complies with PSR-12 and Bitrix\Main\Engine\Controller standards.

Our track record: 100+ successful Bitrix projects, 10+ years of Bitrix development experience, 7 years of Vue + Bitrix integration practice. We deliver turnkey solutions — from a simple filter widget to a full Nuxt.js headless store.

Order Vue.js interface development for your Bitrix project — get a consultation and timeline estimate within a day. Contact us, and we will send a commercial proposal with a detailed work plan. We will assess your project free of charge — just send your technical specification or current site link.