-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
-
keyboard_arrow_right keyboard_arrow_down
- Flowlu
- Flowlu Help Center
- Getting Started
- How to Integrate Slack With Flowlu
How to Integrate Slack With Flowlu
Slack is a business communication platform that allows you to unite your team under one workspace. Its simple interface and multifunctionality will help you to improve communication among team members and facilitate interaction between departments.
Set up the integration of your Flowlu account with Slack workspaces and receive notifications about new tasks, opportunities and projects directly in the messenger.
Stage 1. Setting Up Flowlu Accounts
Go to the Marketplace section and install Slack app.
After installing the application, you will see its settings:
- "Message" tab allows you to configure various algorithms and conditions for receiving a message in Slack;
- In "Sign in" tab will be displayed those messenger workspaces that are integrated with your account;
- "Roles and permissions" and "User Access Settings" tabs allow you to configure access for both a specific group of users and for individual users. The Slack application can only be visible and customizable by administrators.
For setting up integration, you will need to open the appropriate tab and click on the Connect button.
You will be redirected to the Slack site, where you can either log in to an existing workspace or create a new one.
Next, Flowlu asks for permissions to access the workspace as well and also change the workspace if you have more than one.
After confirmation, you will automatically go back to the app settings in Flowlu, where you can see what has been integrated from Slack. Under the "Users" tab, the names of users' email addresses will be displayed instead of their nicknames.
Check that Flowlu and bot have been added to Slack apps, click Save and then proceed directly to setting up messages.
To update your workspace and include new members or new channel names, you can open your integration settings in "Sign in" tab and press the update button.
Stage 2. Setting up forwarded messages in Slack
Go to the "Message" tab. Here you can see the list of messages you have created earlier, edit them or create new ones. Click on the "Create a message" button in order to create a new rule.
Let's take a closer look at each option.
- in the upper right corner you can see message status, “Active” status means that the rule will be executed and, under the appropriate conditions, you will receive a message in Slack. If the status is inactive, then there will be no message;
- in the "Title" field, you can indicate the name and give a brief description of this message;
- in the field "Workspace and channel" you can select the workspace and channel / user to which/whom the message will be forwarded;
- in the "Event" fields, you will need to select appropriate conditions for entities. Currently, conditions are available for tasks, projects and opportunities. The process is the same for each of the entities, a message can be created when:
- creating a task, opportunity or project;
- deleting a task, opportunity or project;
- editing the task, opportunity or project;
- adding a comment to a task, opportunity or project;
- changing the assignee in the task and opportunity or changing the project manager;
- changing the stage of a task, opportunity or project; - sender selection. The bot can send a message both under the guise of an application and under the guise of a user (only under the one who set up the integration);
- it's possible to add an avatar for the bot, which will send a message under the guise of an application. The recommended size is 128x128.
- the "Message" field contains the message itself that the bot will send. By clicking on the three dots, you can select variables that can substitute a value from a created opportunity or a modified task.
After successful configuration, click Save for this rule to come into effect.
The final result will look like this:
Or like this, if you select a user as the sender: