See what the Slack integration can do →
Integrate iPaaS.com with Slack to send alert messages from iPaaS.com to a designated member in your Slack workspace.
How to Connect
The Slack integration supports two authentication methods. OAuth 2.0 is the preferred method because it is simpler to set up: after you save the subscription, you authorize the iPaaS.com Slack app and an access token is stored for you. As an alternative, you can supply a Bot User OAuth Token from your own Slack app. Both methods are described under Authentication Methods below.
Prerequisites
Before configuring the integration in iPaaS.com, ensure the following:
Slack workspace: A Slack workspace where the iPaaS.com Slack app (OAuth 2.0) or your own Slack app (Bot token) will be authorized.
iPaaS.com account: An active subscription on iPaaS.com.
Slack app (Bot token method only): If you intend to use the Bot token method, you must first create a Slack app in your workspace at https://api.slack.com/apps and install it so that a bot token is available. This is not required for the OAuth 2.0 method.
Configure Subscription Settings
Navigate to the Slack subscription settings in iPaaS.com and provide the following details. The same values apply to both the Test and Production environments.
Field | Description | Required | Example |
Name | A unique name for identifying the Slack subscription. | Yes | Slack Integration |
Version | The integration version to use. | Yes | v1.0 |
API URL | The base API URL for Slack. The same value is used for both Test and Production. | Yes | |
API Token | The Bot User OAuth Token from your Slack app, used with the Bot token method. This field must not be left blank. Under OAuth 2.0 the value is not used, so enter a placeholder such as a single dash to satisfy the required field. | Yes | xoxb-your-bot-token |
Client ID | The Client ID from your Slack app, used with the Bot token method. This field must not be left blank. Under OAuth 2.0 the value is not used, so enter a placeholder such as a single dash to satisfy the required field. | Yes | 1234567890.1234567890 |
The connection is not live-validated when you save the subscription. Saving the settings stores them for use, but it does not test connectivity against Slack. To confirm the integration is working, complete the authorization steps below and then run a manual sync.
Authentication Methods
You can authenticate the integration in one of two ways. Choose the method that best fits your workspace.
OAuth 2.0 (preferred)
This method uses the iPaaS.com Slack app and does not require you to create your own Slack app. The API Token and Client ID settings are not used by this method, but they are required fields, so enter a placeholder such as a single dash rather than leaving them blank.
After filling out the subscription settings above and saving the subscription, navigate to your Slack subscription settings in iPaaS.com.
Click the padlock icon to begin the OAuth process.
You are redirected to Slack to authorize the iPaaS.com Slack app.
Grant the requested permissions, allowing the app to access the information it needs, such as channels and conversations.
After granting access, you see an Authorization Complete screen.
Return to your iPaaS.com subscription settings and confirm the message OAuth Process Complete is displayed.
It may take a few minutes for the full OAuth process to complete in the background. To confirm authorization is complete, return to your subscription settings page: when an access token has been stored and the message reads OAuth Process Complete, the integration is authorized. Slack OAuth access tokens do not expire, so this authorization does not need to be renewed on a schedule.
Bot token (alternative)
This method uses a Slack app that you create and install in your own workspace. Use it when you prefer to manage your own app and credentials rather than authorizing the iPaaS.com Slack app.
In your Slack app, open Basic Information and copy the Client ID. Enter this value in the iPaaS.com Client ID setting.
In your Slack app, open OAuth & Permissions and copy the Bot User OAuth Token. Enter this value in the iPaaS.com API Token setting.
Save the subscription. For the supplied token to be used, ensure there is no access token already stored from a previous OAuth 2.0 authorization. If an OAuth access token is present, the integration uses it instead of the values you entered here.
Initialization Support
Currently, initialization is not supported for Slack in iPaaS.com. Bulk initialization of historical data is not available; all data synchronization and mappings must be configured manually during the integration process.
Throttling
Throttling ensures that Slack's API is not overwhelmed by excessive API calls, preserving system performance during heavy data transfers.
While the throttling fields are required, the values are pre-populated by the integration settings. The API Throttle Limit / Concurrent Batch Executions values are set to 5 for the initial transfer and 500 for ongoing transfers. For more details, refer to Subscription Configuration – Edit.