> For the complete documentation index, see [llms.txt](https://docs.emailflow.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.emailflow.so/welcome-to-emailflow.md). # 💌 Welcome to Emailflow ### What is Emailflow? Hello and welcome to Emailflow! We're excited to have you here. Emailflow is a no-code platform designed to simplify the way you handle transactional emails and PDFs for your company. From uploading email templates to generating PDF attachments, Emailflow offers you the tools you need to make your workflow as smooth as possible. ### Who is it For? Whether you're a startup looking to get off the ground, a small business wanting to professionalize your email communications, or a larger enterprise in search of a robust solution for managing transactional emails and PDFs, Emailflow has a plan to suit your needs. ### Why Choose Emailflow? * **Ease of Use**: With our intuitive dashboard, you can set up and manage your email campaigns and PDF templates without any coding knowledge. * **Flexibility**: From a free plan to usage-based pricing, Emailflow is designed to grow with you. * **Powerful Templating**: Our HTML-based templating system allows you to create dynamic, personalized emails and PDFs with ease. * **Insightful Analytics**: Keep track of your emails with our logs and deliverability status features. * **Customer Support**: Depending on your plan, you can get support via email or chat, and even priority support for urgent issues. Thank you for choosing Emailflow. We're excited to be a part of your journey! --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.emailflow.so/welcome-to-emailflow.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.