If your workspace has more than one Gmail alias connected — for example, support@yourcompany.com and advisor@yourcompany.com — you can now tell each automation exactly which alias to send from. Previously every Gmail automation used whichever config happened to be returned first, so all sends landed on the same address regardless of intent.
Where to Find It
Open any automation that uses a Send Gmail Email action, or create a new one. In the action wizard, the first step is Send From. When you select Company Gmail, a second field — Send From Alias — appears directly beneath it.
The dropdown lists every Gmail email config your workspace has set up at https://app.trustpager.com/settings/email. Each entry shows the config name and the alias address, for example: Advisor Inbox — advisor@yourcompany.com (default). The default config is pre-selected when you add a new action.
The Send From Alias dropdown only appears for Company Gmail. If you select Primary Assignee instead, TrustPager resolves the sending account from the opportunity's assignee automatically — there is nothing to configure.
Two Sender Modes
- Company Gmail — sends from a workspace alias configured in Email Settings. Use this for automations where you want a consistent, role-based identity (support@, advisor@, info@).
- Primary Assignee — sends from the personal Gmail of whoever is assigned to the opportunity at the time the automation fires. The assignee must have Gmail connected at https://app.trustpager.com/account/connect; if not, the action fails.
Existing Automations
Automations you built before this update keep working without any changes. The operation falls back to your workspace's default Gmail config (the one marked as default in Email Settings), then to the first available Gmail config if none is marked as default. No re-configuration is needed unless you want to change which alias a specific automation uses.
The next time you save an existing automation through the wizard, it will persist an explicit alias choice — so the fallback only applies to actions that have never been edited since the update.
Setting Up Multiple Aliases
Each alias in the dropdown corresponds to a separate Gmail email config in your workspace. To add an alias, go to https://app.trustpager.com/settings/email and connect an additional Gmail account or assign an additional send-as alias. Each connected alias is then available as its own entry in the Send From Alias dropdown across all automation wizards.
Troubleshooting
The Send From Alias dropdown is empty. No Gmail email configs are set up for this workspace. Go to https://app.trustpager.com/settings/email, connect a Gmail account, and assign at least one send-as alias to the workspace.
An alias I expect is not in the list. Each alias can only be assigned to one workspace at a time. If the alias is assigned to another workspace in your account, it will not appear here. Unassign it from the other workspace first at https://app.trustpager.com/settings/email, then it will appear.
The automation is sending from the wrong address. Open the action in the wizard and check the Send From Alias field. If the field is blank or the wrong config is selected, choose the correct alias and save the automation again. Going forward the explicit selection is persisted so the fallback logic no longer applies.
Primary Assignee fails with a connection error. The assignee listed on the opportunity has not connected their personal Gmail. Direct them to https://app.trustpager.com/account/connect to complete the connection.
