> For the complete documentation index, see [llms.txt](https://docs.ubiquity.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ubiquity.co.nz/documentation/channels/email/first-time-setup.md). # First Time Setup Before you can send emails through UbiQuity, you need to complete two steps: configure your database for sending email, and make sure you have contacts in your database to send to. *** ### Configure your database Your database needs to be set up with the correct fields for email sending before any mailouts can go out. This includes fields for managing opt-outs and bounce handling. Follow the database configuration guide to complete this setup. If your account has already been configured for email, you can skip this step. *** ### Add contacts to your database You will need contacts in your database before you can send a mailout. Contacts can be added in four ways: * **Subscribe form** - set up a web form that adds contacts when they sign up * **File import** - upload a contact list using the import process * **Connectors** - add contacts into your database using a connector * **API** - add contacts programmatically via the UbiQuity API Once your database is configured and you have contacts in place, you are ready to create your first mailout. See Mailouts to get started. --- # 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://docs.ubiquity.co.nz/documentation/channels/email/first-time-setup.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.