> For the complete documentation index, see [llms.txt](https://software-help-docs.gitbook.io/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://software-help-docs.gitbook.io/knowledge-base/software-guide/workflow-triggers/workflow-tigger-email-events.md). # Workflow Tigger: Email Events *In this article you will find out how to create a workflow trigger: Email Events and the scenarios on why it would be used* ***Please Note:** This trigger only works for Mailgun* 1. Click the “**Add New Workflow Trigger**” button * This will pull up a selection tab on the right of your screen {% embed url="" %} 1. Scroll down until you see the “**Events”** column * Click on the “**Email Events**” button * This will be triggered based on what happens within a particular email {% embed url="" %} 1. Select the blue “Add filters” button {% embed url="" %} 1. Next under the **Standard Fields** drop-down select the “**Event**” option {% embed url="" %} 1. Select the filter type that applies * ***Bounced**: an automatic trigger by an email bouncing* * ***Clicked**: someone clicked on an email* * ***Complained**: someone marked it as spam (good for filtering over the list that way you do not get marked for spamming too many times because the account can get flagged)* * ***Opened:** can trigger based on someone opening an email* * ***Unsubrcided**: someone unsubscribing to an email* {% embed url="" %} 1. Example: let’s trigger the automation as if someone “**Opened**” an email 2. Click the blue “**Add filters**” button * *You will have to specify which email; in this case only works if this email is in another **Workflow*** {% embed url="" %} 1. Once completed this will pop up a drop-down option. Click the dropdown “**˅**” button {% embed url="" %} 1. In the **Standard Feilds** option select “**In workflow**” * Now click the expand button; * *This will give you the ability to choose any of the workflows previously created* * *In This Example: We will select the “**Meet with Billy Calendar**”* * *Letting you know someone opened the email that is in the “**Meet with Billy Calendar**”* * *You have now set up this trigger that will let you know the email has been opened* {% embed url="" %} 1. Please make sure you click the green “**Save Trigger**” button before closing out of the trigger {% embed url="" %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://software-help-docs.gitbook.io/knowledge-base/software-guide/workflow-triggers/workflow-tigger-email-events.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.