SMTP Configuration
Connect and manage SMTP routes for Email delivery inside SendFlow.
On this page
Overview
SMTP configuration helps SendFlow teams keep Email routing that stays testable, readable, and team-owned organized inside one workspace instead of scattering setup and campaign work across disconnected tools.
Use this guide as a practical operating reference for admins, staff, and campaign managers who need repeatable workflows.
What to manage
The goal is to keep the workspace readable for the whole team while making sure the data, setup, and delivery flow stay accurate.
When ownership is clear, SendFlow becomes easier to scale across audiences, templates, campaigns, and sending infrastructure.
- Store SMTP details accurately and securely.
- Keep routing names readable for campaign operators.
- Separate test routes from production routes.
- Confirm the route works before live sends depend on it.
Recommended workflow
Use a simple operating flow whenever your team is working on smtp configuration.
This keeps planning, review, and execution aligned before anything goes live.
- 1Open the SMTP configuration area in the workspace.
- 2Add or update the SMTP credentials and route details.
- 3Name the route so the team can identify it later.
- 4Send a test or validate the connection if available.
- 5Use the route in a draft campaign before broad rollout.
Review checklist
A short review step usually prevents configuration drift, wrong audience targeting, or noisy campaign logs later.
Ask a second team member to confirm changes when the guide affects live delivery, routing, or workspace-wide assets.
- Credentials are valid and current.
- The route name is clear for the team.
- Test and production routes are not confused.
- Campaign operators know when to use this route.
Routing mistakes usually show up at launch time
Keep SMTP routes explicit and tested so the team does not discover a bad credential or wrong route only after scheduling a live send.