I was creating a flow where i wanted to connect my flow to Austin to create an action but it was not happening due to midway authentication - please let me know if you have any solution to work on this - and if for now there is no solution can this features comes as connector.
Hi @yadavcn
Welcome to the Quick community!
Could you help me understand a bit more about your setup? When you mention Austin, could you clarify which service or tool you’re referring to? For example, is it Asana, Atlassian, or perhaps another platform?
Hi @Xclipse,
I am creating a Flow where it analyzes a QuickSight dashboard and generates output based on a prompt. This output should then be pushed into AUSTIN to create an action. If you can share your alias, I can give you access for better understanding.
Currently, the Flow is working up to the point where it generates the output from the prompt. However, I am stuck at the login page as AUSTIN requires Midway authentication. I tried using the UI Agent, but I am unable to authenticate through it.
AUSTIN is a completely different platform — it is Amazon’s internal Environment, Health, and Safety (EHS) management platform used across Amazon’s global operations to manage workplace safety and compliance. There is currently no native connector available for it in Amazon Quick.
Is there any workaround for Midway-authenticated platforms, or could this be considered as a future connector/integration?
Hi @yadavcn
Thank you for the detailed explanation. I understand your use case clearly. You’ve built a flow that analyzes a QuickSight dashboard, generates output from a prompt, and you’d like to push that output into AUSTIN to create an action.
Unfortunately, Midway authentication is designed for interactive, user-initiated sessions and does not support programmatic or automated access including through browser-based UI agents. This is a security-by-design constraint, and there is currently no workaround available within Amazon Quick to bypass this.
I’ve marked this as a feature request to promote visibility with the product team.
Hi @yadavcn,
Just wanted to inform you that I will leave this post marked as a Feature Request and archive it so that the AWS Team can address this further.
Thank you!