Out of the box, Fusebit's Slack Integration uses our own demonstration application in the Slack App Directory. This is to make it easier to get started, however you will likely need to register your own Slack App in case:
- the Slack method you are executing via the SDK requires more advanced permissions
- you want to receive inbound messages via the Slack Events API
- you want to deploy your Integration in production and you want end-users to see your own branding instead of Fusebit branding
To create your own Slack App:
- Go to https://api.slack.com/apps and create an App "from scratch". Pick your company workspace for development, the app will be installed on your customer workspaces once it has been set up.
- Note the Client ID and Client Secret shown on the next screen.
- If the method(s) you want to invoke against the Slack API require certain permissions see here, add the appropriate scopes under Features > OAuth & Permissions > Scopes > Bot Token Scopes.
The following permissions are necessary to run the example provided later:
Back in the Fusebit Portal, find the Integration you would like to connect to the new Slack App you just created.
- Select the ConnectorConnector - A connector is the package from Fusebit that manages the relationship between one or more integrations and a specific service. One of the most common types of connector is an OAuth connector, which takes care of the OAuth negotiation between your customers and the service you're integrating, so that you don't have to! tied to that integration
If more than one Integration is linked to that same Connector, they will all use the new Slack App you are about to configure.
- Select Enable Production Credentials in the Connector Configuration and then paste in the Client ID and Client Secret you obtained earlier from the Slack App you created. Also, list the permissions your code requires in the Bot Token Scopes field. To use the example provided later in this guide, specify the following scopes:
channels:join channels:read chat:write users:read.
When switching a Connector to a different Slack App, all IdentityIdentity - An identity is a unique relationship one of your customers has with a service. An identity can be used by multiple integrations to act on that service on behalf of your customer. objects associated with that Connector will be deleted. Your users will need to re-authenticate against Slack after you make the change.
- Navigate back to your Slack App and over to Features > OAuth & Permissions > Redirect URLs and paste the URL provided by Fusebit in the Slack Configuration section under OAuth2 Redirect URL
Any time a new user installs your Integration, you should now see your Slack App information displayed during the authorization step.
In our next section, we will configure this app to listen for events coming from Slack and respond to them.
Updated 20 days ago