You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: "Send transactional emails through Autosend based on Dodo Payments events with high deliverability."
4
-
icon: "envelope"
2
+
title: "AutoSend"
3
+
description: "Learn how to use AutoSend's email API to send automated transactional emails for your Dodo Payments transactions, refunds, and payment events."
4
+
icon: "message"
5
5
---
6
6
7
7
## Introduction
8
8
9
-
Send professional transactional emails automatically when payment events occur. Deliver payment confirmations, subscription updates, and important notifications with Autosend's reliable email infrastructure and excellent deliverability rates.
9
+
The AutoSend and Dodo Payments integration enables you to automatically send real-time email notifications for all payment events, from successful transactions to failed attempts and refund confirmations.
10
+
11
+
Send transactional emails for payment events using AutoSend's powerful email API.
10
12
11
13
<Info>
12
-
This integration requires your Autosend API Key for authentication.
14
+
This integration requires your AutoSend API Key for authentication. You can find your API key in the AutoSend dashboard under Settings > API Keys.
13
15
</Info>
14
16
15
17
## Getting Started
16
18
19
+
Follow these steps to integrate AutoSend with Dodo Payments:
20
+
17
21
<Steps>
18
-
<Steptitle="Open the Webhook Section">
19
-
In your Dodo Payments dashboard, navigate to <b>Webhooks → + Add Endpoint</b> and expand the integrations dropdown.
22
+
<Steptitle="Open Webhook Section">
23
+
Navigate to the Webhooks section in your Dodo Payments dashboard.
24
+
20
25
<Frame>
21
26
<imgsrc="/images/integrations/autosend.png"alt="Add Endpoint and integrations dropdown" />
22
27
</Frame>
23
28
</Step>
24
29
25
-
<Steptitle="Select Autosend">
26
-
Choose the <b>Autosend</b> integration card.
30
+
<Steptitle="Select AutoSend Integration">
31
+
Choose AutoSend from the list of available integrations.
27
32
</Step>
28
33
29
34
<Steptitle="Enter API Key">
30
-
Provide your Autosend API Key in the configuration.
35
+
Provide your AutoSend API key for authentication. You can find your API key in the AutoSend dashboard under Settings > API Keys.
36
+
37
+
<Cardtitle="Learn how to create and manage API keys"icon="key"href="https://docs.autosend.com/api-keys">
38
+
Visit the AutoSend documentation for detailed instructions on creating and managing API keys.
39
+
</Card>
31
40
</Step>
32
41
33
42
<Steptitle="Configure Transformation">
34
-
Edit the transformation code to format emails for Autosend's API.
43
+
Set up JavaScript transformation handlers to customize email content based on payment events.
35
44
</Step>
36
45
37
46
<Steptitle="Test & Create">
38
-
Test with sample payloads and click <b>Create</b> to activate the email sending.
47
+
Test your webhook configuration to ensure emails are sent correctly, then create the integration.
39
48
</Step>
40
49
41
-
<Steptitle="Done!">
42
-
🎉 Payment events will now automatically trigger transactional emails via Autosend.
50
+
<Steptitle="Activation Complete">
51
+
🎉 Your AutoSend integration is now active and will automatically send emails for the configured payment events.
43
52
</Step>
44
53
</Steps>
45
54
46
-
## Transformation Code Examples
55
+
## Code Examples
47
56
48
57
### Payment Confirmation Email
49
58
59
+
Send a confirmation email when a payment is successfully processed:
-**Verify your sender domain**: Ensure your sender email domain is verified in AutoSend to improve deliverability and avoid authentication issues. Verified domains help prevent emails from landing in spam folders.
139
172
140
-
- Use verified sender domains for better deliverability
141
-
- Include both HTML and text versions of emails
142
-
- Personalize content with customer data
143
-
- Use clear, action-oriented subject lines
144
-
- Include unsubscribe links for compliance
145
-
- Test email templates before going live
173
+
-**Use dynamic data for personalization**: Use the `dynamicData` field to personalize emails with customer-specific information like names, payment amounts, and subscription details. Personalized emails have higher engagement rates.
174
+
175
+
-**Write clear subject lines**: Write descriptive subject lines that clearly indicate the email's purpose. Avoid spam-trigger words and keep subjects concise (under 50 characters).
176
+
177
+
-**Test before production**: Always test your emails before sending them in production. This ensures your email content renders correctly and all dynamic data is properly mapped.
178
+
179
+
## API Reference
180
+
181
+
For complete details on the AutoSend API, including all available parameters and error codes, visit the [AutoSend API Documentation](https://docs.autosend.com/api-reference/mails/send).
146
182
147
183
## Troubleshooting
148
184
149
185
<AccordionGroup>
150
186
<Accordiontitle="Emails not being sent">
151
187
- Verify API Key is correct and active
152
-
- Check that sender domain is verified in Autosend
188
+
- Check that sender domain is verified in AutoSend
153
189
- Ensure recipient email addresses are valid
154
-
- Review Autosend sending limits and quotas
190
+
- Review AutoSend sending limits and quotas
191
+
- Verify the API endpoint URL is correct: `https://api.autosend.com/v1/mails/send`
192
+
- Check that required parameters are present in the payload
155
193
</Accordion>
156
194
157
195
<Accordiontitle="Transformation errors">
158
-
- Validate JSON structure matches Autosend API format
159
-
- Check that all required fields are present
160
-
- Ensure HTML content is properly formatted
161
-
- Verify from email address is verified
196
+
- Validate JSON structure matches AutoSend API format
197
+
- Check that all required fields are present (`to`, `from`, `templateId` or `html`/`text`)
198
+
- Ensure email addresses are properly formatted
199
+
- Verify `templateId` is valid if using templates
200
+
- Check that `dynamicData` keys match your template variables
201
+
</Accordion>
202
+
203
+
<Accordiontitle="Template issues">
204
+
- Verify your template ID is correct and active in AutoSend
205
+
- Ensure `dynamicData` keys match the variables used in your template
206
+
- Check that all required template variables are provided
207
+
- Test your template independently in the AutoSend dashboard
0 commit comments