I’m using Glide’s “Trigger Webhook” action to send a payload to my backend, and I’m trying to include a custom field called session_patch_id as a shared secret for basic authentication.
In my test environment (like webhook.site), I can see the session_patch_id sometimes appears in the JSON payload — but other times it’s completely missing, even though the field is hardcoded into the webhook body.
That does seem odd.
What do you see in the Glide workflow run logs? Is it also missing from there?
You say that the value is stored in your “Admin” table. Is that also your User Profiles table?
If not, are you running the workflow in the context of your Admin table?
If not, how is the workflow accessing the value?
The payload I showed before is what I see in the run logs when I send to webhook.site. When I send to my backend, my code is rejecting with a 401 because its not passing my authentication.
Admin table is my user profiles table yes.
I am not running my workflow in the context of the admin table. The workflow is accessing the value through user profile which has been working fine for the reader_id
Only other thing I can think of is are you triggering the workflow as the same user every time?
And does that Session column have a value in every row in your User Profile table?
And again, what do you see for the data payload sent in the workflow run log?
I have even tried deleting the session column and creating a new one. Renaming the column. Doesn’t work. I could try putting that value in a different table, but don’t love that as a solution. A bit bummed this functionality isn’t very consistent. It must be user error though right? Many others would be experiencing this behaviour too…
I only created it because I realised I couldn’t send a secret key in glide headers. So created a secret key on the user table. Then I named it something “non obvious” like session_patch_id because I thought maybe glide didn’t like the fact that I was passing my secret key in the payload.
