External Request Update: send file as parameter in API calls
This is an update about the External Request in the Action Step.
You can include a file itself in the API calls instead of the URL link of the file.
In the External Request, go Body, multipart/form-data and you will see an Upload Files section. Put a file direct link here to include the file itself in the parameter. You can put the link you get from a Question Step here. (Please note that the file URL link from a Question Step is only valid for 24 hours) image.png45.51 KB
1) inputs in Auth section - Api Key type 2) client id, secret, access token, refresh token, etc in Auth section - OAuth v2 type 3) inputs of actions in Actions section
2. Dynamic Source invalid in One Time Url - 2. Web Forms - Inputs
When you go setting the inputs of web forms in a one-time URL, dynamic source won't work here.
3. the drop-down list only loaded when first click "edit action"
In the chatbot flow, when you create a new action of the Mini-App, and first click "Edit Action", the system will do an external request and generate the drop-down list based on the current value in the fields. If you change the parameter e.g. the value in Auth inputs, the drop-down list won't be re-fresh, please delete the action and create a new one.
Before the update, you can duplicate only one step at a time. Now you can select multiple steps and duplicate them.
Please note that,
- after copying multiple steps, you can only paste once. copy again for another paste - where can I paste the steps? (1) to the same bot/flow (2) to the different bot/flow but the same channel (associate custom fields will be created automatically) (3) to different channels (unsupported features will be removed)
- subflow template supported (installed subflow goes to a folder) - template configuration added: viewable, editable, version number (only for subflow template) - install template from different channel - interface changed
Before the update, there are NOW, TODAY system fields that refer to the current time/date of the users (if they have a timezone in their profile, otherwise based on workspace's timezone).
Now a new system field is added called BOT_CURRENT_TIME. This one is the current time based on the workspace's timezone.
This is an update about the preview feature in all channels which support preview (Facebook, Telegram, WhatsApp, Line and Viber)
When you click the "Preview" button, there will be a QR code generated, you can click "Open in XX" to talk to the bot in the website/desktop application or scan the code with your camera or according phone application.
Dynamic Quick Reply in Send Message Step Now Available
This is an update about Send Message Step.
Before the update, you will need to list all the quick replies yourself but now, by selecting a JSON variable, your chatbot can list the quick replies from the JSON variable for you:
Please note that these replies expire in 30 minutes.
Dynamic Quick Answer in Question Step Now Available
This is an update about Question Step.
Before the update, you will need to list all the quick answers yourself but now, by selecting a JSON variable, your chatbot can list the quick answers from the JSON variable for you:
We add a new way for you to auto cleanup bot users. You can cleanup bot user when reached bot user limit or time interval.
For example, set up the cleanup to 90 days and the bot will automatically remove users who haven't interacted with your bot over 90 days.
These cleanup conditions are checked once per day, not in real-time.
Alternatively, for more customized cleanup conditions, we suggest you use a datetime based trigger to do a regular check and in the workflow, setup your own condition like only clean guest user or user without contact information, etc.
Now each message sent by the bot has a little drop-down button, click on it to "Resend Message" or navigate to the step to edit the step, do your improvement in a more convenient way.
When you check error log, you can see which step in which subflow went wrong, before the update, you will need to navigate to the step yourself. Now by simply click on the step name, you will jump to the step right away.
When you click on the "Response Headers", a list of hearer information will show. Now the hearer information is all clickable. For example, in the screenshot below, you can click on the "Response-Code: 200" to get its path "$H['Response-Code'] and save the value "200" to a variable for later usage.