Platform · Error reference

What that toast actually means.

The error strings you'll see across integrations, grouped by theme and paired with a short, actionable resolution. For vendor-specific codes, see the integration's own page.

  • Cross-integration patterns, not an exhaustive catalog
  • OAuth, credentials, webhooks, delivery, mail watch
  • Vendor-side errors flow through verbatim
Try MessageMind free Jump to reference
Documentation Platform fundamentals Error reference

Platform integration

Error reference

  • CategoryPlatform

Overview

Error strings in MessageMind surface in three places: dashboard toasts after a save or connect click, inline validation under fields in the Integrate modal, and webhook response bodies when a vendor rejects a payload. This page consolidates the error messages that recur across multiple integrations, so an operator who sees a toast can look up what it means and what to do next without hunting through the per-vendor pages.

Limitations

  • This page lists cross-integration patterns, not an exhaustive error catalog. For vendor-specific error codes (HubSpot property conflicts, Shopify webhook signature failures, Twilio error 21211, Meta template rejection reasons) see the troubleshooting block on the integration's own documentation page.
  • Vendor-side errors flow through MessageMind as-is. If HubSpot returns 409 CONFLICT or Shopify returns 422 Unprocessable Entity, MessageMind surfaces the vendor message verbatim in the toast rather than rewriting it, so searching the vendor's docs for the string is often the fastest path.
  • Rate limit behaviour differs by vendor: some integrations surface a 429 with Retry-After and MessageMind backs off automatically, others surface a 403 or a vendor-specific quota error that requires a plan upgrade on the vendor side. Check the specific integration page before assuming a retry will succeed.

Troubleshooting

Please provide both Client ID and Client Secret.

The Integrate modal validates that both OAuth credential fields are non-empty before it will submit. Paste the Client ID and Client Secret from the vendor's developer console; whitespace-only values also trip this check, so trim before pasting.

Invalid SID Provided or Invalid Token Provided.

The Account SID or Auth Token pasted into the Twilio connect form does not match a live Twilio account. Copy the values fresh from console.twilio.com (Account Info panel) and retry; if the Auth Token was recently rotated in Twilio, the old value in MessageMind will fail and must be replaced.

The Auth Token was rotated in Twilio and inbound events stop verifying.

Twilio signs inbound webhooks with the current Auth Token; after a rotation the old signature no longer matches. Open the Twilio integration page in MessageMind, paste the new Auth Token, and save, then send a test message to confirm inbound events verify again.

Failed to connect Salesforce.

The OAuth callback came back with ?salesforceSuccess=false. Most common causes are a mismatched Callback URL in the Salesforce Connected App, a sandbox vs production URL mismatch, or the user cancelling the Salesforce consent screen. Re-check the Connected App's Callback URL exactly matches the one shown in the MessageMind modal and retry.

The OAuth popup opens and closes without connecting.

This is almost always a browser popup blocker or a third-party cookie block. Allow popups from the MessageMind dashboard, disable aggressive tracking protection for the integration tab, and retry. If the popup closes instantly, the vendor rejected the client_id, usually because the OAuth app is still in draft or sandbox mode.

Authorization was canceled or closed.

The Facebook or Google consent window was closed before granting permission, or the vendor cancelled the handshake. Re-open the wizard, click Continue, and make sure every requested scope is left checked on the consent screen; unchecking a scope is treated as a cancel.

Google says the app is not allowed on this Workspace.

A Workspace admin has restricted which third-party apps users can authorize. Ask the admin to allowlist the MessageMind OAuth client ID in Google Admin, Security, API controls, App access control, then retry the connect flow.

Microsoft says the app needs admin consent on this tenant.

The requested Graph scopes include at least one that requires tenant-wide admin consent. Send the admin consent URL shown in the modal to a Microsoft 365 Global Admin; once they grant consent, every user in the tenant can connect without re-prompting.

Registration with Meta failed. Check your two-step PIN or try again later.

The WhatsApp number has a two-step verification PIN that Meta cannot bypass during the embedded signup. Open the WhatsApp Business app on the device, remove or re-enter the two-step PIN, then retry the Add WhatsApp wizard.

Meta couldn't add this number through the API.

Fall back to adding the number manually. In Facebook Business Suite open WhatsApp, Phone numbers, add the number there, then return to /channels/whatsapp in MessageMind and the number will sync on the next refresh.