hi @genietim
Are you trying to create a new custom app? Can you give more context? If you are planning to use the GraphQL API, I would recommend you to create a new token here https://app.pipefy.com/tokens
HI @amadeu-cavalcante, I am sorry to see your answer only now. Yes, I am trying to create a custom app (well, I already did actually). The problem I was/am struggling with is the users’ tokens. Yes, I know how to create the tokens and I can use the Pipefy GraphQL API with them. BUT: I do not want to ship the tokens to the user in the custom app. My current workaround is to have the token in the backend and use the backend as a proxy for the queries. But again, while this works for now, it is not ideal: this makes all queries be run by the one token I have, meaning only one user. Other users using the custom app do their mutations with my user. I could ask each and every user to go to https://app.pipefy.com/tokens and give me their token, but this would not be future-proof nor a good user experience. Especially knowing that there is a way without.
If I could get the users’ token (as the calendar custom app does, for example), this would remove the need for the proxy as well as solve the issue with the “only one” user making queries.
Or am I misunderstanding your suggestion?
@genietim Sorry for taking so long to reply to you.
I was searching if we could current support what you are asking. And, unfortunately, the `getAuthToken` method used by our calendar app was designed to internal usage only.
I'll keep you posted as soon as we have any solution for your problem. I'm really sorry.
@genietim did you get the answer you are looking for?
@Juliana Spinardi well, maybe not the one I had hoped for, but “internal usage only” is an answer, I just marked it as such, though I hope @amadeu-cavalcante will have the possiblitiy to come back some time with a more positive answer (:
Este seria um ótimo caminho, também a procura desta solução.
Acessar essa e outras funções eliminariam muito trabalho e custo aos nossos aplicativos personalizados, que é inclusive o único motivo que me faz pagar pelo pipefy hoje em dia.
This would be a great way, also looking for this solution.
Accessing this and other functions would take a lot of work and cost out of our custom apps, which is actually the only reason I pay for pipefy these days.
Hi @ascension-dig, how are you?
Thank you for this feedback!
It would be great if you can register your feedback here to our product team!