Skip to main content

Slack App

This guide contains information to set up a Slack Sink in Vanus Connect.

Introduction

Slack is a cloud-based team collaboration platform that allows users to communicate, share files, and integrate with other tools and services.

With Slack Sink connector in Vanus Connect, you can easily forward real-time updates to a Slack group chat, allowing your team to stay up-to-date on all events generated by your application.

Prerequisites


Perform the following steps to configure your Slack Sink.

Step 1: Create a Slack App

  1. Go to Slack API, and click Create New App①.

slack-app-sink-1

  1. Select From scratch②.

slack-app-sink-2

  1. Set the App name③ and Workspace④, then click Create App⑤.

slack-app-sink-3


Step 2: Configure your App

  1. Add the Permissions① feature for your app.

slack-app-sink-4

  1. Scroll down to Scopes/Bot Token Scopes, and click Add an OAuth Scope②.

slack-app-sink-5

  1. Add chat:write③ and chat:write:public④ permission to your app.

slack-app-sink-6

  1. Scroll up to the top of the page, and click Install to Workspace⑤.

slack-app-sink-7

  1. Click Allow⑥ to install the app.

slack-app-sink-8

  1. Copy⑦ the Bot User OAuth Token.

slack-app-sink-9

  1. Return to the Vanus Connect page and paste your Bot User OAuth Token in the Token⑧ field.

slack-app-sink-10


Step 3: Personalize Event Structure

note

This is a general instruction on how to personalize your event structure. You can structure your events to suit your specific requirements and create connections for different scenarios.

  1. Click on Display sample events① for reference, compose your preferred message, then type $ followed by the desired event② to access a list of associated event values③, and choose the one you prefer.

slack-app-sink-11

  1. You can structure the content as you prefer and fill in as many values④ as you wish to receive.

slack-app-sink-12

  1. Click Submit⑤ to finish the configuration process.

slack-app-sink-13


Learn more about Vanus and Vanus Connect in our documentation.