Knowledge Base

Transactional Email

Set up transactional email sending through Leadpush SMTP with verified sender identities and application-ready credentials.

The Transactional Email section is for product and engineering teams that send operational email through SMTP. Use it when you need to prepare Leadpush for password resets, login codes, account alerts, receipts, verification messages, or other event-driven mail that should send immediately from your application.

Sections in this category

What this category helps you do

Use these guides to learn how to:

  • set up the required prerequisites for SMTP-based transactional sending
  • verify the domain and sender identity used by operational mail
  • generate SMTP credentials for the application or service that will authenticate to Leadpush
  • send a transactional email through SMTP with a concrete application example
  • connect transactional-email planning with the existing workspace-level setup guides in the dashboard

Start here

Start with SMTP Setup for the full order of operations. Open Domain Setup when you need to verify DNS and create the sender identity your application will use. Use SMTP Credentials when you are ready to generate the username and password your app will store. Then use Sending an Email when you want a concrete SMTP example to test from your application.

Why this matters

Transactional email setup is not just about opening an SMTP connection. Leadpush needs a verified domain, a verified sending address, and a valid SMTP credential before your application is ready for reliable live delivery. Organizing these steps into one category makes it easier for teams to move from product requirements to workspace setup without missing a dependency.