Take 10 minutes.
Get hours back every week.
Short walkthroughs that turn the platform into your operations team: automated pipelines, instant follow-ups, AI-handled admin. One video, one less thing to do manually.
How to Set Up Email Configs
Configure how TrustPager sends outbound email — sender name, sending address, reply-to, branding, verified custom domains, and optional Gmail routing.
Email configs control where outbound emails come from — the sender name, sending address, reply-to, and branding that recipients see. One config covers your automations, email marketing campaigns, and all other TrustPager-generated emails. If your team has Gmail connected, you can also nominate a Gmail account and alias for personal sends from the inbox.
Open email settings at https://app.trustpager.com/settings/email.
TrustPager Mail
TrustPager Mail is always active. It handles automations, email campaigns, and any email sent by the platform on behalf of your workspace. Configure it first before turning on any email automation.
Sender Name
This is the name that appears in the From field — for example, "Acme Consulting" or "Sarah from Acme". Set it at https://app.trustpager.com/settings/email under TrustPager Mail. Changes save automatically.
Sending Address
By default, outbound emails are sent from noreply@trustpager.com. You have two ways to use a branded address:
- TrustPager Mail handle: type a handle in the Sending Address field. For example, entering
acmesends fromacme@mail.trustpager.net. Replies route back into your TrustPager email inbox automatically. - Verified custom domain: verify a domain you own (see below) and then select it from the domain dropdown. Type the local-part — like
supportorhello— and choose your domain to send from an address likesupport@yourcompany.com. Replies go to that real inbox.
The sending address is workspace-wide. All automations and campaigns share it.
Verified Sending Domains
You can add and verify your own domain at https://app.trustpager.com/settings/email under the Sending Domains section. TrustPager generates two DNS records — a DKIM TXT record and a Return-Path CNAME — for you to add at your DNS host. No SPF or MX changes are needed; your existing inbox keeps receiving mail normally.
DNS tip: most registrars (Namecheap, GoDaddy, Cloudflare) automatically append your domain to the record Name field. Enter the relative host value shown on the Settings page, not the full hostname. For example, enter pm-bounces, not pm-bounces.yourcompany.com. The Settings page shows the exact value with a copy button for each record.
After adding the records, click Check. Verification usually completes within a few minutes; it can take a few hours depending on your DNS provider's TTL, and rarely up to 24-48 hours. Click Check at any time to re-check live status. For a step-by-step walkthrough, see https://trustpager.com/help-center/workspace-email-domain.
Default Workspace Email Address
The Default Workspace Email Address picker at https://app.trustpager.com/settings/email controls which rail the workspace uses for general outbound email. You can set it to TrustPager Mail (using either your @mail.trustpager.net handle or a verified custom domain address) or to a connected Gmail account. This applies to automations, form notifications, and one-to-one sends from the inbox. Email Blasts always use TrustPager Mail regardless of this picker.
Reply-To Email
When a recipient clicks Reply in their email client, the reply goes here — typically a monitored inbox like support@yourcompany.com or a team member's address. Set it in the Reply-To Email field. This is separate from the sending address and is required for TrustPager Mail to work correctly.
Branding
Email templates generated by TrustPager use your company logo, primary colour, and secondary colour. Upload your logo and set brand colours under the Branding section at https://app.trustpager.com/settings/email. A colour preview shows how they appear side by side before saving. PNG format, 200px height recommended for the logo.
Team Gmail (Optional)
If one or more team members have connected their Gmail at https://app.trustpager.com/account/connect and shared at least one alias with your workspace, a Team Gmail section appears at the bottom of https://app.trustpager.com/settings/email.
This section lets you nominate which connected Gmail account the workspace uses for personal sends from the email inbox. Automations and campaigns always use TrustPager Mail regardless — Team Gmail only applies to one-to-one emails composed from the inbox.
Gmail Account
Choose the team member whose Gmail you want the workspace to route through. The dropdown shows everyone who has connected Gmail and shared an alias with this workspace. Selecting a user saves immediately.
Sending Address
Once a Gmail account is selected, a second dropdown shows the send-as aliases available for that user. Choose the alias you want displayed as the sender — for example, info@yourcompany.com instead of the user's personal Gmail address. If you leave this blank, the user's default Gmail address is used.
Each alias can only be assigned to one workspace at a time. If an alias is already in use by another workspace in your account, it will not appear in the list.
Validation Rules (API and MCP)
The UI constrains what values can be written to email configs. If you write to email configs directly via the API or MCP — for example, using create_email_config or update_email_config — the same validation applies server-side. Writes that violate these rules are rejected with a structured error response.
All errors follow this shape:
{ "success": false, "code": "ERROR_CODE", "message": "Human-readable explanation.", "fix": "One-line actionable hint." }AI agents and integrations should branch on the code field, not the message text (which may change). The fix field is a plain-English hint safe to surface to a user.
INVALID_FROM_EMAIL
The from_email field must use either a @mail.trustpager.net handle or an address on a verified custom domain registered for the workspace. Writing an arbitrary domain address that has not been verified will be rejected. Set the sending address via the UI at https://app.trustpager.com/settings/email, or verify a domain there first before writing a custom-domain address programmatically.
ALIAS_NOT_CONNECTED
The gmail_sender_alias you specified is not in the connected Gmail account's verified send-as list. Gmail requires an alias to be added and verified in Gmail settings before TrustPager can send from it. The error message ends with the list of currently valid aliases: Available aliases: a@example.com, b@example.com. or Available aliases: (none yet — assign one at /settings/email). if none are set up yet.
GMAIL_USER_REQUIRED
You set gmail_sender_alias without specifying which connected team member's Gmail account owns that alias. Include the gmail_user_id field in the same write so TrustPager knows which OAuth connection to send through.
GMAIL_NOT_CONNECTED
The user specified in gmail_user_id has no active Gmail connection. Have that team member go to https://app.trustpager.com/account/connect and connect their Gmail, then retry the write.
MCP and API Access
Email configs are fully accessible via the TrustPager API and MCP. Use list_email_configs to see all configs for a workspace, get_email_config to retrieve a specific one, create_email_config to add a new config, and update_email_config to change an existing one. get_email_capabilities returns what the workspace is capable of sending based on the current config. These tools let agents and automations read and modify email config programmatically without going through the UI.
Example: create a new email config via MCP or API:
create_email_config({
from_email_handle: "acme",
from_name: "Acme Consulting",
staff_email: "support@yourcompany.com"
})from_name sets the display name in the From field. staff_email sets the reply-to address (labelled Reply-To Email in the UI). from_email_handle sets the sending handle (the part before @mail.trustpager.net, or the local-part of a verified custom domain address if one is configured). These are the canonical API field names — use them in all programmatic writes.
Troubleshooting
Automated emails are not sending. Check that TrustPager Mail is configured with a Sender Name and Reply-To Email at https://app.trustpager.com/settings/email. If neither field is filled, the platform cannot dispatch emails.
The Team Gmail section is not visible. The section only appears when at least one team member has connected Gmail and shared an alias with this workspace. Have the relevant team member go to https://app.trustpager.com/account/connect, connect Gmail, and tick at least one alias for this workspace.
An alias is not appearing in the sending address dropdown. Each alias can only be assigned to one workspace. If the alias is already assigned to another workspace in your account, it will be hidden. Unassign it from the other workspace first, then return here to select it.
My verified domain is not passing the Check. Confirm you entered the relative host value (e.g. pm-bounces), not the full hostname — most DNS hosts append the domain automatically. Give it a few minutes for propagation, then click Check again. If it has been more than an hour, double-check that both records (DKIM TXT and Return-Path CNAME) are saved and active in your DNS host's control panel.
Replies to automated emails are not coming through. Confirm the Reply-To Email at https://app.trustpager.com/settings/email is a real, monitored address. If your team has a Gmail inbox connected in TrustPager, replies to that address will appear in the inbox automatically.
An API or MCP write to email config is being rejected. Check the code field in the error response and refer to the Validation Rules section above for the specific fix. The most common cause is writing a domain address that has not been verified in the workspace, or specifying a Gmail alias that has not been verified in Gmail settings.
Two ways to
meet FinalPiece.
Talk to Evie right now, or book a real human for a deeper walkthrough. Whichever feels right.
Pick up the phone.
Hear her in 10 seconds.
- RealHer voice passes for human.
- SmartKnows your prices, hours, and trade.
- PatientPolite, attentive, never has a bad day.
Pencil us in.
60 minutes with a real human · Google Meet · Free.