Summary

Rule-based automation in Wati allows you to automate various scenarios quickly and efficiently. This article introduces the three fundamental building blocks of a rule: Triggers, Filters, and Actions, and guides you through creating your first rule.

Instructions

Understanding How to Create Rule-Based Automation

Rule-based automation provides the flexibility to automate different scenarios by creating rules composed of three key elements:

Trigger: An event that starts the automation (e.g., a new message received).
Filter: Conditions that must be met for the action to occur (e.g., specific keywords in the message).
Action: The automated task that is performed when the trigger and filter conditions are met (e.g., sending a reply).

Let’s explore how to create a rule using these building blocks:

Navigate to Automation Rules: Go to your Automation page and select the Rules tab on the left.
Create a New Rule: Select Create new rule and choose the Trigger you want to use.

Access the Rule Builder: After selecting a trigger, you will be directed to the Rule Builder page, where you can configure the properties for each of the three blocks (Trigger, Filter, and Action). In this example, we will select the Trigger "New attribute is added to a contact".

Configure the Trigger: Click on the first Trigger block and configure the attribute you want to target.

Select an Action: Choose the Action you want the rule to perform when it is triggered. Wati will support a wide range of Actions in the future!

Configure the Action: In this example, let's select "Send template message". This means a specific template message will be sent automatically when this rule is triggered.

Example:

In this example, whenever a new attribute shop_name is added to a contact, and the attribute value contains the word "cafe", Wati will automatically send out a template message for you.

Frequently Asked Questions (FAQs)

General Questions

1. What is rule-based automation in Wati?

Rule-based automation in Wati lets you automate different scenarios by creating rules made of three components: triggers, filters, and actions.

2. What are the key components of a rule in Wati?

A rule consists of:

Trigger: An event that starts the rule.
Filter: Conditions that must be met for the action to happen.
Action: The automated task performed when the rule is triggered and the filter conditions are met.

Creating Rules

3. How do I create a new rule in Wati?

Go to the Automation page, select the Rules tab, and click Create new rule. Then, choose a trigger to start building your rule.

4. What is the Rule Builder in Wati?

The Rule Builder is the page where you configure the details of your rule, including the trigger, filter conditions, and actions.

Triggers

5. What is a trigger in Wati automation?

A trigger is an event that starts a rule. For example, a new message received or a new attribute added to a contact.

6. Can I customize the trigger in a rule?

Yes, when configuring a trigger, you can specify details like the contact attribute you want the rule to target.

Filters

7. What is a filter in Wati automation?

A filter defines conditions that must be met for the action to occur. For example, checking if a contact attribute contains a specific word.

Actions

8. What types of actions can I configure in a rule?

Actions are automated tasks like sending a template message. Wati will support more action types in the future.

9. How do I configure an action in a rule?

After setting the trigger and filter, select the action you want, such as sending a template message, and configure its details.

Examples

10. Can you give an example of a rule in Wati?

For example, you can create a rule where if a new attribute shop_name is added to a contact and it contains the word "cafe", Wati automatically sends a template message.

11. Why is there a duplicate automation triggered on my account?

Duplicate automations may occur when a chat condition matches both a Rule and one of the legacy features(Keyword or Default Actions). In this case, both automations get triggered at the same time.

To prevent duplicates: