Connect an app

Check Settings > Integrations for the apps and actions enabled in your workspace. Public integration pages do not confirm availability in your account.

Connect your own consoleCopy Anchor Link

If your product already has a customer console, use the Developer API and official Node.js SDK from your backend. Send messages through a number-bound key, read conversations and message status, stream permitted attachments, and consume signed events. Incoming conversations also remain in Waaru Inbox. Your backend must authorize each console user; do not expose the machine key in a browser. This path is configured in Settings > Developer, separately from connected app OAuth grants.

Review MCP connectionsCopy Anchor Link

Start with the dedicated MCP client guide for OAuth setup, bootstrap reads, capability review and confirmed actions. MCP does not use the Node.js SDK's API key or enable native AI replies.

When Settings > Developer > MCP is available in your release, it shows the MCP approvals you granted for the selected workspace, their client IDs and exact approved scopes. The server URL comes from the API's public discovery metadata. Manage connected apps opens the existing disconnect controls. An approval record does not prove that a client is connected or that refresh works.

When capability setup is available, choose what your app should help with in Settings > Developer > MCP, then copy its setup request into your connected AI app. Read access, customer support and campaign actions are grouped separately. Claim conversations as yourself takes eligible unassigned work; Reply to customers permits reviewed replies. Claiming sends no message. See the claim and reply steps. Optional choices start empty; scheduling explicitly includes ongoing access. Selecting or clearing choices does not change existing approvals. A listed tool can still require additional approval before it runs. The app needs a permission review; refresh its tools afterward, or use its reconnect flow if it does not support the review. Your workspace role and the application’s approved capabilities remain limits.

Choose optional actions on the first OAuth permission screen; a second connection is not required to approve initial writes. Workspace and number reads are required, while optional choices start unchecked. Contacts, messages, sends, broadcasts and template edits require their own approved permissions. request_permissions can request a named workflow; it cannot approve access or perform the action. Cancelling consent leaves existing access unchanged. Your role and the application's approved scope ceiling still apply.

Template definition changes use preview_template_update followed by confirm_template_update. Review the complete replacement before confirming: it affects every number in the template's WhatsApp business account and can remove its approval. This requires unrestricted number access and separately approved mcp:templates:read / mcp:templates:write scopes. Uncertain results require a template sync before another review; do not repeat the provider edit automatically. Template creation and deletion remain dashboard tasks.

Stored approvals and local tests do not establish Codex Mac or ChatGPT web acceptance. Verify login, reads, permission-review cancellation and the required host confirmation in your actual client before relying on it. Real sends and schedules also need review of the exact sender, audience, content and time.

Codex CLI bootstrapCopy Anchor Link

Codex CLI 0.162.1 can request the issuer’s entire permission catalog during automatic URL-only login. That can fail before capability setup. Configure the URL without starting login first: add the following to ~/.codex/config.toml, keeping your other entries. Replace the example URL with the server URL copied from Settings > Developer > MCP.

[mcp_servers.waaru]
url = "https://YOUR-API-ORIGIN/mcp"

Then run this exact initial login command; it asks only to view the workspace and allowed numbers:

codex mcp login waaru --scopes mcp:workspace:read,mcp:instances:read

For this version, codex mcp add --url starts OAuth before a later scoped login can constrain it. The configuration entry avoids that first automatic login. After connecting, use the plain-language capability choices and review the actual new request. Codex desktop URL-only sign-in is a separate acceptance check and remains unverified here; these CLI steps do not prove the desktop flow.

Connect an available appCopy Anchor Link

1. Open Settings, then Integrations.
2. Select the app and read its current status.
3. If setup is available, select Connect or the displayed setup action.
4. Complete the provider authorization without sharing credentials in notes or chat.
5. Return to Waaru and confirm the connected account and granted scope.
6. Run a safe test before using the connection in a published flow.

If the page marks an app as coming soon or does not offer setup, do not build a production dependency on it yet.

Use events and actionsCopy Anchor Link

Connected app events can start an Automation flow when they appear in the trigger catalog. Connected app actions can appear in Automation or Logic Flow editors when the workspace connection and catalog allow them.

Choose the smallest action and account scope required. Add a failure branch or Inbox handoff when an external outage would otherwise leave a customer waiting. Reauthorization, provider permission changes, and expired credentials can make a previously published action unavailable.

Disconnect safelyCopy Anchor Link

Find every active flow that references the connection before disconnecting it. Deactivate or replace those paths, then remove the connection through the available control. Historical run records remain part of the workspace audit trail.

Follow the connection-specific setupCopy Anchor Link

• Google accounts and resources: Sheets, Calendar, Drive and Contacts.
• Commerce, CRM and booking apps: Shopify, WooCommerce, Razorpay, Shiprocket, Zoho CRM, Cal.com and external automation platforms.
• Custom HTTPS connections: verification, typed methods and revisions.
• Connected actions: account selection, input/output mapping and uncertain outcomes.

A connector still needs your account's provider authorization and required resources before you can use it. If setup is unavailable, use Waaru Care to confirm its status instead of guessing credentials or an endpoint.

Next: Build an Automation flow or use an integration action in a Logic Flow.