Skip to content

[SAFE-EMAIL-TEST-2] PLU-386: make postman email test step send only to the pipe owner#1649

Open
ogp-weeloong wants to merge 1 commit into
feat/ses/safe-test-emails/tooltipfrom
feat/ses/safe-test-emails/action
Open

[SAFE-EMAIL-TEST-2] PLU-386: make postman email test step send only to the pipe owner#1649
ogp-weeloong wants to merge 1 commit into
feat/ses/safe-test-emails/tooltipfrom
feat/ses/safe-test-emails/action

Conversation

@ogp-weeloong
Copy link
Copy Markdown
Contributor

@ogp-weeloong ogp-weeloong commented May 27, 2026

Problem

When testing email, we want to always send the email only to the pipe owner. This prevents them from accidentally sending a real email to their target audience when testing.

Solution

High level: when calling postman's API, clear CC list and force recipient to pipe owner if the run is a test run.

We want to add a UX signal to let the pipe owner know that when they click test step in postman, the email will be sent to them.

I decided on showing a tooltip. However, I'm not 100% sure if tooltip is good enough - we may want to do a NUX / first time modal instead.

This PR

Adds a frontend extension for postman send email action to apply a new test step tooltip, and also updates the postman backend logic as described in the solution

Screenshot 2026-05-27 at 1 20 13 PM Screenshot 2026-05-27 at 1 20 25 PM

Tests

  • Check that when sending a test email, the email is sent only to the pipe owner (Cc list and configured recipient is ignored)
  • Check that published pipes send the email to the configured recipients & CC list people.
  • Check that the postman test step tooltip shows up when configuring postman email step
  • Check that the postman test step tooltip does not show up for other apps & actions

@ogp-weeloong ogp-weeloong requested a review from a team as a code owner May 27, 2026 05:15
@linear
Copy link
Copy Markdown

linear Bot commented May 27, 2026

PLU-386

@ogp-weeloong ogp-weeloong force-pushed the feat/ses/safe-test-emails/action branch from 1063774 to 33324e3 Compare May 27, 2026 05:16
Copy link
Copy Markdown
Contributor Author

ogp-weeloong commented May 27, 2026

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more


How to use the Graphite Merge Queue

Add the label lfg to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

@ogp-weeloong ogp-weeloong force-pushed the feat/ses/safe-test-emails/action branch from 33324e3 to b6a5124 Compare May 28, 2026 06:14
@ogp-weeloong ogp-weeloong changed the title PLU-386: make postman email test step send only to the pipe owner [SAFE-EMAIL-TEST-2] PLU-386: make postman email test step send only to the pipe owner May 28, 2026
Copy link
Copy Markdown
Contributor

@kevinkim-ogp kevinkim-ogp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, tested and verified it works

Sending a "Send email" test step previously delivered to whatever
recipients were configured on the step, which could spam unrelated
people while a builder iterated on a template. The action now rewrites
both `destinationEmail` and `destinationEmailCc` to `$.user.email`
when `$.execution.testRun` is true, and surfaces a `testStepTooltip`
on the Check step button so the user knows test emails will only go
to their own address.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Copy link
Copy Markdown
Contributor Author

Updating UX in #1675 as discussed over sync

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants