API works great but is seems not to reauthenticate in a worflow. After I re-auth manual it works. What can be the cause? Authentication is time based.
After calling I store the token as "access_token". I also store a expire_in variable
Tested the time mechanisme and it works fine:
So what can be the reason retool in not reauthenticating when running the workflow?
As far as I know custom auth is not supported in workflows at this time. Last I checked I couldn't find this stated in the docs either but when opening a ticket I saw
I executed the auth flow within the workflow for the time being. It's not ideal but works for now
@matth Thanks for the assist!
@Etuzy As noted above, resources with custom authentication are not currently supported. This is something that we have on the roadmap and will be tackling. I don't have an ETA right now, but will update you all here as I get any additional information. I'll also move this over to Feature Requests. Thanks!
Hey - know that you've replied to this relatively recently, but was wondering if there have been any changes/updates to support custom authen. in retool workflow?
@josh_woong No updates at this time, we'll let everyone know in this thread when we have any additional movement on the internal ticket. Thanks!
Checking in on this feature request; Any movement?
Add a +1 from me on the internal ticket.
Until this gets released, the docs should really reflect that this isn't possible yet.
(Better yet: add a disclaimer in-app when setting up custom auth)
+1 Any updates on when this will be supported?
Are there any updates on when this will be supported?
Hey @nikolajs, no updates as of right now. This is still in our backlog and not currently prioritized. I've added your plus 1 to the internal request. Thanks!
Hi. That's weird. I used to use an old version of Retool, when Workflows was still on "beta".
And my webhook triggered workflows used to work like a charm with custom authentication. It worked like this for months.
I built the exact same thing on a recent Retool instance, and it didn't work. I never thought it wasn't supported, as it used to work before...
Anyway, this would clearly be a plus.
Hi @Emeric_LEBON,
Our apologies, that is a very odd case that your previous work flow worked and now does not.
Likely due to a wide variety of changes we are making to the product, this might be due to fixing another issue that the custom auth tooling must be set up in a different way.
Also in terms of status updates, as of an month ago this ticket was designated as ready for work and just needs to be assigned to an engineer. Bear with us as we have a lot of projects in the works but can hopefully fix this soon!
+1 on this, been waiting a long time to give our internal users a good user experience
+1
+1
