Skip to main content
Solved

Problem with GraphQl endpoint User

  • November 7, 2022
  • 3 replies
  • 169 views

rafa15
  • Known Participant
  • 14 replies

Hello, we are using this object (https://api-docs.pipefy.com/reference/objects/User/)  in you api but we are getting a user from pipefy's CSM team a#####@pipefy.com 

So we pay for this user? 

I believe that she appears in the response because she gives us some support on our pipefy organization. How can I identify that this user is from pipefy and not my org? 

 

Best answer by marcos.pedrosa

If you run the query below, you’ll be able to gather the user’s permission, name and email. If the email returns as @pipefy.com, it will be a non chargeable user. 

query{
  organization(id:xxxxxx)
  {
    members{
      role_name
      user{
        name
        id
        email
      }
    }
  }
}

 


The admin user will have full power to model the process if needed. If you are org admin, you can manage these users and even change their permission. 

View original
Did this topic help you find an answer to your question?
This topic has been closed for comments

3 replies

marcos.pedrosa
Pipefy Staff
Forum|alt.badge.img+2

Hello there, @rafa15!

@pipefy.com emails are non chargeable and it will not add any fee to your organization. 
This domain is used by Pipefy employees only and they are only granted access with users permission. 

Please let me know if you need additional information about this, alright ? ðŸ˜€


rafa15
  • Author
  • Known Participant
  • 14 replies
  • November 7, 2022

@marcos.pedrosa thanks! how can I distinguish, using your api, the pipefy employees? we couldn't find any prop to help us

 

Moreover, the user will always be admin? 


marcos.pedrosa
Pipefy Staff
Forum|alt.badge.img+2
  • Pipefy Staff
  • 41 replies
  • Answer
  • November 7, 2022

If you run the query below, you’ll be able to gather the user’s permission, name and email. If the email returns as @pipefy.com, it will be a non chargeable user. 

query{
  organization(id:xxxxxx)
  {
    members{
      role_name
      user{
        name
        id
        email
      }
    }
  }
}

 


The admin user will have full power to model the process if needed. If you are org admin, you can manage these users and even change their permission. 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings