> ## Documentation Index > Fetch the complete documentation index at: https://help.wotnot.io/llms.txt > Use this file to discover all available pages before exploring further. # Automations > Automations let you perform actions automatically when specific events or conditions occur during a conversation. Instead of manually monitoring conversations, assigning chats, sending notifications, or calling external APIs, you can define a trigger and let WotNot handle the action for you. ![Image](https://mintcdn.com/wotnot/IgY-Q46pOTb5_NPe/images/image-492.png?fit=max\&auto=format\&n=IgY-Q46pOTb5_NPe\&q=85\&s=71096b9a411cc94f94fb2588fd3b016f) > [!NOTE] > > **Available on all channels.** # When to use an automation You can use automations to: * Add chat transcript to your CRM after chat ends * Notify your team when SLA is breached * Send slack notifications when a variable changes to X * Send an email to the visitor after chat ends * and more... | Feature | Best for | How it works | | :- | :- | :- | | **Automations** | Running actions automatically based on conversation events | Monitors trigger criteria and performs an action when the criteria are met. | | **Live chat assignment rules** | Assigning conversations to the right team or agent | Routes conversations based on your assignment rules. | | **Trigger action block** | Starting a flow from inside a bot conversation | Triggers the configured bot flow when the visitor reaches that block. | | **Zapier** | Connecting WotNot with third-party applications through Zapier | Sends or receives data through a Zapier workflow. | # Triggers A trigger defines the event or condition that starts an automation. > [!NOTE] > > **An automation starts only when its configured trigger criteria are met.** | Trigger | When it fires | Data available to the action | | :- | :- | :- | | **Assignee change** | When the assignee of a conversation changes | Conversation and assignee information | | **Conversation status** | When the conversation status changes | Conversation and status information | | **Variable value** | When a variable reaches the configured value | Conversation variables and their values | * You can configure multiple trigger conditions for an automation. Choose whether **ALL** conditions or **ANY** conditions must match before the automation runs. ![Image](https://mintcdn.com/wotnot/IgY-Q46pOTb5_NPe/images/image-493.png?fit=max\&auto=format\&n=IgY-Q46pOTb5_NPe\&q=85\&s=5eaababffb6a323db5ab023466511209) # Actions An action defines what WotNot does after the trigger criteria are satisfied. ![Screenshot 2026 08 25 104947](https://mintcdn.com/wotnot/IgY-Q46pOTb5_NPe/images/Screenshot-2026-08-25-104947.jpg?fit=max\&auto=format\&n=IgY-Q46pOTb5_NPe\&q=85\&s=39a33b3b559063f8be0b407f5fd702d4) | **Action** | **What it does** | **What it needs configured** | | :- | :- | :- | | Send an email | Sends an email notification to a specified email address | Recipient email address and email content | | HTTP Request | Sends an API request to an external endpoint | API endpoint and request configuration | | Send agent response | Sends a response to the agent | To send a response to agent | # Conditions Conditions let you control when an automation should run. You can add multiple trigger conditions and choose how they should be evaluated: * **ALL** — every configured condition must be satisfied. * **ANY** — at least one configured condition must be satisfied. For example, you can create an automation that sends an email only when: * The conversation status changes to closed, **AND** * A specific variable contains a particular value. Using conditions helps prevent an automation from running for conversations that do not match your intended criteria. # Creating an automation ![Image](https://mintcdn.com/wotnot/IgY-Q46pOTb5_NPe/images/image-494.png?fit=max\&auto=format\&n=IgY-Q46pOTb5_NPe\&q=85\&s=445efb0b9194cabca55079b74b3c3814) **1. Open Automations** Go to **Settings → Account → Automations**. **2. Create an automation** Create a new automation and provide the required details. **3. Configure the trigger** Select a trigger such as **Assignee change**, **Conversation status**, or **Variable value**. **4. Add trigger conditions** Configure the values that determine when the automation should run. If you add multiple conditions, choose whether **ALL** or **ANY** conditions must match. **5. Configure the action** Select the action you want WotNot to perform, such as **Send an email** or **HTTP Request** or **send agent response**, and configure its required settings. **6. Activate the automation** **Enable** automation. The automation will now run whenever its trigger criteria are met. ![Recording 2026 08 24 170120 2](https://mintcdn.com/wotnot/IgY-Q46pOTb5_NPe/images/Recording-2026-08-24-170120-2.gif?s=9637903d0c7aa0e7a9ffb970cbdd4329) > [!CAUTION] > > An automation must be activated before it can run. Saving an automation without activating it does not make it active. # Activate your automation Finally, switch the automation on to make it active and start running whenever the trigger conditions are met. You can check the last run status from the automation dashboard. ![Screenshot 2026 08 24 164622](https://mintcdn.com/wotnot/ez0GlzggSLvSJ5j6/images/Screenshot-2026-08-24-164622.png?fit=max\&auto=format\&n=ez0GlzggSLvSJ5j6\&q=85\&s=24a24991f69e55d432f9459815c7e0ee) You can also activate your automation by opening that particular automation and select the enable button. ![Screenshot 2026 09 15 115017 1](https://mintcdn.com/wotnot/PKybgkZax_5VziX5/images/Screenshot-2026-09-15-115017-1.png?fit=max\&auto=format\&n=PKybgkZax_5VziX5\&q=85\&s=28a52c882096bf8f97a7e05dc34e5a65) # Logs **Logs** are records of automations that happen within WotNot while a bot or conversation is running. ![Download](https://mintcdn.com/wotnot/IgY-Q46pOTb5_NPe/images/download.jpg?fit=max\&auto=format\&n=IgY-Q46pOTb5_NPe\&q=85\&s=0c6dd4bfbbaf383f9b24a1df0e5e447c) * Simply click **"Logs"** to see the complete history of your automation runs. * You can check the Logs and apply a **filter.** * Each log includes the related Chat or Ticket, run status, execution time, and detailed payload and response information — making it easier to monitor automations and troubleshoot issues. ![Image](https://mintcdn.com/wotnot/IgY-Q46pOTb5_NPe/images/image-495.png?fit=max\&auto=format\&n=IgY-Q46pOTb5_NPe\&q=85\&s=ca3ce7bf0874d2a3487132ddce56d78e) # Order of execution When you have multiple automations, more than one automation can match the same event if its trigger criteria are satisfied. Keep your automation rules specific to avoid unintended actions. * For example, if two automations listen for the same conversation status change, both can potentially match the event if their conditions are satisfied. # Troubleshooting > [accordion] My automation is not firing > > Check the following: > > 1. Make sure the automation is **active**. > 2. Verify that the configured trigger actually occurred. > 3. Check the trigger values and conditions. > 4. If multiple conditions are configured, verify whether **ALL** or **ANY** is selected. > 5. Test the automation with a conversation that clearly meets the configured criteria. > [accordion] My automation is firing more than once > > Check whether the trigger event can occur multiple times for the same conversation. > > For example, an assignee can change more than once or a variable can change to the configured value more than once. Review your trigger conditions and make them more specific if the automation should run only for a narrower set of conversations. > [accordion] My automation is firing for the wrong conversations > > Review the trigger conditions and make sure the configured values match your intended audience. > > If you have multiple conditions, check whether **ANY** is selected when you actually need **ALL**. Using **ANY** can cause the automation to run when only one of the conditions matches. > [accordion] My action is not working > > Check the action configuration. > > For **Send an email**, verify the recipient and email configuration. > > For **Fire an API**, verify the endpoint and request configuration. Also confirm that the external API accepts the request sent by WotNot. > [accordion] My automation conflicts with a live chat assignment rule > > Automations and live chat assignment rules solve different problems. Assignment rules determine how conversations are assigned, while automations perform configured actions when their trigger criteria are met. > > If an automation depends on an assignee change, verify that your assignment rules are not repeatedly changing the assignee and unintentionally triggering the automation multiple times. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.