engAIge can react to events/triggers with an action e.g. we can render a form to the customer when the page is loaded e.g. contact us form or a sales capture form
Action Images
Below are all the actions available to a user to drag and drop in the workflow they creating.
Action Details
Render Form
This triggers the display of a form on the website. Forms are typically used to collect user input, such as contact details, feedback, or other relevant information.
Render Pop-Up
This action displays a pop-up window on the website. Pop-ups can be used for notifications, promotions, or to capture user information
Change Text
This action modifies the text content of a specific element on the website. For example, updating the text of a button or changing the content of a paragraph.
Render Landing Page
This action directs the user to a specific landing page. Landing pages are often used in marketing campaigns to provide information about a particular product, service, or offer.
Update Image
This action replaces an existing image on the website with a new one. It can be used to refresh visuals or display new content.
Google Floodlight
This is a specific action related to Google's advertising services. It allows advertisers to track and measure the impact of their online ad campaigns.
Send Email
This action initiates the sending of an email, often to a specified recipient. It can be used for notifications, confirmations, newsletters, or other communication purposes.
Javascript examples
InputData.Email.ToString()
InputData and ToString() stay constant
Email will be a parameter in the payload of the external source
The aim here is to use the To Address field as a variable so we can send the email to many customers. If we had inserted a single email address, then the email would send to that one address only.
Send SMS
This action sends a text message to a specified phone number. It's often used for notifications, verifications, or alerts.
Example of SMS content
"Hi " + InputData.customerName.ToString()+", your " + InputData.shortName.ToString() +" payment has failed. Please pay R" + InputData.billedAmount.ToString() + " immediately to avoid any interruptions. Use Banking Details: ABSA Acc Number 4086019863; Branch 632005: Ref:" + InputData.policyNo.ToString()+" or call 0861111485"
This will render:
Hi Kira Francis, your abcdef payment has failed. Please pay R80 immediately to avoid any interruptions. Use Banking Details: ABSA Acc Number 4086019863; Branch 632005: Ref: 123456de89 or call 0861111485
Example of SMS msisdn
InputData.Phone.ToString()
InputData and ToString() stay constant
Phone will be a parameter in the payload of the external source
The aim here is to use the msisdn field as a variable so we can send the SMS to many customers. If we had inserted a single number, then the SMS would send to that one number only.
Send WhatsApp
This action sends a message via WhatsApp, a popular messaging platform. It can be used for customer support, notifications, or promotional messages
Using Variables
WhatsApp templates can include variables, which are placeholders for dynamic content that can be personalized for each recipient
Customer Name:
- Template: "Hello {{1}}, thank you for your purchase!"
- Example: "Hello John, thank you for your purchase!"
Order Number:
- Template: "Your order {{1}} has been shipped."
- Example: "Your order #12345 has been shipped."
When defining what each variable is on the action, we will use the same JS as used in the SMS action.
For Example: InputData.customerName.ToString()
The to Number will be a JS string also, pulling the numbers from the payloads of the external source.
API Call
This action involves making a request to an Application Programming Interface (API). APIs allow different software applications to communicate with each other. An API call can be used to retrieve data, send data, or trigger specific functionalities in another system. For example, checking the weather by calling a weather API or updating user information in a database through a dedicated API endpoint.
Shorten URL
This action generates a shortened version of a long URL, making it more user-friendly and easier to share.
Log Support Ticket
This action creates a support ticket, typically in a customer support system. It's used to track and address user issues or inquiries.
External Workflow
This action refers to the initiation or interaction with a workflow that resides outside the current system or platform. An external workflow is a sequence of processes or tasks that are managed and executed by an external system. Engaging with an external workflow might involve triggering a series of events, tasks, or processes in another application, system, or service. For instance, after a user submits a form on a website, an external workflow in a Customer Relationship Management (CRM) system might be initiated to manage the user's inquiry, send automated responses, and assign the inquiry to a sales representative. The use of external workflows allows for seamless integration and automation between different systems, ensuring that data flows smoothly and processes are coordinated across platforms.
Resume Workflow
If a workflow was paused or interrupted, this action resumes it from where it left off.
SQL DB
This action queries a database to retrieve specific information. For example, checking product availability or fetching user details.
Mongo DB
This action queries a database to retrieve specific information. For example, checking product availability or fetching user details.
Postgres DB
This action queries a database to retrieve specific information. For example, checking product availability or fetching user details.
Web Instruction
This action provides specific instructions to the website, such as loading a new script, initiating an animation, or executing a particular function.
External Source Instruction
This action involves sending a specific command or instruction to an external source. It's a directive for the external source to perform a particular function or return specific data. For instance, instructing a third-party payment gateway to process a transaction.
End of client
This action signifies the termination or conclusion of a client's session or interaction on the website.
End of Workflow
This action marks the completion of a specific workflow or process on the website.
Filters And flow
Yes/No Split
This refers to a decision point in the workflow where there are two distinct paths based on an outcome: "Yes" or "No". At this juncture, the user must make a choice based on a specific condition or criteria. If the condition is met (true), the "Yes" path is taken; if the condition is not met (false), the "No" path is followed. This type of split is used to handle different scenarios or outcomes based on a singular decision point.
Real life example
John pays for a monthly subscription using pAIment.
engAIge comes into play with a "Yes/No Split" based on the payment status
Yes (Payment Successful): If John's payment is successful, engAIge triggers an action to send an email to John's registered email address, confirming his purchase and thanking him for shopping.
No (Payment Failed): If there's an issue with John's payment, perhaps due to insufficient funds, engAIge activates a different action. John receives an SMS notifying him of the payment failure and suggesting steps to resolve the issue.