Bitrix24 widgets and apps
When the standard card is not enough: I add the needed interfaces, buttons and external-system data right where the manager works.
When you need it
What's included
How I work
- 1Analysis of the manager scenario
- 2Choosing the widget type (tab / toolbar / SPA)
- 3Development and connection to portal data
- 4Logs and error handling
- 5Demo and acceptance
What the client gets
- The needed data right in the card
- One-click actions
- Less switching between systems
- A clear step-by-step interface for complex processes
Risks and limits
- Depends on the Bitrix24 edition and access
- Heavy logic is moved to D7 separately
- The look is limited by the portal capabilities
Approximate work formats
If the project is old, without logs or documentation, with unknown integrations or production risks — an audit comes first. Otherwise any exact estimate is just guessing.
What I will need to work
- Minimal access to the system: Bitrix24 / repository / staging
- Access to logs if the task is about errors
- Description of the business scenario and expected result
- For integrations: API docs, test keys, payload examples
How I handle access
- I do not ask for excessive rights
- Tokens and keys are never sent to public chats
- For production changes — a separate user and a backup when there is risk
- After completion access can be revoked
Related cases
FAQ
Why is a widget better than a separate site?
The manager works in one Bitrix24 window, while the data and actions are right in the card.
Box or cloud?
Both: cloud — apps via REST, box — on D7.
Can external-service data be shown?
Yes, in a tab/card via an integration with logs and secret protection.
Not sure where to start?
Just describe the problem. I will study the current solution, assess the risks and propose implementation options.