Add “Requester Email” and “CSAT Placeholder” variables to Action Flows? | The place for Zendesk users to come together and share
Skip to main content
Accepted

Add “Requester Email” and “CSAT Placeholder” variables to Action Flows?

Related products:Admin center
  • July 29, 2025
  • 2 replies
  • 2 views

We’re testing the Action Flows EAP and would like to send Zendesk CSAT surveys to end‑users via Slack direct message. Two additional variables would make this possible:

  1. Requester Email – exposes the requester’s primary email without adding a separate Look up user step.
  2. CSAT Placeholder – a variable (or support for classic {{satisfaction.rating_section}}) that renders the interactive survey block in Slack, just as it does in email.

These additions would let us build a single, fully automated flow:

  • Trigger: Ticket solved
  • Slack DM to requester: “Hi {{requester.first_name}}, thanks for contacting us! Please rate your experience: {{csat_placeholder}}

Benefits

  • Consistent CSAT delivery across channels (email + Slack).
  • Fewer manual follow‑ups from agents.
  • Cleaner flows (no extra user lookup or workarounds).

Thanks for considering these variables for the next Action Flows update!

2 replies

Daniel100
  • Employee
  • July 31, 2025

Hi @steven28 , thanks for your feedback! 

  1. Makes sense. I’ve captured this request in our backlog but it’s not prioritized at this stage.
  2. Sending an interactive survey block in a Slack message, with the Send slack message action is a new request. I’ve added this to our backlog for consideration.

Karl22
  • February 25, 2026

We are using Action Block for external responses, and we need the basic functionality of a placeholder in Action Flow so we can utilize the most out of it. Sometimes, we just need the placeholder as it is, but Zendesk security keeps modifying it, preventing a smoother connection with external services, and we had to do a lot of workaround the problem.