Skip to content

Include action name and form data in action approval emails - #14

Draft
suraj-ranganath wants to merge 1 commit into
mainfrom
suraj.ranganath/automation-request-email-details
Draft

Include action name and form data in action approval emails#14
suraj-ranganath wants to merge 1 commit into
mainfrom
suraj.ranganath/automation-request-email-details

Conversation

@suraj-ranganath

Copy link
Copy Markdown
Collaborator

Summary

Requestable action/automation approval emails were too generic: approvers had to open the request to see what was asked for, and requestors only got a generic “your action is submitted” notice.

This change keeps the existing access-request approval flow and adds the customer-visible details from Pylon #13007:

  • Action Name on the approver email, the requestor confirmation email, and Slack copy
  • Form data when the request includes it (omitted when not applicable)
  • Secret-looking form fields are redacted; session/agent internals are not shown as form data
  • The same Action Name and form data are stored on the access request and shown on the review UI so approvers are not flying blind if they do open the request

Customer evidence

Test plan

  • python3 platform/test_action_approval_emails.py
  • python3 platform/test_mcp_gateway.py
  • python3 platform/test_runtime_execution.py
  • python3 demo/run_demo.py all

Requestable action approval emails were generic unless the approver
opened the request. Persist Action Name and form data on the access
request, and put both in the approver email, the requestor confirmation,
and Slack copy.

Co-authored-by: c1-squire-dev[bot] <c1-squire-dev[bot]@users.noreply.github.com>
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.

1 participant