Skip to main content

Slack Error Messages

Errors you may see when sending Slack alerts from iPaaS.com, their causes, and how to resolve them.

Overview

This article catalogs the errors a subscriber or their MiSP can encounter when using the Slack integration, what causes each one, and how to resolve it. The Slack integration sends alert messages from iPaaS.com to a designated Slack member or channel. Errors are viewed under Dashboard → Integration Monitoring → Error Logs.

Each error carries a stable code you can search for on this page. The Slack integration makes a single kind of call to the Slack API, so every message-delivery and runtime authentication failure shares one code — SLCK-EXTN-1001 — and the specific Slack response shown after the code tells you which case you have. The connect-time authorization failure has its own code, SLCK-AUTH-1001.

Some resolutions reference your Managed Integration Service Provider (MiSP) — the partner who configured and maintains your Slack integration. Where a resolution goes beyond what you can adjust yourself, your MiSP is the first point of contact.

iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.

If an alert is not delivered and no error appears in the log, the message most likely did not meet the integration's delivery criteria or the content was automatically shortened — both are by-design behaviors described in the Slack Integration Known Limitations article rather than errors.

Supported Flows

  • Connection and Authorization

  • Slack API and Message Delivery (Message FROM iPaaS.com)

Error Collection

Connection and Authorization

Authorization could not be completed

SLCK-AUTH-1001 - Unable to complete OAuth process in ProcessAuthorization.

  • Description: The connection could not be authorized during setup, and the subscription does not reach an authorized state. This happens when the authorization handshake is incomplete or interrupted, when the authorization credentials for the integration are missing, or when Slack declines to return a usable access token for the workspace.

  • Resolution: Restart the authorization from the subscription's connection settings — click the lock icon, confirm you are signed in to the correct Slack workspace, and click Allow. If it continues to fail, confirm the API URL setting is correct and that the connecting account can install apps in the workspace, then try again. If authorization still cannot complete — for example if the message indicates the integration's client credentials are not configured — your MiSP owns the integration's OAuth configuration and can confirm it before you retry.

Slack API and Message Delivery

The failures below all surface through a single Slack API call and share the code SLCK-EXTN-1001. The Slack response shown after the code ({error} in the message) identifies which case applies.

Authentication failed

SLCK-EXTN-1001 - Error calling Slack CallWrapper.{action}: invalid_auth (also token_revoked, account_inactive)

  • Description: The stored credentials are no longer valid. invalid_auth means the token cannot be validated; token_revoked and account_inactive mean the app was removed, or the workspace or user the token belongs to is no longer active.

  • Resolution: Re-authorize the connection from the subscription settings using the preferred OAuth method, or supply a current Bot User OAuth Token if you use the Bot token method. Confirm the Slack application is still installed in the workspace.

Missing permissions

SLCK-EXTN-1001 - Error calling Slack CallWrapper.{action}: missing_scope (also no_permission)

  • Description: The authorized Slack application does not hold the permissions required to read the member list or post messages.

  • Resolution: Grant the Slack application the permissions required to post messages and read workspace members, then re-authorize the connection so the updated permissions take effect. If you do not manage the Slack app directly, your MiSP can arrange the scope change.

Wrong token type

SLCK-EXTN-1001 - Error calling Slack CallWrapper.{action}: not_allowed_token_type

  • Description: The API Token preset holds an app-level token (one beginning with xapp-, created with the App-Level Tokens "Generate Token and Scopes" option) instead of a bot token. The integration posts messages with a bot token, which an app-level token cannot do.

  • Resolution: Replace the API Token with the Bot User OAuth Token (it begins with xoxb-) from the Slack app's OAuth & Permissions page, then save the subscription. See the Slack Installation Instructions for the full bot-token setup.

Recipient not found

SLCK-EXTN-1001 - Error calling Slack CallWrapper.{action}: channel_not_found

  • Description: The recipient could not be resolved. Either the Channel mapping value did not match any workspace member (it matches member Name first, then Real Name), or it targets a private channel the iPaaS.com app has not been added to — the app cannot see a private channel until it is a member.

  • Resolution: For a member recipient, confirm the member exists in the connected workspace and that the Channel mapping value matches that member's Name or Real Name. For a private channel, add the app to it: in Slack, right-click the channel and choose View Channel Details, open the Integrations tab, click Add Apps, select the iPaaS.com app, and click Add. Then send the alert again.

Recipient cannot receive the message

SLCK-EXTN-1001 - Error calling Slack CallWrapper.{action}: not_in_channel (also is_archived)

  • Description: The Slack application is not a member of the target conversation, or the target conversation has been archived.

  • Resolution: Add the Slack application to the target conversation, or choose an active recipient. Archived conversations cannot receive new messages.

Too many requests

SLCK-EXTN-1001 - Error calling Slack CallWrapper.{action}: rate_limited

  • Description: Messages were sent to Slack faster than Slack's rate limits allow.

  • Resolution: No permanent action is required — reduce the volume or pace of alerts, or lower the API Throttle Limit for the subscription so requests are spread out. Slack accepts new messages again once the limit window resets.

Message rejected for length or an unexpected response

SLCK-EXTN-1001 - Error calling Slack CallWrapper.{action}: Invalid response code

  • Description: Slack rejected the request at the transport level rather than returning a named error — most commonly because the message was too long for Slack's request-size limit, or Slack returned an unexpected response.

  • Resolution: Shorten the alert content; see the Slack Integration Known Limitations article for the message-shortening behavior. If the failure persists on a normal-sized message, capture the error timestamp and ask your MiSP to review the mapping that produced the alert.

Related Documents

Related Articles
Did this answer your question?