Skip to content
Discussion options

You must be logged in to vote

Filed as an internal support discussion as well, for posterity / future readers:

Currently, we do not parse header literal values even if they are templated values .
You can try modifying your action to one of these approaches
Choose select "From env var" value from dropdown while defining headers in create action form and pass your third party token env var to it.
Choose "Forward client headers to webhook" and then pass dynamic value of token from your client in form of headers while querying against Hasura
Consume your token from action input payload in your backend middleware and send it as headers forward to your business logic

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by ajohnson1200
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
k/enhancement New feature or improve an existing feature t/gql-services
2 participants