Third-Party Integrations
WaDesk connects to outside services in three ways. Pick the one that matches your goal — react to events, enable a first-party connector, or drive a workspace from your own software.
1. Webhooks (event-driven)
The most common integration. Register an HTTPS endpoint and WaDesk POSTs a signed JSON payload whenever an event fires — a new inbound message, a delivery/read receipt, a campaign finishing. Your server verifies the signature and reacts (push to a CRM, trigger a workflow).
Conversely, incoming webhooks let an outside system push an event into WaDesk to start a flow or send a message. See Webhooks for payload shapes and signature verification.
When to use it. You want to be notified the moment something happens, without polling — the reactive glue between WaDesk and your stack.
2. Native connectors (OAuth / API keys)
WaDesk ships first-party connectors you enable from workspace settings. Each stores its credentials encrypted and syncs through the platform's own services — no direct database access needed.
| Category | Services |
|---|---|
| CRM & commerce | HubSpot, Shopify, WooCommerce — two-way contact/order sync and invoice sharing. |
| Productivity | Google (Calendar & Sheets), Slack, Trello — all signature-verified. |
| Payments | A large set of pluggable payment drivers for checkout; each is a self-contained driver class. |
| AI providers (BYOK) | Bring your own OpenAI / Anthropic / other keys per workspace; the platform resolves the workspace key first, then the admin key. |
When to use it. The service is already supported — connect it in a few clicks and let WaDesk handle the sync.
3. Drive WaDesk from your app (REST API)
When you want your software to control a workspace — send messages, sync contacts, launch campaigns — use the REST API with a workspace key. This is the right choice for a custom portal, a backend job, or a mobile app. See API Endpoints for the full map.
When to use it. You are building something that acts on a workspace, on your own schedule.
Extending the platform itself
If you are adding a brand-new provider, payment driver, or connector to the codebase (not just calling the API), read the Customization Guide and Architecture Overview first — they show where driver classes, service bindings, and the Node bridge hook in.