suse-coder
diff --git a/‎blog/2023-02-13-slack-integration/10-slack_group.png
319 KB b/‎blog/2023-02-13-slack-integration/10-slack_group.png
319 KB
diff --git a/‎blog/2023-02-13-slack-integration/11-variable_to_folder.png
395 KB b/‎blog/2023-02-13-slack-integration/11-variable_to_folder.png
395 KB
diff --git a/‎blog/2023-02-13-slack-integration/12-folder_to_group.png
276 KB b/‎blog/2023-02-13-slack-integration/12-folder_to_group.png
276 KB
diff --git a/‎blog/2023-02-13-slack-integration/index.md
Lines changed: 25 additions & 0 deletions b/‎blog/2023-02-13-slack-integration/index.md
Lines changed: 25 additions & 0 deletions
diff --git a/‎docs/flows/13_flow_branches.md
Lines changed: 3 additions & 2 deletions b/‎docs/flows/13_flow_branches.md
Lines changed: 3 additions & 2 deletions
@@ -92,6 +92,31 @@ on Windmill. The runs will be permissioned through the `g/slack` global group.
 
 ![Run info](./6-run-info.png)
 
+:::
+
+:::danger
+
+You won't be able to have Slack interact with your resources and variables before adding them to the `slack` group that was automatically created by Windmill after you set up your Slack workspace on Windmill.
+
+To give the permission, go to "Resources" (and "Variables") menu, click on `Share`, `Group` and pick `slack`.
+
+<br/>
+
+![Share to slack group](./10-slack_group.png)
+
+<br/>
+
+One simplier way to handle permissions is to host resources and variables on a folder that is part of the group `slack`.
+
+<br/>
+
+![Share variable to folder](./11-variable_to_folder.png)
+
+<br/>
+
+![Share folder to group](./12-folder_to_group.png)
+
+
 :::
 
 ## Action on Slack from Windmill
 
@@ -7,11 +7,12 @@ There are two types of branches:
 
 ## Branch one
 
-A branch one is a special type of step that allows you to execute a branch if a condition is true. If the condition is false, the default branch will be executed. Each branch is a flow.
+A branch one is a special type of step that allows you to execute a branch if a condition is true. If the condition is false, the default branch will be executed. If several branches are true, the first one will execute. Each branch is a flow.
 
 Clicking on one branch will open the branch editor. You can configure the:
 
-- **Predicate expression**: the expression that will be evaluated to determine if the branch should be executed.
+- **Summary**: gives a name to the branch, useful when several branches. By default Branch 1, 2, 3...
+- **Predicate expression**: the expression that will be evaluated to determine if the branch should be executed. It can be simple `true`/`false` but also comparison operators (`results.c.command === 'email'`, `flow_input.number >= 2` etc.)
 
 ![Branch one step](../assets/flows/flow_branch_one.png)