NYou could use the vanilla tRPC client if you need, or a mutation if that’s appropriate
NIf it’s going to drive the UI in any way it would be better to set some state which then triggers a useQuery
NAnd if the UI doesn’t need it, maybe move the extra API calls inside tRPC and just make the one mutation call in onsubmit?
NGot it, I do the same stuff
NI treat those steps as mutations. One creates a object/URL, one uploads to it (probably using fetch directly), final mutation confirms the upload is ready for the backend
NBut it doesn’t matter hugely if you want to use the vanilla client instead, you’ll have to maintain whatever loading state yourself anyway with that middle fetch call involved
NCould pop it all inside a standard react-query useMutation to abstract it away
NBest pointer is to check the docs 
NIt's very similar to the react client though
NOh you don't need to have two there! That's just for the react one
Nvanilla client is just a Promise based thing, just create the client and then start using it