Quick Flow Action Steps Not Executing — Outlook & Slack Connectors (Custom User Based OAuth)

Q&A
,
1

Hi everyone,

I’ve built Quick Flows that generate content and then execute action steps (CreateDraft in Outlook, Send Message to User in Slack). The Flows run correctly through the generation steps, but the action steps either don’t execute or behave inconsistently.
What’s Happening:

  1. Outlook (Amazon Outlook V2): The CreateDraft action works in my Flow, but requires a manual “Review required for Action” approval click before it executes. Is there a way to disable this review requirement so the Flow runs fully automatically?

  2. Slack (PXT Slack & PXT Slack V2): The Send Message to User action works perfectly when I use it directly in Quick chat. However, when I use the same connector as an action step in a Flow, it doesn’t execute — the Flow says it completed but no message is actually sent. Same auth type as Outlook V2, which does work in Flows.

My Questions:

  1. How do I disable the “Review required for Action” approval step in Flows so action steps execute automatically without manual confirmation?

  2. Why would a Slack connector (Custom user based OAuth) work in chat but not execute as a Flow action step — when an Outlook connector with the same auth type does work in Flows?

  3. Is there a specific permission, scope, or configuration needed to enable Slack connectors for Flow action step execution?

What I’ve Already Tried:

  • Verified both Slack connectors show Status: Ready

  • Confirmed authentication is current (Custom user based OAuth)

  • Tested both PXT Slack and PXT Slack V2 — same result

  • Confirmed the same Slack action works perfectly in direct chat

  • Referenced the Nov 2025 thread on Outlook integration (Brett’s suggestion about service auth)

Any help is appreciated. Thanks!

-– Jake

2

Hi @mcnajake and welcome to the Quick Community!

Specifically for your Outlook “Review required for Action” prompt, this is by design to keep a human in the loop. Quick Flows require manual confirmation before executing write actions (sending emails, posting messages, etc.) as a safety layer against AI prediction errors. The way to make it fully automatic is through scheduling. When you set up a schedule for your Flow, there’s an “Action permissions” step where you can toggle on “Run with no confirmation”. This should auto-submit the action forms without waiting for you to approve each one (Scheduling your Amazon Quick Flows - Amazon Quick).

One thing to note though, this only applies to scheduled runs. If you’re running the Flow manually/on-demand, there’s currently no way to bypass the review step. That’s a known gap and something the community has requested, but for now scheduling is the only path to fully hands-off execution.

Now the behavior you’re experiencing with your Slack connector is a bit odd. Before jumping to a support ticket, I’d check your Flow run history and see if any of those runs are actually stuck in a “waiting for input” state. It’s possible the Slack action is pausing for review (like Outlook) but you’re not catching the notification. That may explain why it says “completed” but no message is sent.

If that’s not it, then I’ve seen a few instances of this silent failure behavior in the community and my guess is that it may come down to how the OAuth session is carried into the Flow execution context. It’s especially odd if you’ve properly configured your action step and the output says it completed but nothing actually happened. With that, I would suggest creating a support ticket and the support team will be able to further investigate into the cause of this. Please refer to this resource on how to create a support ticket (Case management - AWS Support).