Hi. No don’t do that.
I have to be honest and I kind of skimmed through your text before my last answer, sorry about that. I got the direction of the entire thing wrong and thought the trigger was a request from Pipedrive but I see that this is a local trigger and then a request to pipedrive to Cloudflare on YOUR end has nothing to do with this. Let’s think about this.
- Cloudflare seem to have banned your servers IP-address from reaching the API. They will give a 403 error to a banned ID,
What is wrong
Lets look at the 403 response you posted. I created a 403 response from the Pipedrive API and we see differences right away. The headers [report-to] is a give away that this is Cloudflare. Pipedrive also have content-type application/json not text/html plus lots of other differences. It is Cloudflare that blocked your server.
How can you test it.
Change the IP number of the server. Depending on your hosting you might need to ask them. It can happen that the hosts change the IP when rebooting the machines etc.. Perhaps they transferred you workload to another machine.
Try to access the Pipedrive API from the server. You should get a 403 error.
What to do.
If my theory is correct. Check that the server is not infected and change IP
Possible causes
Sometimes you share IP with other hosting customers, where one customer does something stupid and get the IP banned. It might be that the server is rebooted and changes to an IP that is already banned.
It might also be that your server have a “virus”, that might or might not be unrelated to your website. Check for outgoing traffic that should not be there.
Pipedrive 403.
For reference the Pipedrive response body looked like this when I tried to delete a person as a regular user:
{
"success": false,
"error": "You do not have permissions to do this.",
"error_info": "Please check developers.pipedrive.com for more information about Pipedrive API.",
"data": null,
"additional_data": null
}