---
title: "Example: Signal Design With Webhooks"
slug: "example-signal-design-with-webhooks"
updated: 2026-06-03T17:58:02Z
published: 2026-06-03T17:58:02Z
canonical: "documentation.decisions.com/example-signal-design-with-webhooks"
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Example: Signal Design With Webhooks

Follow an example how to use a Signal Start Event element in the Process Modeler using a Signal with a webhook.

### Overview

> [!NOTE]
> **Intended audience:** Process designers, Web designers, graphic designers, software developers, coding engineers
> 
> **Tags:** Signal Manager; Process Modeler, Signal Start Event; Screen design

The following example demonstrates signals: how a Process uses a Signal Start Event with a Webhook Signal collection. This example demonstrates that external thirdparties are available to configure in a Webhook Signal. For this example, the external thirdparty to use is [Docparser](https://docparser.com/integrations/webhooks/). Docparser send the signal and the payload request.

Follow these steps to use a Webhook Signal in a Process:

1. [Create a signal](/v1/docs/create-a-new-signal).
2. [Enable the webhook access](/v1/docs/edit-a-signal#configure-a-signals-webhook-access) for the created signal with the default values:

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/79057e4a-6d34-4a4b-84f9-57f2610f7e2b.png)

  - In the **Accepted Form Fields** without fields.
  - In the **Accepted Method**, the **POST** option selected.
  - In the **Authentication**, the None option selected.
  - In the **Restrict Access From,** without URLs.
3. In the **Webhook URL**, click **Copy to Clipboard** to copy the URL to use it in the external third-party app.
4. Click **Save** to save the signal webhook configuration.
5. Configure the Docparser account to use the webhook URL. This configuration depends on the third-party app and its version. For Docparser, it is configured in the **Integrations** section as follows:

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/eb4ef665-41c0-40f1-b9cf-335625559615.png)

  - In the **Name** setting, enter the webhook name.
  - In the **Payload format** setting, select the JSON format.
  - In the **Target URL** setting, copy the ProcessMaker Platform's **Webhook URL** .
  - In the **Include Fields** setting, select the fields that Docparser is going to send to ProcessMaker Platform.

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/e38fd342-a7aa-4d37-b9ef-367abff134f0.png)
6. [Create a process](/v1/docs/create-a-process) and model the process including a [Signal Start Event](/v1/docs/signal-start-event). In this example the Signal Start Event is **Webhook sent from DocParser**:

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/626c2707-c51f-436c-9ec8-ee4eb158e1e9.png)
7. Configure the Signal Start Event to broadcast the external Docparser signal as follows:

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/4e13a60d-eeaf-42de-9c78-45d510c64039.png)

  - In the **Name** setting, enter the Signal Start Event name, which is **Webhook sent from DocParser**.
  - In the Signal setting, select the signal created in step 1.
  - In the **Request Variable** setting, enter the variable name that store the payload data. For this example, it is **payload**.
8. Use the JSON data from the **payload** request variable in your Screens as follows:

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/23b20b92-a6ac-4f6d-ad54-df606fd91004.png)

The **Variable Name** setting of a control setting calls the Signal payload by calling the JSON object as **payload.bol**. In this example, **bol** is the object called.
9. Configure your Process elements and Screens as necessary.