1. The delivery infrastructure for LINE Messages has been revamped to greatly improve the speed of delivery of large volumes of messages (parallel delivery processing with Google Cloud Pub/Sub and Cloud Functions). 2. Added an input check function to the question action of the chatflow. 3. SMS location changed to Japan.
Why does it matter? 1. In the past, sending out LINE messages to many users (over 10,000) took up to 15 minutes to complete delivery. In addition, there were errors when delivering large numbers of messages from HubSpot's workflow. 2. When prompting a user for keyboard input in a chat flow question action, the value entered could not be checked. 3. A timeout error could occur in the delivery of SMS (short message). How does it work? 1. By processing the delivery of LINE messages in parallel, the delivery speed has been improved by more than 10 times. 30,000 users can receive a LINE message in about 3 minutes.
In the example below, about 500 servers are immediately up and delivering messages.
We have also modified the system to handle send requests from HubSpot workflows in parallel. The "Send Immediately" flag in the workflow action has been eliminated, allowing immediate sending without overloading the system.
When using a template from a workflow, there may be a time lag of 1 to 5 minutes due to the limited number of times the HubSpot API can be executed.
2. Specify the pattern of values you wish to check in the "Input Validation" section of the question action. We have prepared patterns for "e-mail address," "phone number (without hyphen)," and "katakana," but you can also create your input checks using regular expressions.
3. Japanese location is now used when sending SMS. For receiving, the parameter "#e=tokyo" must be added to the Webhook URL set in Twilio. Please set this parameter if you wish to use a Japanese location.