Skip to main content
Solved

Additional Card Information from Webhooks

  • May 17, 2022
  • 1 reply
  • 214 views

michael-cope

Hello Pipefy team. I have been experimenting with webhooks to better automate our processes. I noticed that when I get a response, that the only information I receive is the card ID, and a pipe ID. Because of this, I have to execute an additional query to find the phase ID, and other information. Is it possible to have the webhook response include that kind of thing? It would be great if I could include all of the same information in the webhook response, that I could get in a query.

Best answer by Marcos Carvalho

Hey @michael-cope, how are you? I’m Marcos from Pipefy Engineering Team. 
 

In fact that’s how Pipefy Webhooks were designed, with a GraphQL flavor in mind and avoiding over or under fetching, since the card can contain many information like card values, information about the phases, emails sent and much more. 

Since each integration is unique, sending all the card information in the webhook payload could be too  much. 
With the card ID and this extra request, you can request just the information you want. 

But we want to hear you, what extra fields would you need in the webhook payload? 

Best regards, 

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

1 reply

Marcos Carvalho
Pipefy Staff
Forum|alt.badge.img+6

Hey @michael-cope, how are you? I’m Marcos from Pipefy Engineering Team. 
 

In fact that’s how Pipefy Webhooks were designed, with a GraphQL flavor in mind and avoiding over or under fetching, since the card can contain many information like card values, information about the phases, emails sent and much more. 

Since each integration is unique, sending all the card information in the webhook payload could be too  much. 
With the card ID and this extra request, you can request just the information you want. 

But we want to hear you, what extra fields would you need in the webhook payload? 

Best regards, 


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