WhatsMine Documentation
Home
  • What is WhatsMine?
  • Feature Tour
  • Requirements
  • Installation
  • Configuration (.env reference)
  • Going Live Checklist
Admin Guide
User Guide
Integrations
  • Architecture
  • REST API v1
  • Production Deployment
  • Frequently Asked Questions
  • Troubleshooting
  • Changelog
Home
  • What is WhatsMine?
  • Feature Tour
  • Requirements
  • Installation
  • Configuration (.env reference)
  • Going Live Checklist
Admin Guide
User Guide
Integrations
  • Architecture
  • REST API v1
  • Production Deployment
  • Frequently Asked Questions
  • Troubleshooting
  • Changelog
  • Admin Guide

    • Admin Guide Overview
    • Admin Dashboard
    • Clients
    • Plans, Coupons & Tax
    • Subscriptions & Payments
    • Payment Gateways
    • Currencies & Languages
    • Email System
    • Branding & Settings
    • Site Content (Marketing Site & Pages)
    • Support Tickets
    • Roles, Permissions & Admin Users
    • Integrations (Admin)
    • AI Dashboard
    • System Tools

Integrations (Admin)

The Integrations hub is where you store the credentials for every third-party service the platform uses — Meta, AI providers, OAuth logins, storage, Google services and more. They're stored encrypted in the database and can be tested with one click.

Location: Admin → Integrations (/admin/integrations)

📸 Screenshot: The Integrations hub with providers grouped by category.

System-level vs. workspace-level credentials

Credentials you set here are the platform defaults. Customers can optionally override some of them (AI keys, SMS providers, their own email server) within their workspace. WhatsMine always checks for a workspace override first, then falls back to your system defaults. This means you can provide a working experience out of the box and let advanced customers bring their own keys.

How it works

Each integration is a provider with its own credential fields. The hub shows every provider grouped by category, with its status: enabled/disabled, test/live mode, configured or not, and the result of the last connection test.

Common actions

ActionWhat it does
EditEnter or update the provider's credentials.
TestVerify the credentials by connecting to the service.
ToggleEnable/disable the integration without deleting credentials.
RotateRegenerate a webhook verify token / credential.
Set defaultMark this provider as the default for its category (e.g. default storage).
Audit logSee who changed what and when.

Credentials are masked after saving — when you edit, existing secrets are preserved unless you type a new value over the masked field.

What you can configure here

CategoryProviders
MessagingMeta App (WhatsApp / Instagram / Messenger / Facebook)
AI / LLMOpenAI, Anthropic (Claude), Google Gemini
Social OAuthFacebook, Instagram, LinkedIn, X/Twitter, YouTube, TikTok
GoogleGoogle Workspace (Calendar/Sheets/Docs/Forms), Google Places (leads)
E-commerce OAuthShopify, BigCommerce
StorageLocal disk, Amazon S3, DigitalOcean Spaces, Wasabi

Some integrations live elsewhere

A few credentials are managed on dedicated screens rather than the Integrations hub:

  • Payment gateways → Payment Gateways
  • Platform email (SMTP) → Email System
  • Real-time (Pusher) → System Tools → Real-time
  • SMS providers are configured per workspace by the customer (Broadcasting).

Security

  • All credential fields are encrypted at rest with the application key (APP_KEY).
  • Every change is recorded in the integration audit log with the admin's identity and timestamp.
  • Webhook verify tokens are separate from API keys and can be rotated independently.

Setting up each integration

Each service has a dedicated, step-by-step setup guide in the Integrations section:

  • Meta / WhatsApp
  • Messenger & Instagram
  • AI Providers
  • Social Networks
  • Google (Workspace & Places)
  • E-commerce
  • Storage

➡️ Next: monitor AI usage across the platform in the AI Dashboard.

Last Updated: 6/19/26, 4:34 PM
Prev
Roles, Permissions & Admin Users
Next
AI Dashboard