You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/content/tutorial/ai-chatbot.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -100,19 +100,19 @@ Navigate to the Bolty **App Home** and select a provider from the drop-down menu
100
100
101
101
If you don't see Bolty listed under **Apps** in your workspace right away, never fear! You can mention **@Bolty** in a public channel to add the app, then navigate to your **App Home**.
102
102
103
-
103
+
104
104
105
105
## Setting up your workflow {#workflow}
106
106
107
107
Within your development workspace, open Workflow Builder by clicking on your workspace name and then **Tools > Workflow Builder**. Select **New Workflow** > **Build Workflow**.
108
108
109
109
Click **Untitled Workflow** at the top to rename your workflow. For this tutorial, we'll call the workflow **Welcome to the channel**. Enter a description, such as _Summarizes channels for new members_, and click **Save**.
110
110
111
-
111
+
112
112
113
113
Select **Choose an event** under **Start the workflow...**, and then choose **When a person joins a channel**. Select the channel name from the drop-down menu and click **Save**.
114
114
115
-
115
+
116
116
117
117
Under **Then, do these things**, click **Add steps** and complete the following:
118
118
@@ -121,20 +121,20 @@ Under **Then, do these things**, click **Add steps** and complete the following:
121
121
3. Under **Add a message**, enter a short message, such as _Hi! Welcome to `{}The channel that the user joined`. Would you like a summary of the recent conversation?_ Note that the _`{}The channel that the user joined`_ is a variable; you can insert it by selecting **{}Insert a variable** at the bottom of the message text box.
122
122
4. Select the **Add Button** button, and name the button _Yes, give me a summary_. Click **Done**.
123
123
124
-
124
+
125
125
126
126
We'll add two more steps under the **Then, do these things** section.
127
127
128
128
First, scroll to the bottom of the list of steps and choose **Custom**, then choose **Bolty** and **Bolty Custom Function**. In the **Channel** drop-down menu, select **Channel that the user joined**. Click **Save**.
1. Choose **Messages** and then **Send a message to a person**. Under **Select a member**, choose **Person who clicked the button** from the drop-down menu.
135
135
2. Under **Add a message**, click **Insert a variable** and choose **`{}Summary`** under the **Bolty Custom Function** section in the list that appears. Click **Save**.
136
136
137
-
137
+
138
138
139
139
When finished, click **Finish Up**, then click **Publish** to make the workflow available in your workspace.
140
140
@@ -149,7 +149,7 @@ In order for Bolty to provide summaries of recent conversation in a channel, Bol
149
149
150
150
To test this, leave the channel you just invited Bolty to and rejoin it. This will kick off your workflow and you'll receive a direct message from **Welcome to the channel**. Click the **Yes, give me a summary** button, and Bolty will summarize the recent conversations in the channel you joined.
The central part of this functionality is shown in the following code snippet. Note the use of the [`user_context`](https://api.slack.com/automation/types#usercontext) object, a Slack type that represents the user who is interacting with our workflow, as well as the `history` of the channel that will be summarized, which includes the ten most recent messages.
155
155
@@ -191,7 +191,7 @@ To ask Bolty a question, you can chat with Bolty in any channel the app is in. U
191
191
192
192
You can also navigate to **Bolty** in your **Apps** list and select the **Messages** tab to chat with Bolty directly.
Copy file name to clipboardExpand all lines: docs/content/tutorial/custom-steps-for-jira.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -127,21 +127,21 @@ If your app is up and running, you'll see a message noting that the app is start
127
127
2. Select **New Workflow** > **Build Workflow**.
128
128
3. Click **Untitled Workflow** at the top of the pane to rename your workflow. We'll call it **Create Issue**. For the description, enter _Creates a new issue_, then click **Save**.
4. Select **Choose an event** under **Start the workflow...**, and then select **From a link in Slack**. Click **Continue**.
133
133
134
-
134
+
135
135
136
136
5. Under **Then, do these things** click **Add steps** to add the custom step. Your custom step will be the function defined in the [`create_issue.py`](https://github.com/slack-samples/bolt-python-jira-functions/blob/main/listeners/functions/create_issue.py) file.
137
137
138
138
Scroll down to the bottom of the list on the right-hand pane and select **Custom**, then **BoltPy Jira Functions** > **Create an issue**. Enter the project details, issue type (optional), summary (optional), and description (optional). Click **Save**.
6. Add another step and select **Messages** > **Send a message to a channel**. Select **Channel where the workflow was used** from the drop-down list and then select **Insert a variable** and **Issue url**. Click **Save**.
143
143
144
-
144
+
145
145
146
146
7. Click **Publish** to make the workflow available to your workspace.
147
147
@@ -150,16 +150,16 @@ If your app is up and running, you'll see a message noting that the app is start
150
150
1. Copy your workflow link.
151
151
2. Navigate to your app's home tab and click **Connect an Account** to connect your JIRA account to the app.
4. In any channel, post the workflow link you copied.
160
160
5. Click **Start Workflow** and observe as the link to a new JIRA ticket is posted in the channel. Click the link to be directed to the newly-created issue within your JIRA project.
0 commit comments