Custom Connector get token first and then make an API call

[sasrsc]

I have a flow where I use the HTTP connector and get the token using a basic auth method. It works.
I then use the HTTP connector and use that token using a bearer auth method. I can repeat for multiple methods. It works.
Fine, but I ideally want to build a custom connector to make it cleaner for each method (Get this, Get that, Post this, Post that, etc). I've started this and it works.
But I'm not clear on 2 points...

1. How can I pass the HTTP token into a custom connector action as part of the custom connector. Is it as simple as using {mytoken} and putting that in the Headers of the Import from Sample?? 
2. Is there a way, to make the custom connector do the token call first and then the method (get this) as part of "one" action when viewing the customer connector in Power Automate. 

That would really clean this up. I'm just a citz dev but I've got this far so making headway slowly. I have been browsing for answers and found nothing.

[v-yueyun-msft]

Hi , @sasrsc 

According to your description, your API needs to call the API to get the token first, and then pass the token to the header and call other APIs.
For your needs, I think you can create multiple Actions directly in the Custom Connector. Your API to get the token is also one of the actions.
Other APIs define an Authentication in Headers to receive your token.

In other words, when you call a custom connector elsewhere, you need to call the action to get the token first, then get the token and pass it in.

Best Regards,

Yueyun Zhang

[sasrsc]

Yes, that is what I am doing now with multiple actions. (Get This, Get That, etc..). Sorry I didn't explain myself well enough.

The issue stems from the GetToken requiring the Basic method of authorization and all the other Actions using the API key method. There is a little documentation on using multiple authorizations methods (apparently you have to create that using CLI commands). The 2nd issue is that I'm still not clear on how you pass in info to be consumed by the authorization config (specifically the token which changes every hour). You can pass in parameters using {this param} to be used in the definition config (and I am using them) but it's not's apparent to me how you pass in parameters to be consumed in the security config. You are not allowed to put an Authorization Header on the Definition page if I understand properly.