Your first email integration should support a real moment in your product. A customer pays, requests access to an account, or books time with your business. Start with the moment your product needs to handle at launch. You do not need to build all three workflows before connecting one useful email.
Choose the customer action, then the message
If customers pay through your product, start by checking how you will provide a receipt for a confirmed payment. If they sign in with a password, decide how a requested password reset will reach the account owner. If your business takes bookings, an appointment confirmation can put the agreed time and next step in one place.
There is no universal ordering. A booking service with no password login may need confirmations first. An account-based application may need its reset flow before it takes payments. Write down the customer action your launch supports and the information that customer needs afterward. That becomes the scope of your first integration.
Make a short message checklist
For a receipt, identify the confirmed payment, the recipient and the purchase details you need to show. For an appointment confirmation, identify the booking, the agreed time and the next step. For a password reset, identify the genuine reset request and the intended account owner. These are planning examples; use the fields supported by your chosen approved template.
In Emailer API, select the approved template for the supported event. The current sending contract uses fixed template versions and verified customer events. It is not an unrestricted editor for arbitrary email bodies. Keep the first message focused on the customer action it confirms.
Know which system confirms the event
A message should follow an event your application can establish. Emailer API uses Stripe verification for payment receipts and paid orders. Other supported transactional events use a signed application callback. Your callback must look up the real event in your application and return the expected facts.
For example, your application should look up the actual booking when authorizing an appointment message. It should not turn an arbitrary incoming request into a new booking just to satisfy a check. The setup assistant can prepare integration code, but your application still supplies its own event lookup. Read the setup guide for that connection before sending.
Check the connection before relying on it
Work through the sending domain, approved template and application connection in the onboarding wizard. Use an isolated development environment for your application logic, then inspect the intended recipient and rendered message through the supported validation flow before an authorized real send.
Keep the result of each check. If validation fails, identify the missing domain, template or event requirement before trying again. If the API accepts a send with status 202, that means it is queued. Use the later delivery logs and webhook events to understand what happened; acceptance alone does not establish delivery or inbox placement.
This guide is a planning checklist, not a runnable example or a report of a completed delivery test. The API reference and the generated integration describe the exact fields your application must supply.
Add the next workflow when its checks are ready
After the first connection works through its validation and observed delivery checks, review the next customer action your product needs. There is no fixed number of days that makes another workflow ready. Repeat the domain, template, event and result checks for the new use case.
Plan volume against your actual account allowance and the shared delivery budget. New Emailer API accounts start at 100 recipient reservations per day and 3,000 per calendar month; shared capacity and sending safeguards also apply. These are allowances, not reserved throughput. The pricing page explains the current limits.
Free for Life includes the setup assistant, so you can start with a clear use case inside your account. Choose the email your product needs first, connect its real event, and build from that verified starting point.
Sources and next steps
- Emailer API pricing and current limits
- Transactional email setup guide
- Email domain and DNS setup guide
Start free with setup help included · Read current plan limits
Reviewed by the Emailer API editorial assistant against the linked documentation. This guide explains the documented workflow; it is not a report of a new integration test.