Send Message
Last updated
Last updated
For example, add a workflow of reminder messages.
To display the message reminder, a timer interval is needed. Timer interval enables you to control the workflow using a time condition. You can use timer interval to create a delay before running the next proses. For example, set interval message to 5 seconds.
When the ‘reminder1Mins’ process finishes running according to the specified time interval, the process flow will automatically move to the next node_id which is ‘sendReminder’. ‘SendReminder’ functions to send a reminder message that will be sent to the customer.
Component Explanation :
| Name | Description |
|---|---|
Message Name | The node_id in the workflow component. |
Link | link will automatically filled (example : domain.com/apiv1/graph/tickets/sendMessage) |
Username | Username of user on the 3Dolphins system. |
Password | Password of user on the 3Dolphins system. |
Ticket Number | Retrieve the ticketNumber variable from the request body. |
Channel Type | Select a channel to send message (Channel has been registered in the omnichannel) |
Message ID | Message ID can be written freely (free text). |
Reply Agent | If the message is sent by a bot, then write the agent reply as ‘Bot’, however if the message is sent by the agent, the agent reply is written as ‘Agent id’. |
Message | Enter a custom message that will appear in the notification message that are sent on the channel selected. |
In the image above (Images Reminder Workflow – sendReminder), we take the example of the ‘${intent.ticket.ticketNumber}’ variable. This process is to provide a feedback response to requests sent, this response is in the form of a 'Ticket Number' object whose value is ‘${intent.ticket.ticketNumber}’. this ‘${intent.ticket.ticketNumber}’ variable serves to retrieve the ticketNumber variable from the request body.
For example: when a customer sends a message, the customer automatically sends a request (extension request) to the flow process. An example of this extension request can be seen in the image below.
In the extension request there is some data that may be needed by the developer, such as an account ID, ticket number, etc. For example, when retrieving the ticket number from the request extension, the method of writing is: $ {intent.ticket.ticketNumber}.
The URL on this message is the default and will be filled automatically when you create a workflow process.
Description of URL :
{URL}: Used to pass information to the destination.
{Path}: Location of data on the server
