> For the complete documentation index, see [llms.txt](https://guides.noloco.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.noloco.io/~/revisions/4ycMT0EcUe4aYSGLpT5Z/workflows/workflows/send-automated-emails.md). # Send automated emails {% embed url="" %} One of the best use cases of workflows is to notify team members when records are either created or updated via your Noloco app. In this video, we set up a workflow to notify the team manager when a new 'Product' record has been created via a native form in our Noloco app. We talk through: * Workflow set-up * Different options for triggers and actions * How to populate the email with dynamic data from the new record * How to attach files to the email * How to link to the new record page from the email * Testing our new workflow #### Setup the 'Send Email' action Send an email to one (or many) email address(es). \ An email action has the following fields: * **To -** The address to send the email to. If you want to send to multiple, separate them by commas * **Subject** **-** The email's subject * **Message -** The email's message. This can be as long as you want. * **Call-To-Action Text -** When provided, will render as a CTA button text * **Call-To-Action URL -** When provided, the link of the CTA button
--- # 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://guides.noloco.io/~/revisions/4ycMT0EcUe4aYSGLpT5Z/workflows/workflows/send-automated-emails.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.