Ask the Community

Hi,This API for createFieldCondition says "Deprecation. Mutation will be removed in the nextupdate.https://api-docs.pipefy.com/reference/mutations/createFieldCondition/Are you adding replacement for this feature? or is there any other way to create fieldCondition?

I am deploying Pipefy in a company that has two branches (with the expectation of opening three more) and I would like all branches to share the same Pipes (to reduce the number of automations and create a global view of the process).My solution was to create a branch table, where I listed those responsible for each area. With the automations, I linked the responsible person to each card based on the informed branch.To facilitate the filter by branch, I created another branch field with the label type.What I couldn't solve:1) I wish that the users could not see the cards of the other branches (without them needing filters).2) The restricted view does not solve, as the user needs to see the branch cards, even if he is not marked as responsible.I would like to know how you have been doing in these cases.Greetings from Brazil.

Hello - is there a task / resource forecast that pipefy provides? - Looking to get a dashboard similar to https://www.forecast.app/integrations/harvest

I am interested in seeing examples (screenshots) of how best to enter instructional lists into Pipefy.  In situations where you need a PDF, checklists can’t be used .  The alternative is to use vertical radio buttons with one instruction per button. I would like to see examples of what users put in the field name versus what text is input in the option box.

What is the availability of the support team? It will depend on the plan that I have?

Dear Pipefy Team, I really love Pipefy - it lets us do amazing things that would be very difficult to do otherwise, and the features that you guys have put together are incredible.However, it seems like there is some kind of issue with availability/speed/reliability on a near-weekly basis. This makes it really hard for us to fully rely on it for real business purposes. The features are great, but reliability is critical. For example, the recent email changes caused lots of problems. Today, the system is down and randomly not accepting entries or timing out. So, please, Pipefy management - if you are listening - prioritize stability and reliability of the platform! Thanks in advance!  

Hello, everyone.Pipefy is the best option to organize your process and manage the papers of company.I am very happy to share my experience and to be part of a global team around the world.Do you need to plan your agenda? Use Pipefy.Do you want to improve your process of sales? Use Pipefy.This is my opinion. I am very proud to be an user of Pipefy. Have a nice week.

Hi,I am trying to make an API call to createCard referring to this link.The documentation here seems to be a bit tricky. What are the fields passed inside the "fields_attributes"? How do I get the IDs of the fields in my instance?

How long is gonna take the modeling & training process to initiate after we start up the service?

Instead of yearly subscription from the onset, can we start with month to month or a 3 – 6 month option? 

I'm trying to create card with this mutation:mutation { createCard(input: {pipe_id: <PIPE_ID>,phase_id: <PHASE_ID>,fields_attributes: [{ field_id: ""mobile_number"", field_value: ""+5511991026221"" },{ field_id: ""customer_name"", field_value: ""Caio Vitor Souza Santos"" },{ field_id: ""email"", field_value: ""caiovitor.santos@gmail.com"" },{ field_id: ""country"", field_value: ""Brazil"" },{ field_id: ""package"", field_value: ""bulk"" },{ field_id: ""payment_term"", field_value: ""L/C at Sight"" },{ field_id: ""delivery"", field_value: ""fob"" },{ field_id: ""price"", field_value: ""600.0"" },{ field_id: ""volume"", field_value: ""400.0"" },{ field_id: ""company_name"", field_value: ""Barley"" },{ field_id:

Hi,its possible to delete a member, or at least remove a member from a team using the API?I dind’t find a mutation for that

Hi there,I’m working on an Onboarding Process and would like cards to move to a “Done” phase after the date of their onboarding has passed. There is a field in our start form where card creators indicate what the Start Date is for the new person that’s being onboarded.Ideally, I’d like to set up an automation that would move the cards to “Done” automatically once the Start Date from the start form is reached.I found this post here in the community that seems similar to what I’m asking, but it relies on using the SLA settings on a phase. If I use the “When an alert is triggered” automation, it seems that only refers to SLA alerts. I don’t think using the SLA setting will work as a trigger for this automation I have in mind. Is there another type of alert I could configure or something else I could try?Perhaps using the “R

Hi, could you show me what is wrong? import requestsurl = "https://api.pipefy.com/graphql"payload = """{ "query": "{ pipe (id: 549212) {name}}"}"""headers = {'authorization': "Bearer xxxxxx",'content-type': "application/json"}response = requests.request("POST", url, data=payload, headers=headers)print(response.text)When I executed this, give me the error:{"errors":[{"message":"no \"data\" or \"errors\" in response from origin"}]}Thank you

About the implementation hours, those hours are one shot, or yearly ? What is the cost for additional professional hows for modeling?

 Hello., I have a question. For the two factor authentication what do you use? or how implement this ?

Is it possible - through the API - to query member IDs all at once?If so, how can I do it, I searched the documentation and didn't find it. thanks in advance 

Good morning. How many times pipefy reports an event. For example, if there is an error in the community does pipefy warn you again? Thanks

Hi,  Can't figure what is wrong with my code in Python, I'm trying to get all the pipes from a company, my code is the following and the response I getting is 404, I already tried different things like make the "query" in a single row using "\" to escape the caracteres: import requests url = "https://api.pipefy.com/graphql" headers = { 'authorization': "Bearer company_token", 'content-type': "application/json" } query = """ { "query": "{organization(id: 16094){pipes{id}}}" } """ response = requests.get(url, data=query, headers=headers) print(response.text)

  Hello! Is Pipefy planning on integrating the ability to use our own form backgrounds?Currently, we have to go through Unsplash and they have their own set of requirements just to upload an image. I think this would really bring the forms to life and allow the companies to showcase their brandings and designs with their own backgrounds. Thank you for your time!   

I am having an issue in which whenever I try to run and advanced search on allCards, I get an execution error. here is the query I am trying to run (pipeId and value have been changed) {allCards(pipeId: 1111111,filter:{field: "taskid",operator: equal,value: "1111"}){edges{

When a new opportunity becomes available (a customer calls), I’d like to check to see if that person is already a customer.  How could I do that?

I'd like to retrieve all fields that correspond to a new card from a specific column in my pipe. It's possible?

On my cards, the user selects one of two options on a radio button, and enters a due date. On the calendar, the items display based on due date, but I’d like to see the items displayed differently (different color?) based on the radio button selected. Possible? 

import requestsimport jsonurl = "https://api.pipefy.com/graphql"# Static query works#query = """mutation{createCard( input: { pipe_id: 301421136 fields_attributes:[ {field_id: \"company_name\", field_value: \"Static Test Company\"} ] } ){ card { id title } } }"""# Variable query to testvariables = { "company_name": "My Test Company"}query = """mutation($company_name: String){ createCard( input: { pipe_id: 301421136 fields_attributes: [{field_id: \"company_name\", field_value: $company_name} ] } ) { card { id title } } }"""headers = { "content-type": "application/json", "authorization": "Bearer token here"}# Static query work#response = requests.request("POST", url, json={"query": query}, headers=headers)response = requests.request("POST", url, json={"query": query, "variables": variables}, headers=headers)print(response.text)I