Knowledge Base

Knowledge Base/Features/Automations/Automations: send web...

Topics

Automations: send webhook requests

Yssel Salas

Last updated: November 9, 2026

Note: The webhook action in Automations is only available on Growth and higher plans. Regular webhooks (outside of Automations) are available on all plans.

The webhook action in automations lets you automatically send information from Pipedrive to an external app whenever your automation’s trigger conditions are met.

For example, you could:

Automatically notify your team on Slack when a deal is marked as won
Create a new record on your invoicing tool when a deal reaches a specific stage
Send lead details to a custom database as soon as new lead comes in

Create a webhook

Note: Only users with global admin permissions can create automated webhooks, up to 200 per user. Learn more about global user management.

Before you use the webhook action in your automation, you first need to create an automated webhook.

Open the account menu and go to Tools and apps > Webhooks. Click “+ Webhooks”, then select “Automated webhook”.

Give your webhook a clear name. You’ll need to recognize it by name later, when you add it to an automation.

Next, add the endpoint URL and any authentication credentials the endpoint requires.

Note: The endpoint URL must end with a “/”, “&”, “?” or “=” character. This lets your automation add a path to the base domain without creating an invalid URL. You can choose the path later, when you add the webhook action to an automation.

Add a webhook to automations

Note: See who can create and manage automations and manage who can trigger automations for a full overview of permissions needed for working with automations.

Once you’ve created a webhook, go to automations and start building an automation. When you reach the action step, select the webhook action.

Under mandatory fields, fill in webhook, method and body.

Choose your webhook and method

First, select the webhook you created earlier from the webhook field.

Then, choose a method:

Method	What it does
`POST`	Creates a resource
`PUT`	Replaces a resource with another one
`DELETE`	Deletes a resource

Build the webhook body

In the webhook body, you can choose to set it up by “Key-value” or “Raw”.

The key-value builder lets you add entries one at a time. Click the field button to insert a Pipedrive field into any entry.

The raw builder gives you full control. You can write your own JSON-valid body if you need a payload the key-value builder can’t produce.

Use the field button to insert placeholders for the deal’s real data. Automations replaces them with the real values when it sends the webhook request.

Add a webhook path

The webhook path is optional. If you need one, click “+ Add fields” to add it.

Automations appends this path to the base domain you set when you created the webhook.

Review webhook execution history

For an overall view of automation health across your account, check the automation overview dashboard.

To review a specific webhook request, go to Automations > History and open the execution you want to check. It shows the final body and path sent with the request.

If a webhook stops working, or is missing authentication or permissions, the execution fails.

For example, if your endpoint keeps returning errors, you might see “Maximum retry limit reached”.

Note: Learn more about automation limits in Pipedrive. Any limit for the outgoing webhook request delivery comes from your endpoint’s own service.

Was this article helpful?

Yes