Accessing application client id in Complement Token Flow actions
Original message was deleted
RHi @hughp0920 thanks for your question, I will get back to you soon! 
Rhi @hughp0920 I am discussing the problem with an engineer within the team, I will get back to you
SHi @hughp0920 unfortunately I have to tell you that you didn't miss anything, the information is currently not available in the action.
I would recommend creating an issue on github, so that we can plan it.
As I'm currently working on actions v2 I can tell you that the plan is to make it equal to actions v1, but if necessary this could be expanded as well.
Additionally to that, if it's regarding the information of created access tokens, you could also use the events API https://zitadel.com/docs/guides/integrate/external-audit-log#events-api.
If you have specific requirements which we can help with generally, the best way would be to book a discovery call https://zitadel.com/contact
I would recommend creating an issue on github, so that we can plan it.
As I'm currently working on actions v2 I can tell you that the plan is to make it equal to actions v1, but if necessary this could be expanded as well.
Additionally to that, if it's regarding the information of created access tokens, you could also use the events API https://zitadel.com/docs/guides/integrate/external-audit-log#events-api.
If you have specific requirements which we can help with generally, the best way would be to book a discovery call https://zitadel.com/contact
ZITADEL • Identity infrastructure, simplified for you
We are here for you. Find a way to contact us via email, support, chat, or scheduling a discovery call.
This document details integrating ZITADEL with external systems for streaming events and audit logs.
