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. Errors are viewed under Dashboard → Integration Monitoring → Error Logs.
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.
Connection and Authorization Errors
Authorization Could Not Be Completed
What you see: the connection cannot be authorized during setup, and the subscription does not reach an authorized state.
Cause: an incomplete or interrupted authorization handshake, missing authorization credentials, or Slack declining 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 it still does not complete, contact iPaaS.com Support at support@ipaas.com.
Authentication Failed
What you see: invalid_auth, token_revoked, or account_inactive in the error log.
Cause: the stored credentials are no longer valid. invalid_auth indicates the token cannot be validated; token_revoked and account_inactive indicate 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
What you see: missing_scope or no_permission in the error log.
Cause: 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.
Wrong Token Type
What you see: not_allowed_token_type in the error log when the first message is sent.
Cause: 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.
Message Delivery Errors
Recipient Not Found
What you see: the alert is delivered to no recipient, or channel_not_found appears in the error log.
Cause: this has two common causes. (1) The Channel mapping resolves a member by matching the supplied profile name against the workspace members (member Name first, then Real Name), and no member matches. (2) The Channel mapping targets a private channel (for example,
return "#chris-private";) that 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
What you see: not_in_channel or is_archived in the error log.
Cause: 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
What you see: rate_limited in the error log.
Cause: 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.