Transactional Email

SMTP Credentials

Generate and manage the SMTP username and password your application uses to authenticate transactional email through Leadpush.

SMTP credentials are the authentication layer for transactional sending through Leadpush. Your application, background job, or external service uses the generated username and password to open an SMTP session and send operational email from the workspace.

SMTP connection settings

When your application is ready to connect, use:

  • SMTP host: smtp.leadpush.net
  • Port: 587

Then authenticate with the username and password from the SMTP credential you created in the workspace.

What these credentials are for

Use SMTP credentials when:

  • an application needs to send password resets, login codes, receipts, or alerts through Leadpush
  • you want a separate credential per environment or integration
  • you need to rotate access without changing the verified sending domain itself

Each credential belongs to one workspace. Deleting that credential stops any system still using it from authenticating successfully.

When to create a new credential

Create a new SMTP credential when:

  • a new application or service needs its own authentication pair
  • you are separating production from staging or testing
  • you are rotating credentials after an incident or secret exposure
  • you want clearer ownership for a specific integration

Storage and rotation guidance

  • Store the generated username and password in a secret manager, environment variable set, or other secure credential store.
  • Use descriptive names so teammates can trace which application owns each credential.
  • Rotate by creating a replacement credential first, updating the application, testing it, and only then deleting the older one.
  • Remember that the password is only shown once at creation time.

SMTP credentials are only one part of transactional setup. Pair them with:

Troubleshooting