New: Automations webhook requests
Hey Pipedrivers 👋
We’re beginning to gradually release automated webhooks, expecting to reach all regions by the end of April 2024.
What does it do?
The webhook action in Automations allows you to connect Pipedrive with external tools and apps by sending information to specific endpoints. Unlike regular webhooks, you can use automation conditions and setup to define more precisely which parameters and events must happen for specific information to be sent out. You can also see the execution history for your webhooks that are set up this way.
This feature is available from the Advanced plan and above. For more details, check out our knowledge base article here.
Comments
-
This is exciting. Looking forward to it.
0 -
This is great news!!
0 -
We are thrilled to see Pipedrive advancing interoperability with other tools, allowing us to manage certain scenarios without the need for automation tools like Zapier or n8n in the future.
We've had the opportunity to test the new feature and are pleased with its initial functionalities. However, for it to truly serve as a full-fledged replacement, there are a couple of capabilities still missing. Specifically, the ability to analyze the response after sending a webhook so that the data can be used in subsequent workflow steps, and the functionality to include header data for authentication with web services. Additionally, incorporating a GET function to fetch data from other web services would be highly beneficial, especially for updating records in Pipedrive based on external data.
We are hopeful that continuous development of this feature will turn it into a robust tool for our processes. Keep up the great work!2 -
Hi @Martin Miersch thanks for the feedback! At the moment, that goes beyond what can be set up directly in workflow automations in-app, such as a built-in GET function.
But depending on the tool you’re looking to integrate with, you might be able to find a preexisting integration or use dedicated automation tools like Zapier or Make.0 -
Hi @wonders I have put in the request to our product team, it should be coming to you in the next release batch
0 -
Why is there a restriction for URLs? "URL must end with /, &, ?, or =" I want to use a Power Automate generated URL as my endpoint, it is set to be publicly available, but this error is restricting me. I have no control over the URL as it is generated when you use Microsoft's' Power Automate platform. Specifically, the "When an HTTP request is received" action.
1 -
@boneal I had this problem with a different tool. Use the separator that the API you're calling requires when specifying parameters. I needed a ? because the webhook ID is in the URL but it depends on the tool.
0 -
@Iain Ashley I was able to bypass the issue by adding a "&" at the end of the URL. This character is ignored by Power Automate. All other combinations resulted in no trigger of the Power Automate flow. It appears this issue only exists for Automated Webhooks, this issue does not occur, for the exact same Endpoint URL, within regular webhooks. But thank you!
0 -
It's disappointing that only administrators can benefit from the global automated webhook functionality.
Here's what I've explained to the support team :
All users in my account should be able to trigger an automation that includes a webhook action. For example, this action can help them enrich data from external providers. Please, delete confusion between the « create automated webhook » reserved for admin users and the availability to trigger the automation (using webhook) by all users. If everyone can trigger the automation, it shouldn’t be stopped for permission problems.3 -
Just like Alice said, it's disappointing. For now, it's quite useless. We also have to send data from Pipedrive after some event and conditions are met, such as creating an organization and filling custom fields. The webhook in automations seemed promising, as it looked like we could finally do this. However, if only admins can use it, it's pointless. Creating a normal webhook for creating or updating an organization is overkill because you can't specify any conditions, and it sends data every single time. 😑
2 -
My colleague Romain, Head of Growth, has created a temporary system to deliver the same results.
However, it shouldn't be so complicated to bypass this useless feature.
- Use the Trello native add-on to send data to a card.
2. Utilize the content of Trello cards to carry out the process and then update the information in Pipedrive.
Hope this will be helpful!
0 -
What?? Only admin can trigger automated webhooks? Why?????
1 -
@Manuel Oliveira Can we please get some more explanation on this limitation discussed above? This makes this feature functionally useless for our organization and we were relying on this to connect core data to our internal systems.
0 -
Hi, @boneal and @Randall Pena I checked this with the product team, and the reason is that automation webhook requests follow the existing permission structure: since regular webhooks are only available for admins, the automated ones are also only available for admins.
Changing permissions to allow for that type of action is not in the plans for the very near future. But please do share this feedback in the Product Feedback category. The more visible a type of request is, the more likely it is to be picked up for research and development.0 -
@Jakub Completely agree - fairly useless feature if only admins can trigger webhooks. Need to change the "Triggered by any user" language in the Automations when clearly that is not actually possible. I am using Power Automate as my endpoint so there is no reason why someone in Pipedrive cant trigger the automation webhook so that I can send an email to our entire organization. This was the primary feature that we needed to make Pipedrive work in our org.
0 -
this is great news and already a huge leap towards usable workflow automations. One can set to trigger workflow by anyone tho, just as any other workflow:
(the workflow on screenshot is triggered by anyone and makes a request to make, which then does a bunch of stuff on miro, google drive, sheets, youtrack and lexoffice, so all works)
0 -
@Nikolai Sokolov but unfortunately it doesn't work like you describe… Yes, the trigger will be triggered by any user but it will fall in case the user doesn't have access to webhooks.
0 -
@Jakub haha this is very convenient ) pipedrive team def needs to look into that - very misleading indeed. Lets flood the feature request thread!
0
