Hello everyone,
I need some help regarding the use of additionalScope when working with resources.
Basically, when I create a REST API, I can provide an additionalScope for it. However, when I consume specific resources provided by Retool, like AWS DynamoDB or S3, there doesn't seem to be a way to pass additionalScope.
My question is: is it also possible to define additionalScope when using these types of resources? I couldn't find a clear answer, and it would be really useful if this were supported.
Thanks in advance!
Hi @Guilherme_Tosi and welcome to the Retool community!
Yes, there is usually a way. For example, you can pass variables to a workflow as below:
If you send a screenshot of your resource/query we can help a little more.
Basically, I have a script that makes some async requests. I convert a token to base64 for authorization, and I would like to send the result of this query in the additionalScope of the putSiengeDevelopmentCredentials request too, because I get to useadditionalScope in createSiengeWebhook`.
example:
const token = await convertToBase64.trigger();
createSiengeWebhook.trigger({
additionalScope: {authorization: token}
})
.
.
.
await putSiengeDevelopmentCredentials.trigger({
additionalScope: {authorization: token}
})
createSiengeWebhook: has additionalScope (it's a custom resource)putSiengeDevelopmentCredentials: AWS DynamoDB resource (it doesn't support additionalScope directly
)
Can you share a screenshot of your resource putSiengeDevelopmentCredentials?
Is this in an app or in a workflow?
It's in an App. Below you can see the putSiengeDevelopmentCredentials GUI. Basically there's a script in this app that make some async requests, like convertDataToBase64and in that specific request, a set the result in a variable convertedSiengeIntegrationToken, but I would to remove it and use additionalScope instead.
When you build a Retool query using a built-in resource (e.g. DynamoDB via the GUI), you can already inject values directly into the JSON body or parameter editor using {{ }}. That’s why there is no explicit "additionalScope" option—you're literally doing the same thing already.
You already have dynamic variables—injected in real time—just like additionalScope would with a SQL query. Retool simply doesn't surface an "additionalScope" field because it's effectively unneeded for these resource types.
1 Like
