Platform guide

Integrations & API Scope

See which connected workflows are publicly documented and what must be confirmed before building an external integration.

DeskGo product guideNo API setup required

What this service does

DeskGo connects selected product workflows through configured providers and company settings. This documentation describes the publicly supported product surface without implying an unpublished REST API, webhook contract, bank connector, or accounting integration.

Start with the workflow you need. DeskGo is modular, so a company can enable this service without being required to use every other DeskGo module.

Who it is for

Teams evaluating WhatsApp Business, payment, data-import, or future integration requirements before onboarding.

Recommended setup

  1. Identify the workflow

    Describe the exact business event, source system, destination, data fields, owner, and failure-handling requirement before requesting an integration.

  2. Use supported configuration

    Configure the DeskGo workflow and provider connection available for the selected service, such as WhatsApp Business or payment collection where enabled.

  3. Protect access

    Keep provider ownership, credentials, permissions, customer consent, and company data boundaries under an authorized administrator.

  4. Confirm external contracts

    Request current API, webhook, import, export, device, or accounting-integration documentation from DeskGo before engineering against it.

Main workflows

Workspace access

Use cloud browser access to the DeskGo workspaces authorized for the company and user.

WhatsApp Business

Connect WhatsApp Business and use team workflows where the company has enabled and authorized the service.

Payment collection

Use configured payment collection and Razorpay-related flows where they are enabled for the company.

Company-controlled data

Use available imports, exports, reports, and documents while keeping ownership and access within the company workflow.

Integration review

Review integration requirements and current technical scope before implementation against an external system.

Important controls

No public REST API contract is claimed here

Review this control during setup and whenever the company changes its workflow or team responsibilities.

No bank or accounting integration is claimed without current product scope

Review this control during setup and whenever the company changes its workflow or team responsibilities.

Provider credentials remain company-controlled

Review this control during setup and whenever the company changes its workflow or team responsibilities.

External integrations require an authorized technical review

Review this control during setup and whenever the company changes its workflow or team responsibilities.

Frequently asked questions

Can I build against a public DeskGo REST API today?

Do not assume that. A public API contract is not documented on this page; contact DeskGo for current availability and access requirements.

Does DeskGo support WhatsApp Business?

Yes, where the company connects an authorized WhatsApp Business workflow and enables the relevant services and permissions.

Does DeskGo support bank or accounting connectors?

Do not rely on a connector unless it is shown in the current product or written integration scope. Ask DeskGo before promising it to a customer.