> For the complete documentation index, see [llms.txt](https://thisdot.gitbook.io/data-mapper-for-mailchimp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://thisdot.gitbook.io/data-mapper-for-mailchimp/workflows/configure-mandrill.md). # Configure Mandrill Before using Stripe workflows, make sure you are subscribed to a plan that supports them. If you'd like to see what features are included in each plan, visit our pricing page . Once you're subscribed to a compatible plan, you'll also need to configure Mandrill before you can start using Stripe workflows to send transactional emails. Mandrill is Mailchimp's transactional email service, designed to send automated, one-to-one emails triggered by user actions — things like order confirmations, receipts, or purchase summaries. Unlike standard marketing emails, transactional emails are sent to individual contacts based on specific events, which is why a dedicated service like Mandrill is required. The steps below will walk you through retrieving your Mandrill API key and configuring your Data Mapper account to use it, so that your Stripe workflows can send transactional emails automatically. ### Getting a Mandrill API key To connect Mandrill to your Stripe workflows, you'll need a Mandrill API key. You can find your existing keys or create a new one in your Mandrill account . If you already have an API key saved for this purpose, you can skip ahead and use that key when configuring your Data Mapper account in the next section. If you don't have an API key yet, you can create one by clicking the "Add API key" button. A dialog box will appear displaying your newly generated key. Make sure to copy and save this key somewhere secure — once you close the dialog, the full key will not be accessible again.
For now, go ahead and click "Copy key." ### Configure your account with Mandrill #### Via onboarding Where you enter your Mandrill API key will depend on whether your Data Mapper account has already been onboarded. If you're currently in the middle of onboarding, you're likely already on the screen prompting you for your Mandrill key.
Paste your newly created or pre-existing API key into the input field labelled "Mandrill API key" and continue through the remaining onboarding steps. If you complete onboarding without entering an API key — whether you skipped the step or something went wrong — don't worry. You can always add or update the key later through the Data Mapper settings page, which is covered below. #### Via the settings page If your account is already onboarded, or if you need to add your key after the fact, navigate to the Data Mapper settings page and scroll to the bottom. You'll find a section labelled "Mailchimp Transactional Email" — this is where you'll link Mandrill to your account. Paste your API key into the input field and save your settings when prompted. Once saved, your Data Mapper account will be configured to send templated transactional emails through your Mailchimp account whenever a Stripe workflow triggers one. To confirm the key was saved successfully, refresh the page and scroll back down to this section. You should see a partially masked version of your key displayed, indicating that Mandrill is connected and ready to use. --- # 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: ``` GET https://thisdot.gitbook.io/data-mapper-for-mailchimp/workflows/configure-mandrill.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.