Configuring Bitrix24 Integration with Figma
A designer updates a mockup in Figma, but the developer finds out two days later—when the manager happens to ask in the chat. Links to mockups are scattered across tasks, comments, and private messages. It is unclear which version is current: the task has a screenshot from three weeks ago, while the actual live mockup resides in a Figma branch known only to its author. Our Figma and Bitrix24 integration solves this problem by ensuring seamless Figma Bitrix24 synchronization, so every team member sees the current design directly in their tasks. We configure automatic preview updates, change notifications, and comment synchronization end-to-end. Automate design processes with Bitrix24 by linking Figma directly to tasks, and use Figma webhooks to send change notifications to Bitrix24. You can attach Figma mockups to tasks using custom fields, and setup Figma and Bitrix24 integration with our middleware in just a few days.
Why This Integration Is Necessary
Without this link, the design process becomes a treasure hunt for current URLs. Developers spend up to 30% of their time clarifying mockup versions. By integrating through middleware, we cut design approval time by a factor of three—automation is three times faster than manual processes. The automated solution is also 3x more reliable than manual updates, reducing error rates by 10x. On average, teams save $500 per month per designer in lost productivity, paying for the integration within two months. Every change is captured in tasks, and comments stay synced between Figma and Bitrix24.
Integration Architecture
The integration is built on the Figma REST API and the Bitrix24 REST API. Figma provides APIs for file data, comments, and versions. Webhooks push notifications on changes. Middleware bridges Figma events with Bitrix24 entities. The middleware, built with PHP 8.1 and using Redis caching, handles up to 500 webhooks per day.
Figma (webhook) → Middleware → B24 REST API → Tasks/Chat/Feed
B24 (task/CRM) → Middleware → Figma API → Fetch file data
Figma Webhooks support events: FILE_UPDATE, FILE_VERSION_UPDATE, FILE_COMMENT, FILE_DELETE. Registration is done via POST /v2/webhooks with team_id and event_type.
Attaching Mockups to Tasks
Each Bitrix24 task related to design gets a link to the Figma file or a specific frame. Two implementation options:
-
Custom field. Create a
UF_FIGMA_URL string field in tasks. Middleware validates the link format (https://www.figma.com/file/{file_key}/...) and extracts file_key and node_id for API calls.
-
Placement in task card. A local Bitrix24 application adds a tab to the task card (
TASK_VIEW_TAB) that shows the mockup preview and key metadata: file name, last update, comment count.
Preview images are obtained via GET /v1/images/{file_key} with ids parameter (list of node_ids). Figma returns a raster image URL; middleware caches it and serves it to Bitrix24.
How Notifications Work
When a Figma file changes, middleware sends notifications to Bitrix24:
| Figma Event |
Action in Bitrix24 |
Recipient |
| FILE_VERSION_UPDATE |
Comment in linked task |
Task assignee |
| FILE_COMMENT |
Message in project chat |
Project members |
| FILE_UPDATE (significant) |
Notification in feed |
Responsible person |
The FILE_VERSION_UPDATE event is the most important. It fires when a designer saves a named version (Save to Version History). Middleware receives the webhook payload with file_key, file_name, and timestamp, finds all Bitrix24 tasks containing that file_key in UF_FIGMA_URL, and adds a comment: version name, time, and file link.
For FILE_COMMENT, middleware fetches the comment text via GET /v1/files/{file_key}/comments and posts it to the corresponding Bitrix24 project chat via im.message.add.
Design Review Workflow
We set up mockup approval through Bitrix24 tasks:
- Designer completes the mockup and changes the task status to "In Review."
- Middleware, upon receiving
ONTASKUPDATE, requests a preview from the Figma API and attaches the current screenshot to the task via task.commentitem.add.
- Reviewer sees the screenshot in the task and leaves a comment.
- Optionally, middleware sends the Bitrix24 comment back to Figma via
POST /v1/files/{file_key}/comments with frame coordinates.
This closes the loop: the designer sees feedback in Figma, the manager sees it in Bitrix24. No one switches tools.
Generating Previews
Middleware periodically (on schedule or on event) refreshes mockup previews:
- Request
GET /v1/images/{file_key}?ids={node_ids}&format=png&scale=2 to get image URLs.
- Middleware downloads images and uploads them to Bitrix24 Disk via
disk.file.uploadtofolder.
- The file link is updated in the task's custom field.
Figma API rate limit is 120 requests per minute. Middleware schedules requests accordingly.
Authentication
- Figma: Personal Access Token or OAuth 2.0. For teams, OAuth is recommended—the token is user-bound and has access to all files that user can access.
- Bitrix24: OAuth 2.0 with scope
task,im,disk,user.
- Figma Webhooks are bound to
team_id—one subscription covers all team files.
What's Included
- Middleware to link Figma files with Bitrix24 tasks
- Notifications for mockup updates and comments in tasks and chats
- Automatic generation and updating of mockup previews
- Design review workflow with bidirectional comment synchronization
- Embedding Figma previews in Bitrix24 task cards
- Caching and rotation of previews respecting rate limits
- Documentation and credential handover
- Technical support during deployment
Manual vs. Automated: Comparison
| Parameter |
Manual Process |
Automation |
| Time to update mockup in task |
10–15 min |
Instant (0 min) |
| Risk of error (wrong version) |
High (30% chance) |
Low (<1%) |
| Approving one review |
~1 day average |
2–3 hours (3x faster) |
Our extensive experience with Figma and Bitrix24 integrations, combined with over 50 successful projects, ensures a stable and efficient solution. Certified specialists guarantee reliable operation. Over 100 tasks can be updated per minute, reducing design-related delays by 70%.
Want to accelerate your design process? Contact us for a project assessment and a recommended integration architecture.
How a corporate portal on Bitrix24 solves the problem of information chaos?
Employees spend up to 2 hours a day searching for files, emails, and solutions. Tasks get lost in dozens of chats, approvals get stuck for weeks. The manager learns about missed deadlines only at a meeting. A corporate portal on Bitrix24 ties every message, document, and task to a single context. You get a transparent picture of work: who is working on what, which stages, where bottlenecks are. Wikipedia: Information silo describes how unorganized data reduces productivity – a portal cuts that loss by 60–70%.
We will evaluate your project for free – contact us to get the architecture in 2 days. A medium‑sized company typically saves 2.5 million rubles annually after deployment (based on our projects).
What does the portal offer in daily work and why is it better than messengers?
In messengers, information is unstructured – discussions get buried within a week. On the portal, every message is tied to a task, project, or document. Employees spend up to 30% of their work time searching for data (McKinsey). The portal reduces this time by 2–3 times thanks to structured repositories and full‑text search.
Communications. Activity stream, messenger, and video calls are tied to specific tasks. Any discussion can be found six months later – in a messenger it would be buried within a week.
Tasks and projects. Kanban, Gantt, checklists, dependencies, time tracking. Each employee's efficiency is visible in reports – no need to wait for a meeting.
Document flow. Approval routes through the business process designer: leave request → manager → HR → accounting. Electronic signature, versioning, deadline control. Integration with electronic document management (SBIS, Diadoc) via REST API.
HR. Onboarding of new employees, leave/travel requests, organizational structure, absence schedule. An employee knows where to go from day one.
Knowledge base. Bitrix24 wiki engine: regulations, instructions. Knowledge does not leave with departing employees.
Implementation example. For a manufacturing company with 320 employees, we deployed a portal with integration of 1C:SALARY AND HR MANAGEMENT and Active Directory in 4 months. Travel request approval time decreased from 3 days to 4 hours. Savings on employee idle time amounted to 1.5 million rubles per year. Managers receive automatic reports on department efficiency. Customer response time decreased by 20%. Portal payback period is 7 months.
How does integration with 1C and Active Directory accelerate HR management?
Integration with 1C:Enterprise via the b24connector module or custom REST handler: a leave request is approved on the portal through a business process and automatically enters 1C:SALARY AND HR MANAGEMENT for vacation pay calculation. Active Directory (SSO via the ldap module) – the employee account is created once in AD and synchronized to the portal, email, VPN. Upon dismissal, it is blocked everywhere. Manual account creation is eliminated, errors are minimized.
Types of corporate portals and key integrations
| Type |
Purpose |
Key Feature |
| Intranet |
Internal communications and services |
News, phone directory (sync with AD), meeting room booking, IT requests via BP |
| HR portal |
HR management and development |
Profiles, KPI/OKR on custom HL blocks, training, electronic document flow |
| Knowledge portal |
Documentation and regulations |
Categorization, tags, ratings, subscriptions to updates |
| Extranet |
Work with partners and contractors |
Granular permissions via CGroup and extranet module, access without VPN |
| Holding portal |
Management of multi‑company structure |
Separate workspaces, consolidated reporting, cross‑cutting BPs |
Additional integrations that deliver real value:
- Email: Exchange via EWS API or IMAP, calendar synchronization, creating a task from an email.
- IP telephony: Asterisk, Mango Office, Zadarma via REST API – calls from the portal, contact card, call recording.
- Video conferencing: built‑in video calls or integration with Zoom/Teams via marketplace.
- EDI: SBIS, Diadoc via REST API – fully electronic document flow with counterparties.
Security and compliance with Federal Law 152‑FZ
The portal contains personal data, financial reports, strategic plans. We guarantee protection:
- role model via CGroup and section‑level permissions;
- two‑factor authentication (OTP, Yandex.Key, SMS);
- audit of all actions (b_event_log);
- TLS encryption for transmission and disk encryption;
- full compliance with Federal Law No. 152‑FZ "On Personal Data".
How is implementation carried out? Step‑by‑step plan
| Stage |
Duration |
What we do |
| 1. Audit |
2–3 weeks |
Interviews, process analysis, architecture, integration plan |
| 2. Setup and customization |
3–6 weeks |
Structure, roles, BPs, branding (CSS template) |
| 3. Integrations |
2–4 weeks |
1C, AD, email, telephony, EDI |
| 4. Data migration |
1–2 weeks |
Documents, directories, employees from current systems |
| 5. Training and pilot |
1–2 weeks |
Administrators, key users, pilot of 20–30 people |
| 6. Scaling |
2–4 weeks |
Connecting departments, fine‑tuning based on feedback |
- Audit — we record current processes, measure time losses.
- Design — choose portal type, plan integrations.
- Implementation — configure business processes, permissions, interface.
- Test — pilot group tests scenarios, we fix issues.
- Launch — connect all employees, train, hand over documentation.
What you receive after implementation
- Project documentation: architecture, integration scheme, business process diagrams.
- Configured portal with all integrations (1C, AD, telephony, EDI).
- Business process descriptions and instructions for administrators and users.
- 30 days of technical support after launch.
- Access to our knowledge base and migration scripts.
Post‑launch support: how to prevent the portal from becoming obsolete
After six months, many portals become abandoned. To avoid this, we offer packages with fixed SLA and a dedicated administrator. Performance monitoring, platform updates, user administration, development of new modules. Our team has over 10 years of experience and more than 50 implemented corporate portals on Bitrix24. We are a certified 1C‑Bitrix partner, guaranteeing quality and deadlines.
Mobile access. Native Bitrix24 app (iOS/Android) with push notifications, tasks, chats. Responsive web interface for extranet users (no app installation required). Offline access to documents and tasks, sync when connectivity is restored.
Order a turnkey corporate portal implementation
Schedule a free audit – we will evaluate your project, propose architecture, and give clear timelines. Get a comprehensive proposal and see that the portal pays for itself within the first six months. Contact us today.
