---
sourceDocument: Zurich Build workflows
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/build-workflows

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Create an external trigger

# Create a saved external trigger {#ariaid-title1}

* Release version: Zurich
* 
* Updated July 31, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read

Save a set of trigger definitions as a reusable trigger that responds to external events through webhooks. When an event occurs in the configured third-party application that meets the specified conditions, the trigger is
activated.

## About this task

Create a saved trigger that responds to events occurring in a supported third-party spoke that is already configured in Workflow Studio. When an event occurs, the third-party spoke sends the event payload to Workflow Studio.  
In the trigger definition, you specify:

* The event payload structure in JSON format
* The conditions that determine when the trigger starts
{#create-saved-external-trigger__ul_sbh_kxk_whc}Obtain the event payload JSON from the third-party spoke that you configure.

## Before you begin

Role required: trigger_designer, flow_designer, or admin

Subscription required: This step requires an Integration Hub subscription.  
Plugins required: Install the following Integration Hub plugins:

* ServiceNow Integration Hub External Trigger \[com.glide.ih.external_trigger\]: To use out of the box external triggers.

* External Trigger Builder \[sn_ext_trg_bldr\]: To create a saved external trigger.

{#create-saved-external-trigger__ul_ybr_cpm_xdc}  
Note:  
For information about what is included with different Integration Hub subscriptions, see [Legal schedules - Integration Hub overview](https://www.servicenow.com/content/dam/servicenow-assets/public/en-us/doc-type/legal/snc-addendum-integrationhub.pdf)  
Create the required event sources in the Event source builder, or use the existing event sources from these spokes.

* Jira Spoke
* GitHub Spoke
* Docusign eSignature Spoke
* Microsoft Azure DevOps Boards Spoke

{#create-saved-external-trigger__ul_phb_q14_xdc}For more information about creating an event source, see [Create an external event source](https://www.servicenow.com/docs/RVtv5IQLZCbGd4OsM7pa4A#create-an-external-event-source "Create an external event source for a spoke or scoped application that listens to events occurring in an application or system outside ServiceNow. Based on the external event source, you can create an external trigger definition that receives communication from the external event source and starts a flow on your ServiceNow instance.").  
Important:  
Keep the event payload JSON of the third-party application handy. Refer to the third-party webhook documentation to identify where you can copy the event payload JSON. For example, see the following link for Jira event payloads: [Executing a webhook](https://developer.atlassian.com/server/jira/platform/webhooks/#executing-a-webhook).

## Procedure

1. Navigate to AllProcess AutomationWorkflow Studio.
2. From the Workflow Studio home page, select NewTrigger.
3. On the form, fill in the fields.  
   {#create-saved-external-trigger__table_rrl_y5k_5dc__entry__2}

   | Field | Description |
   |-|-|
   | Trigger name | Name to identify the trigger. |
   | Trigger type | The type of the trigger to start your flow. Under External, select Event (Webhook). |
   | Description | Description of the trigger. |
   | Application | Application scope to create the trigger. Workflow Studio displays the configured spokes that are supported. |
   | Event source | The third party system that will send the events to ServiceNow. |
   | Domain | Domain scope of the flow. For more information about domain separation, see [Domain separation explained](https://www.servicenow.com/docs/access?context=bp-what-is-domain-separation&version=zurich&pubname=zurich-platform-security&ft:locale=en-US). |
   [Table 1. New Trigger form]

   {#create-saved-external-trigger__table_rrl_y5k_5dc}
4. Select Show additional properties and fill in the fields.  
   {#create-saved-external-trigger__table_yfq_yxk_5dc__entry__2}

   | Field | Description |
   |-|-|
   | Accessible from | The trigger data is accessible from all application scopes. |
   | Category | The category where your trigger is displayed. |
   | Trigger annotation | Annotation for your trigger that the user can see before they select the trigger. |
   [Table 2. Additional properties form]

   {#create-saved-external-trigger__table_yfq_yxk_5dc}
5. Select Build trigger.  
   Workflow Studio displays the Trigger definition page. In the Event source preview area, you can view information about how the external trigger endpoint is configured. Configurations you make to the trigger are auto-saved.
6. Under Parser, fill in the fields.  
   {#create-saved-external-trigger__table_opx_51l_5dc__entry__2}

   | Field | Description |
   |-|-|
   | Trigger output name | Label to identify the trigger output. |
   | Request headers | Optional field to specify one or more headers to be included in the inbound request. |
   | Query parameters | Optional field to specify one or more parameters to be included in the inbound request. |
   [Table 3. Parser form]

   {#create-saved-external-trigger__table_opx_51l_5dc}
7. Under Body, in JSON editor, paste the payload JSON from the third-party application.  
   Refer to the third-party webhook documentation to learn about from where you can copy the payload JSON.
8. Select Visualize objects.  
   The editor displays the objects that are in the payload JSON. You can reorder or remove the objects. The objects are available as data pills to use in conditions.
9. In Condition editor, drag and drop the data pills to create a condition set.  
   Use and or or operators to add more conditions to the condition set.
10. Select +New condition set to add additional condition sets, as required.
11. Select Publish to make the trigger available for use.  
    Note:  
    Once the trigger is published, you can edit only the output Label fields.
* **[Managing external event sources](https://www.servicenow.com/docs/RVtv5IQLZCbGd4OsM7pa4A#manage-external-event-sources)**   
  Create and manage external event sources for a spoke or a scoped application that listen to events occurring in an application outside ServiceNow. Then, you can create external trigger definitions and associate them with the external event sources. When the event that you specify in the external trigger definition occurs, it starts one or more flows on your ServiceNow instance.

*[\>]: and then