Webhook vs OAuth App at a Glance
| Inbound Webhook | OAuth (Local) App | |
|---|---|---|
| Setup Time | Minutes | Hours to days |
| Authentication | Secret URL tied to one user | OAuth 2.0 tokens with refresh |
| Acts As | The user who created it | The application, installed on the portal |
| Permissions | Scopes chosen at creation | Scopes declared by the app |
| Interface Inside Bitrix24 | None | Can add placements, tabs, and widgets |
| Events | Outbound webhooks for events | Event handlers bound by the app |
| Best For | Server-to-server feeds on one portal | Integrations that need UI or run on many portals |
Inbound Webhooks: Fast, Simple, Powerful and Blunt
- Created in minutes; no OAuth dance; perfect for server-to-server flows you control
- The URL is the credential: leak it and someone has your scopes until you rotate
- Tied to the creating user: their permissions, and death on their deactivation — create under a service account, always
- No embedded UI, no app-level event subscriptions
OAuth (Local) Apps: More Machinery, More Control
- Access + refresh token lifecycle — short-lived credentials instead of a standing secret
- Granular scopes; not bound to one human user's employment
- Placements: embed tabs and widgets in the portal UI
- App-level event.bind subscriptions that survive personnel changes
- Required path for anything distributable via Bitrix24.market
Our Recommendation Matrix
One-way lead feed from your website? Webhook, under a service account, with the URL in a secrets manager. Two-way ERP sync running for years? OAuth app — token rotation and user-independence justify the setup cost. Anything with UI inside Bitrix24? App, no choice. Quick internal script? Webhook, then delete it when done. When in doubt for production systems, we default to apps; for prototypes and internal tools, webhooks.
Security Checklist for Either Option
- Create the webhook or install the app under a dedicated service user, not a person's account
- Grant only the scopes the integration needs
- Store secrets and tokens in a secrets manager or environment config, never in code or spreadsheets
- Validate the application token on incoming event calls
- Log every call and alert on repeated failures
- Rotate webhook URLs when someone with access leaves