Figma-Bitrix24 Integration: Automate Design Workflows

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:

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:

1. Designer completes the mockup and changes the task status to "In Review."
2. Middleware, upon receiving ONTASKUPDATE, requests a preview from the Figma API and attaches the current screenshot to the task via task.commentitem.add.
3. Reviewer sees the screenshot in the task and leaves a comment.
4. 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

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.