# Marketplace Workflow Triggers

> Marketplace Workflow Triggers are the customizable workflow triggers managed in Marketplace . You will be able to create custom triggers to push data…

- Source: https://docs.ghlcustomercare.com/docs/app-marketplace/workflow-triggers-and-actions/marketplace-workflow-triggers
- Section: App marketplace / Workflow Triggers & Actions
- Reading time: 6 min
- Images: 22, each explained below
- Modified on Fri, 16 Aug, 2024 at 2:19 AM

---
Marketplace Workflow Triggers are the customizable workflow triggers managed in Marketplace. You will be able to create custom triggers to push data from your application/API to a workflow.

Sign up/ Sign in to Marketplace to manage Marketplace Workflow Triggers.  
Marketplace Workflow Triggers are part of LC Premium Triggers & Actions and are chargeable per execution.  
How to enable and rebill LC Premium Triggers & Actions for Workflows?  
You should enable Workflow LC Premium Triggers & Actions for the sub-account to access the Triggers created in the Marketplace App.  
The marketplace workflow triggers created in an APP will be listed in the workflow triggers only if the sub-account has the APP installed/integrated from the Marketplace.  

**TABLE OF CONTENTS**

-   [Prerequisites](#prerequisites)
-   [Create Trigger](#create-trigger)
-   [](#trigger-information)[Trigger Information](#trigger-information)
-   [](#trigger-configuration)[Trigger Configuration](#trigger-configuration)[](#trigger-data)
-   [Trigger Data](#trigger-data)[](#manage-filters)
-   [Manage Filters](#manage-filters)
-   [Manage Custom Variables](#manage-custom-variables)
-   [Subscription URL](#subscription-url)
-   [Submit for Review](#submit-for-review)
-   [Create New Version](#create-new-version)
-   [Delete Trigger](#delete-trigger)
-   [Can workflow execute without contact?](#can-workflow-execute-without-contact)

## **Prerequisites**

**_Note : workflows.readyonly scope should be turned on to enable actions and triggers._**

![Prerequisites (image 1 of 22)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155031136715/original/0aSds7RCt1quSlQ08B6V0bOuZWIUk56ZGw.png)

**Prerequisites (image 1 of 22)**

This screenshot appears in the "Prerequisites" section of "Marketplace Workflow Triggers". The text alongside this image reads: Note: workflows.readyonly scope should be turned on to enable actions and triggers. Immediately after, the guide continues: A unique identifier for this trigger, used to reference the trigger inside the workflow. This value cannot be changed later. Example: {{mycustomtrigger.data.name}}.
- What this covers: Note: workflows.readyonly scope should be turned on to enable actions and triggers.
- Next: A unique identifier for this trigger, used to reference the trigger inside the workflow. This value cannot be changed later. Example: {{mycustomtrigger.data.name}}

## **Create Trigger**

![Create Trigger (image 2 of 22)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155008571402/original/-akI1I0dRCxxnUB-vS_AXBRwM2lDmLY9zQ.png)

**Create Trigger (image 2 of 22)**

This screenshot appears in the "Create Trigger" section of "Marketplace Workflow Triggers". The text alongside this image reads: Note: workflows.readyonly scope should be turned on to enable actions and triggers. Immediately after, the guide continues: A unique identifier for this trigger, used to reference the trigger inside the workflow. This value cannot be changed later. Example: {{mycustomtrigger.data.name}}.
- What this covers: Note: workflows.readyonly scope should be turned on to enable actions and triggers.
- Next: A unique identifier for this trigger, used to reference the trigger inside the workflow. This value cannot be changed later. Example: {{mycustomtrigger.data.name}}

### **Name**

Enter Trigger Name

**Key**

A unique identifier for this trigger, used to reference the trigger inside the workflow. This value cannot be changed later. Example: {{mycustomtrigger.data.name}}

# **Trigger Information**

Add trigger details

![Trigger Information (image 3 of 22)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155008571484/original/upXNQ8ldHATTzVMFsJA6SDjKyyyXW8Md0A.png)

**Trigger Information (image 3 of 22)**

This screenshot appears in the "Trigger Information" section of "Marketplace Workflow Triggers". The text alongside this image reads: A unique identifier for this trigger, used to reference the trigger inside the workflow. This value cannot be changed later. Example: {{mycustomtrigger.data.name}}. Immediately after, the guide continues: Choose an Icon for this Trigger. Shown in workflow for this trigger.
- What this covers: A unique identifier for this trigger, used to reference the trigger inside the workflow. This value cannot be changed later. Example: {{mycustomtrigger.data.name}}
- Next: Choose an Icon for this Trigger. Shown in workflow for this trigger.

### **Icon**

Choose an Icon for this Trigger. Shown in workflow for this trigger.

### **Name**

Custom Trigger Name

### **Key**

A unique identifier for this trigger, used to reference the trigger inside the workflow, Ex: {{trigger\_a.custom\_variable}}. This value cannot be changed later.

### **Short description**

A short description explaining what your trigger does to help users understand. Shown in workflow as sub-title for this trigger.

### **Summary**

A detailed information on what your trigger does to help users understand why they should use this trigger.

# **Trigger Configuration**

## **Trigger Data**

Add sample trigger payload data to configure filters and custom variables.

**Add sample trigger payload data  
**

Enter a valid sample payload JSON structure that will be sent to the trigger.

![Trigger Data (image 4 of 22)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155008572394/original/dDTnUzyorTuAP9fwktAjyt8XWSZoNy0ysQ.png)

**Trigger Data (image 4 of 22)**

This screenshot appears in the "Trigger Data" section of "Marketplace Workflow Triggers". The text alongside this image reads: Enter a valid sample payload JSON structure that will be sent to the trigger. Immediately after, the guide continues: Add filters using sample trigger data, for users to use in workflows trigger configuration.
- What to fill in: Enter a valid sample payload JSON structure that will be sent to the trigger.
- Controls: Add sample trigger payload data
- Next: Add filters using sample trigger data, for users to use in workflows trigger configuration.

## **Manage Filters**

Add filters using sample trigger data, for users to use in workflows trigger configuration.

![Manage Filters (image 5 of 22)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155008573989/original/dUCSEOtTj74A2fotCwqyRB5157kJjHfxXA.png)

**Manage Filters (image 5 of 22)**

This screenshot appears in the "Manage Filters" section of "Marketplace Workflow Triggers". The text alongside this image reads: Add filters using sample trigger data, for users to use in workflows trigger configuration. Immediately after, the guide continues: Select one of the following field types.
- What this covers: Add filters using sample trigger data, for users to use in workflows trigger configuration.
- Next: Select one of the following field types:

### **Create New Filter**

![Create New Filter (image 6 of 22)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155008575005/original/Eno_UsYIGBv7NPyT-TDujscxHAjDgMwM8w.png)

**Create New Filter (image 6 of 22)**

This screenshot appears in the "Create New Filter" section of "Marketplace Workflow Triggers". The text alongside this image reads: Add filters using sample trigger data, for users to use in workflows trigger configuration. This part of the guide covers 3 fields, listed below. Immediately after, the guide continues: Select one of the following field types.
- What this covers: Add filters using sample trigger data, for users to use in workflows trigger configuration.
- Fields: String, Multiple Select, Dynamic
- Controls: Name, Type, Required, Reference, Alters Dynamic Filter
- Next: Select one of the following field types:

Full procedure:

1. String
2. Select
3. Multiple Select
4. Dynamic

**Name**

Enter Filter Name

**Type**

Select one of the following field types:

-   String
-   Select
-   Multiple Select
-   Dynamic

**Required**

Enable if this is a required filter in workflow.

**Reference**

Select reference key from the sample Trigger Data. The value of this field will be bind to the provided key. Example: trigger\_a\_name

**Alters Dynamic Filter**

If enabled, any changes made to this filter value will trigger/ re-trigger loading the dynamic filters to the workflow trigger configuration UI.

### **Type: Select / Multi Select  
**

![Type: Select / Multi Select (image 7 of 22)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155008575097/original/esi5jPJrs8bzkVEwcMvNP2P6JGgF_ZMHvg.png)

**Type: Select / Multi Select (image 7 of 22)**

This screenshot appears in the "Type: Select / Multi Select" section of "Marketplace Workflow Triggers". The text alongside this image reads: If enabled, any changes made to this filter value will trigger/ re-trigger loading the dynamic filters to the workflow trigger configuration UI. This part of the guide covers 3 fields, listed below. Immediately after, the guide continues: Option Type is applicable only for Select and Multi Select field types.
- What this covers: If enabled, any changes made to this filter value will trigger/ re-trigger loading the dynamic filters to the workflow trigger configuration UI.
- Fields: Constants, Internal Reference, External API
- Next: Option Type is applicable only for Select and Multi Select field types.

Full procedure:

1. Constants
2. Internal Reference
3. External API

Option Type is applicable only for Select and Multi Select field types.

Select one of the following option types:

-   Constants
-   Internal Reference
-   External API

#### **Constants**

Load options by adding custom Label-Value constants

![Constants (image 8 of 22)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155005617938/original/xkySDB0XDrua62JzPisbo1TNQH59sEZSaw.png)

**Constants (image 8 of 22)**

This screenshot appears in the "Constants" section of "Marketplace Workflow Triggers". The text alongside this image reads: Load options by adding custom Label-Value constants. Immediately after, the guide continues: Load options from GHL Customer Care Internal Modules. Select one of the GHL Customer Care Modules to load options list.
- What this covers: Load options by adding custom Label-Value constants
- Next: Load options from GHL Customer Care Internal Modules. Select one of the GHL Customer Care Modules to load options list.

#### **Internal Reference**

Load options from GHL Customer Care Internal Modules. Select one of the GHL Customer Care Modules to load options list.

![Internal Reference (image 9 of 22)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155005617998/original/du8lZRMai5wENrSducJPjhqgFASlOZ_P6Q.png)

**Internal Reference (image 9 of 22)**

This screenshot appears in the "Internal Reference" section of "Marketplace Workflow Triggers". The text alongside this image reads: Load options from GHL Customer Care Internal Modules. Select one of the GHL Customer Care Modules to load options list. Immediately after, the guide continues: Supported GHL Customer Care Modules.
- What to choose: Load options from GHL Customer Care Internal Modules. Select one of the GHL Customer Care Modules to load options list.
- Next: Supported GHL Customer Care Modules

**Supported GHL Customer Care Modules**

![Internal Reference (image 10 of 22)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155005670538/original/8uQtBkMLWLhm6jcDxdX-gzjR07BQ_GPtXw.png)

**Internal Reference (image 10 of 22)**

This screenshot appears in the "Internal Reference" section of "Marketplace Workflow Triggers". The text alongside this image reads: Supported GHL Customer Care Modules. For context, this section explains: Load options from GHL Customer Care Internal Modules. Select one of the GHL Customer Care Modules to load options list. Immediately after, the guide continues: Load option from external API endpoint.
- What this covers: Supported GHL Customer Care Modules
- Next: Load option from external API endpoint

#### **External API**

Load option from external API endpoint

![External API (image 11 of 22)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155005618042/original/2om_uuB9g_V8MhG1MOLUrPPMIiq2kLggTA.png)

**External API (image 11 of 22)**

This screenshot appears in the "External API" section of "Marketplace Workflow Triggers". The text alongside this image reads: Load option from external API endpoint. For context, this section explains: Provide a URL to support GET method and send a valid response as per the sample response structure shared below. Immediately after, the guide continues: Provide a URL to support GET method and send a valid response as per the sample response structure shared below.
- What this covers: Load option from external API endpoint
- Controls: URL (GET), Headers, Sample Response Data
- Next: Provide a URL to support GET method and send a valid response as per the sample response structure shared below.

**URL (GET)**

Provide a URL to support GET method and send a valid response as per the sample response structure shared below.

**Headers**

Add headers as per your requirement

**Sample Response Data**

{  
   "options": \[  
      {  
         "label": "Afghanistan",  
         "value": "AF"  
      },  
      {  
         "label": "Åland Islands",  
         "value": "AX"  
      },  
      {  
         "label": "Albania",  
         "value": "AL"  
      },  
      {  
         "label": "Algeria",  
         "value": "DZ"  
      },  
      {  
         "label": "American Samoa",  
         "value": "AS"  
      }  
   \]  
}

### **Type: Dynamic**

Dynamic filters are used to build custom filters from an API call. The API call should return the below response structure to construct the filters in the Workflow trigger configuration form UI. Only one Dynamic type can be created per trigger.

![Type: Dynamic (image 12 of 22)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155008575252/original/ifNAt13wYheupSXn2LhgyT0zOp4wql5YtQ.png)

**Type: Dynamic (image 12 of 22)**

This screenshot appears in the "Type: Dynamic" section of "Marketplace Workflow Triggers". The text alongside this image reads: Dynamic filters are used to build custom filters from an API call. The API call should return the below response structure to construct the filters in the Workflow trigger configuration form UI. Only one Dynamic type can be created per trigger. Immediately after, the guide continues: Enter your API endpoint URL. When executed data is sent to this API endpoint via POST method in the below mentioned payload format and a valid response is expected as per the sample response structure shared below.
- What to fill in: Dynamic filters are used to build custom filters from an API call. The API call should return the below response structure to construct the filters in the Workflow trigger configuration form UI. Only one Dynamic type can be created per trigger.
- Controls: URL (POST), Headers, Sample structure for each Filter Types
- Next: Enter your API endpoint URL. When executed data is sent to this API endpoint via POST method in the below mentioned payload format and a valid response is expected as per the sample response structure shared below.

**URL (POST)**

Enter your API endpoint URL. When executed data is sent to this API endpoint via POST method in the below mentioned payload format and a valid response is expected as per the sample response structure shared below.

**Headers**

Add headers as per your requirement

**Sample Payload:**The form data is sent as payload to the dynamic field API

{  
   "data": {  
        "name": "John Doe",  
        "age": "29",  
        "gender": "male",  
        "hobbies": \["sports", "music"\],  
        "address": "My Address",  
        "country": "US",  
        "profileType": "public",  
   },  
   "extras": {  
        "locationId": "xyz",  
        "contactId": "abc",  
        "workflowId": "def"  
   },  
   "meta": {  
        "key": "custom\_trigger\_key",  
        "version": "1.0",  
   }  
}

**Sample Response Structure:** 

{  
  "filters": \[  
    {  
      "field": "name",  
      "title": "Name",  
      "fieldType": "string",  
      "required": true  
    },  
    {  
      "field": "gender",  
      "title": "Gender",  
      "fieldType": "select",  
      "required": true,  
      "options": \[  
        {  
          "label": "Male",  
          "value": "male"  
        },  
        {  
          "label": "Female",  
          "value": "female"  
        }  
      \]  
    }  
  \]  
}

**Sample structure for each Filter Types**

String

{  
   "field": "name",  
   "title": "Name",  
   "fieldType": "string",  
   "required": true  
}

Select

{  
   "field": "gender",  
   "title": "Gender",  
   "fieldType": "select",  
   "required": true,  
   "options": \[  
      {  
         "label": "Male",  
         "value": "male"  
      },  
      {  
         "label": "Female",  
         "value": "female"  
      }  
   \]  
}

Multiple Select

{  
   "field": "hobbies",  
   "title": "Hobbies",  
   "fieldType": "multiselect",  
   "required": true,  
   "options": \[  
      {  
         "label": "Sport",  
         "value": "sport"  
      },  
      {  
         "label": "Music",  
         "value": "music"  
      }  
   \]  
}

## **Manage Custom Variables**

Add Custom variables using trigger data, for users to use in workflows.

## **

![Manage Custom Variables (image 13 of 22)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155008572016/original/JkQMjhsCodCIJQU-BA-KjP9rH3aEn7fZYA.png)

**Manage Custom Variables (image 13 of 22)**

This screenshot appears in the "Manage Custom Variables" section of "Marketplace Workflow Triggers". The text alongside this image reads: Add Custom variables using trigger data, for users to use in workflows. Immediately after, the guide continues: Select a reference key from the sample trigger data.
- What this covers: Add Custom variables using trigger data, for users to use in workflows.
- Next: Select a reference key from the sample trigger data.

**

### **Add Custom Variable**

![Add Custom Variable (image 14 of 22)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155008572039/original/JQry9o7DFN62Ce_h2X0zvVE1zShpmMNqKg.png)

**Add Custom Variable (image 14 of 22)**

This screenshot appears in the "Add Custom Variable" section of "Marketplace Workflow Triggers". The text alongside this image reads: Add Custom variables using trigger data, for users to use in workflows. Immediately after, the guide continues: Select a reference key from the sample trigger data.
- What this covers: Add Custom variables using trigger data, for users to use in workflows.
- Controls: Name, Reference
- Next: Select a reference key from the sample trigger data.

**Name**

Enter label name

**Reference**

Select a reference key from the sample trigger data.

## **Subscription URL**

Collect trigger configuration details through API endpoint.

![Subscription URL (image 15 of 22)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155008572516/original/NxuZK11tEgoiGhlnW0FUCrPpaQu5iM88FA.png)

**Subscription URL (image 15 of 22)**

This screenshot appears in the "Subscription URL" section of "Marketplace Workflow Triggers". The text alongside this image reads: Collect trigger configuration details through API endpoint. Immediately after, the guide continues: Enter your API endpoint URL. When a trigger is configured (CREATED/UPDATED/DELETED) in workflow the trigger configuration data is sent to this API endpoint via POST method in the below mentioned payload format.
- What this covers: Collect trigger configuration details through API endpoint.
- Controls: URL (POST), Headers, Trigger "CREATED" in workflow, Trigger "UPDATED" in workflow
- Next: Enter your API endpoint URL. When a trigger is configured (CREATED/UPDATED/DELETED) in workflow the trigger configuration data is sent to this API endpoint via POST method in the below mentioned payload format.

**URL (POST)  
**

Enter your API endpoint URL. When a trigger is configured (CREATED/UPDATED/DELETED) in workflow the trigger configuration data is sent to this API endpoint via POST method in the below mentioned payload format.

**Headers**

Add required header data that has to be included while sending data to the API endpoint

**Payload format:**  
**Trigger "CREATED" in workflow  
**

{  
   "triggerData": {  
      "id": "def",  
      "key": "trigger\_a",  
      "filters": \[\],  
      "eventType": "CREATED",  
      "targetUrl": "https://services.leadconnectorhq.com/workflows-marketplace/triggers/execute/abc/def"  
   },  
   "meta": {  
      "key": "trigger\_a",  
      "version": "2.4"  
   },  
   "extras": {  
      "locationId": "ghj",  
      "workflowId": "qwe",  
      "companyId": "asd"  
   }  
}

**Trigger "UPDATED" in workflow**

{  
   "triggerData": {  
      "id": "def",  
      "key": "trigger\_a",  
      "filters": \[  
         {  
            "field": "country",  
            "id": "country",  
            "operator": "==",  
            "title": "Country",  
            "type": "select",  
            "value": "USA"  
         }  
      \],  
      "eventType": "UPDATED",  
      "targetUrl": "https://services.leadconnectorhq.com/workflows-marketplace/triggers/execute/abc/def"  
   },  
   "meta": {  
      "key": "trigger\_a",  
      "version": "2.4"  
   },  
   "extras": {  
      "locationId": "ghj",  
      "workflowId": "qwe",  
      "companyId": "asd"  
   }  
}

**Trigger "UPDATED" in workflow**

{  
   "triggerData": {  
      "id": "def",  
      "key": "trigger\_a",  
      "filters": \[  
         {  
            "field": "country",  
            "id": "country",  
            "operator": "==",  
            "title": "Country",  
            "type": "select",  
            "value": "USA"  
         }  
      \],  
      "eventType": "DELETED",  
      "targetUrl": "https://services.leadconnectorhq.com/workflows-marketplace/triggers/execute/abc/def"  
   },  
   "meta": {  
      "key": "trigger\_a",  
      "version": "2.4"  
   },  
   "extras": {  
      "locationId": "ghj",  
      "workflowId": "qwe",  
      "companyId": "asd"  
   }  
}

## **Submit for Review**

The trigger version will be in draft state by default. After updating the trigger information and configuration the trigger version should be submitted for review.

![Submit for Review (image 16 of 22)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155005621439/original/5UVWUz25eAcVTFtVlVtxEh3Fkg15t4zXDg.png)

**Submit for Review (image 16 of 22)**

This screenshot appears in the "Submit for Review" section of "Marketplace Workflow Triggers". The text alongside this image reads: The trigger version will be in draft state by default. After updating the trigger information and configuration the trigger version should be submitted for review. Immediately after, the guide continues: Click on Submit for review and add required changelog information for the submitted version.
- What this covers: The trigger version will be in draft state by default. After updating the trigger information and configuration the trigger version should be submitted for review.
- Controls: Submit for review, changelog
- Next: Click on Submit for review and add required changelog information for the submitted version.

Click on **Submit for review** and add required **changelog** information for the submitted version.

![Submit for Review (image 17 of 22)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155008572191/original/IGXs2a9XcQ-ybuxHr4VjcY8_JSnDq-VNOg.png)

**Submit for Review (image 17 of 22)**

This screenshot appears in the "Submit for Review" section of "Marketplace Workflow Triggers". The text alongside this image reads: Click on Submit for review and add required changelog information for the submitted version. Immediately after, the guide continues: Once approved the version submitted for review will be published live to all Sub-accounts.
- How to confirm: Click on Submit for review and add required changelog information for the submitted version.
- Controls: Submit for review, changelog
- Next: Once approved the version submitted for review will be published live to all Sub-accounts.

Once approved the version submitted for review will be published live to all Sub-accounts.

![Submit for Review (image 18 of 22)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155005621452/original/YeMGRy21eS8S8bI8rexthcKA8R4INYc2zw.png)

**Submit for Review (image 18 of 22)**

This screenshot appears in the "Submit for Review" section of "Marketplace Workflow Triggers". The text alongside this image reads: Once approved the version submitted for review will be published live to all Sub-accounts. Immediately after, the guide continues: Click on + New Version to create a new version for the trigger.
- What this covers: Once approved the version submitted for review will be published live to all Sub-accounts.
- Controls: Submit for review, changelog
- Next: Click on + New Version to create a new version for the trigger

## **Create New Version**

Click on  **\+ New Version** to create a new version for the trigger

![Create New Version (image 19 of 22)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155005621457/original/bHLDsksmL1K7qgmv7KoFYS6af3iMg8f0vQ.png)

**Create New Version (image 19 of 22)**

This screenshot appears in the "Create New Version" section of "Marketplace Workflow Triggers". The text alongside this image reads: Click on + New Version to create a new version for the trigger. Immediately after, the guide continues: On clicking + New Version It will create a new draft version with all the previously published data prefilled.
- What to click: Click on + New Version to create a new version for the trigger
- Controls: + New Version
- Next: On clicking + New Version It will create a new draft version with all the previously published data prefilled.

On clicking **\+ New Version** It will create a new draft version with all the previously published data prefilled.

![Create New Version (image 20 of 22)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155005622063/original/yLpMG6PiUYcVdUTi1zkBE6udOqOscWghbA.png)

**Create New Version (image 20 of 22)**

This screenshot appears in the "Create New Version" section of "Marketplace Workflow Triggers". The text alongside this image reads: On clicking + New Version It will create a new draft version with all the previously published data prefilled. Immediately after, the guide continues: Once a Trigger is deleted, it will be deleted permanently and cannot be restored. The deleted trigger will be removed from Marketplace App and Workflow Trigger list. If a deleted trigger is part of any workflow the trigger execution will….
- What this covers: On clicking + New Version It will create a new draft version with all the previously published data prefilled.
- Controls: + New Version
- Next: Once a Trigger is deleted, it will be deleted permanently and cannot be restored. The deleted trigger will be removed from Marketplace App and Workflow Trigger list. If a deleted trigger is part of any workflow the trigger execution will be skipped.

## **Delete Trigger**

Once a Trigger is deleted, it will be deleted permanently and cannot be restored. The deleted trigger will be removed from Marketplace App and Workflow Trigger list. If a deleted trigger is part of any workflow the trigger execution will be skipped.

![Delete Trigger (image 21 of 22)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155014522319/original/iILsc-HqjeJcvaYLyzPS1DLyWTp-E8ls2w.png)

**Delete Trigger (image 21 of 22)**

This screenshot appears in the "Delete Trigger" section of "Marketplace Workflow Triggers". The text alongside this image reads: Once a Trigger is deleted, it will be deleted permanently and cannot be restored. The deleted trigger will be removed from Marketplace App and Workflow Trigger list. If a deleted trigger is part of any workflow the trigger execution will be skipped. Immediately after, the guide continues: Enter trigger name to confirm delete.
- What this covers: Once a Trigger is deleted, it will be deleted permanently and cannot be restored. The deleted trigger will be removed from Marketplace App and Workflow Trigger list. If a deleted trigger is part of any workflow the trigger execution will be skipped.
- Controls: Enter trigger name to confirm delete
- Next: Enter trigger name to confirm delete

**Enter trigger name to confirm delete**

![Delete Trigger (image 22 of 22)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155014522368/original/6eQ0DnkP561wluUc9BZkj3VbytT196rMSQ.png)

**Delete Trigger (image 22 of 22)**

This screenshot appears in the "Delete Trigger" section of "Marketplace Workflow Triggers". The text alongside this image reads: Enter trigger name to confirm delete. For context, this section explains: Once a Trigger is deleted, it will be deleted permanently and cannot be restored. The deleted trigger will be removed from Marketplace App and Workflow Trigger list. If a deleted trigger is part of any workflow the trigger execution will be skipped. Immediately after, the guide continues: Workflow can run contactless without any Contact data dependency so you can send any payload data via Marketplace Triggers and use it in workflow. You can proceed without contact and use actions that are not dependent on contact….
- What to fill in: Enter trigger name to confirm delete
- Controls: Enter trigger name to confirm delete
- Next: Workflow can run contactless without any Contact data dependency so you can send any payload data via Marketplace Triggers and use it in workflow. You can proceed without contact and use actions that are not dependent on contact information. Custom Webhook, Google Sheet, Slack, ChatGPT and all Internal Tools can be executed without contact. If necessary, you can use the Create/Update or Find Contact actions to retrieve the contact data to the workflow. Example: Send order data to trigger and add the order information to google sheet, use if/else to categorize based on order value and send a slack notification. Retrieve the contact with Contact ID using Find contact action

## **Can workflow execute without contact?**

-   Workflow can run contactless without any Contact data dependency so you can send any payload data via Marketplace Triggers and use it in workflow.
-   You can proceed without contact and use actions that are not dependent on contact information. Custom Webhook, Google Sheet, Slack, ChatGPT and all Internal Tools can be executed without contact.
-   If necessary, you can use the Create/Update or Find Contact actions to retrieve the contact data to the workflow.  
    **Example:**
-   Send order data to trigger and add the order information to google sheet, use if/else to categorize based on order value and send a slack notification.
-   Retrieve the contact with Contact ID using Find contact action

---

Documentation for GHL Customer Care. Support: support@ghlcustomercare.com