Hi,
I’m working on an image generation site, I have API’s with webhooks and backend workflows that save the image output i receive from replicate into the file manager and makes changes to the database with name, created by, etc… this works well.
But in the file manager, when saving the image into the bubble storage from the webhook, it comes as an anonymous user – can the file have the user ID of the actual creator (as in the user who requested the prediction)?
Does the API service let you dynamically include what headers are sent back with the webhook? If so you can setup API keys per user and have the webhooks come in authenticated as specific users Build a Rest API - #5 by chris.williamson1996
2 Likes
It’s been a year, @surveylupa you might have already solved the problem. I recently got into need of attaching user to the image generated, what I did is sent the user’s unique ID into replicate input (Replicate return’s the input along with it’s output) and then in make change to a thing I just added a constraint of user’s unique ID in BE workflow.
Can I ask — why do you specifically need the user ID to be associated with the file in the File Manager?