Skip to content

Multiple senders per integration are hard to use – no sender selection at send time #418

Description

@sebastianhochreiter

Problem

Notifuse allows adding multiple senders to a single email integration (SES, SMTP, etc.).
However, there is currently no way to choose which sender to use when creating or sending a Broadcast or a Transactional notification in the UI.

The sender is only selectable at the Template level (sender_id).
If nothing is set on the template, the system always falls back to the integration’s default sender.

This is unintuitive for most users:

  • Users naturally expect to choose the “From” address when creating a campaign or sending a transactional email.
  • Having multiple senders in an integration is almost useless if you can only change the sender by editing the template every time.
  • The only place where a per-send override currently exists is the Automation Email node (from_override).

Expected behavior

Users should be able to select the sender (from the list defined on the active integration) at the following places:

  • When creating / editing a Broadcast
  • When sending a Transactional notification from the UI
  • (Optionally) as an override when calling the Transactional API

The template-level sender_id can remain as a default, but it should be overridable at send time.

Current workaround

  1. Edit the template and change the sender_id before every send, or
  2. Create duplicate templates (one per sender).

Both workarounds are cumbersome and error-prone.

Suggestion

Add a simple sender dropdown (populated from the active marketing/transactional integration’s sender list) in the Broadcast and Transactional send UIs.
Keep the template’s sender_id as the default value.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions