Add a custom tab inside the task screen so teams can see key task details in one place. The flow also completes the app install steps and keeps basic settings without a database. It suits teams that work in Bitrix24 and want a fast, simple view inside tasks.

Here is how it runs. A webhook receives calls from Bitrix24 and checks if the event is an install, a task tab open, or install finish. On install, it binds the task tab to your handler URL, saves a small settings file, and returns the install finish page. When a user opens the task tab, it reads the saved settings, calls the Bitrix24 API to get the task using the access token and the placement options, formats the result, and serves a clean HTML page. If anything fails, it sends an error page instead of breaking the view.

Setup is simple. You need a Bitrix24 app with placement and tasks rights and a public n8n URL. After install, every task shows a new tab that loads fast and highlights the fields you care about. Expect fewer clicks, faster checks, and less admin time for daily task work. Many teams use it to show task context, quick links, or status summaries right where work happens.

• Webhook endpoint receives Bitrix24 POST calls on a fixed path for reliable routing
• Event check logic routes install, task tab open, and install finish events correctly
• Automatic placement binding registers the task tab and points it to your handler URL
• File based settings store creates, writes, reads, and extracts a small JSON config
• Merges installation data with each request so later steps have all needed fields
• Task data fetch uses the Bitrix24 REST API with placement options and access token
• HTML responses serve install finish, task view, and friendly error pages
• Validation checks ensure settings exist before calling external APIs

• Reduce setup time from 4 hours to 30 minutes with a guided install flow
• Streamline task review by 40 percent by showing key fields in one tab
• Eliminate copy paste of task IDs as the widget reads placement options automatically
• Improve data accuracy by 90 percent with token and domain passed directly from Bitrix24
• Scale to thousands of task views since each request is stateless and fast

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Bitrix24. See the Tools Required section above for links to create accounts with these services.
3. Activate your n8n instance on a public HTTPS URL so Bitrix24 can reach your webhook.
4. Open the Webhook node and confirm the path and method match your plan. Keep the POST method and the provided path for consistency.
5. Copy the Production Webhook URL from the Webhook node. You will use this as the handler URL in your Bitrix24 app.
6. In your Bitrix24 developer console, create a custom app with the placement for the task view tab. Add scopes for placement and tasks. Set the handler URL to the n8n webhook URL you copied.
7. Install the app in your Bitrix24 portal. The first call should trigger the install flow and show the install finish page.
8. Optional credentials: If you prefer using a dedicated Bitrix24 credential, double click the HTTP Request nodes, then in the 'Credential to connect with' dropdown click 'Create new credential' and follow the on screen instructions.
9. Open any task in Bitrix24. A new tab should appear with the configured title. Click it to load the task details page served by n8n.
10. Check the n8n executions to confirm the settings file was created and the task data call returned a result. Fix any missing permissions in your app if the call fails.
11. Troubleshooting: If you see 401 errors, confirm your app scopes and that the access token is present in the request. If the tab does not appear, verify placement binding succeeded and the handler URL is reachable.