The number of users who use an internal chat service, “slack”, is increasing these days.
I hear that some customers of our Questetra are using the service.
One customer consulted with us as the following.
“We want to check daily report more easily with smart phone by posting digest of the report to Slack after processing it in Questetra.”
I’ll introduce the details of our proposition at that case.
== 1. Overview ==
That’s very easy!
- Obtain token for calling slack API
- From Questetra, send data (including the token described above) with http to “slack” posting API
== 2. Details ==
=== 2.1 Preparation for slack ===
Obtain token by accessing the website below （Slack Web API）.
=== 2.2 Preparation for Questetra ===
The parameter settings are as follows:
- Specify [Access URL] of [Network Settings] as 「https://slack.com/api/chat.postMessage」
- In [Parameters], specify the value obtained in previous step as [token], the name of slack channel you want post to as [channel], the message(Process data item) you want to post to as [text]
♦There are some optional parameters you can specify in posting API of slack. By using such options, you can deal with some cases such as “Posting a message as a certain user’s post”.
Please check API reference of slack for more details.
Incidentally, Questetra itself also has equipped with in-house chat service, [Open Chat]. [Open Chat] has an advantage of being capable of connecting chat message to process which processed on Questetra. Please use chat services according to your purpose.
Questetra BPM Suite has supported “the case of OAuth2.0 connection which has access tokens with unlimited validity and not have refresh tokens” since Ver.10.4.0. It has become possible to connect with OAuth settings other than the procedure above.
|Prev article - 50. Questetra Tips||Handle Script Step Well! : Solution for Error (1)|
|Next article - 50. Questetra Tips||We have Started Supporting Microsoft Edge|
|Another article - Kusaka Tsuyoshi||Tips When You are in Trouble with kintone’s “Workflow Management” (part 1)|