Skip to content
App marketplace

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…

6 min read1,278 words22 explained imagesUpdated Fri, 16 Aug, 2024 at 2:19 AM
View as markdownOpen in ClaudeOpen in ChatGPT
Each image has a one line explanation. Switch to full detail for the step it belongs to, the fields and buttons involved, examples and the whole procedure.
On this page
  1. Prerequisites
  2. Create Trigger
  3. Name
  4. Icon
  5. Name
  6. Key
  7. Short description
  8. Summary
  9. Trigger Data
  10. Manage Filters
  11. Create New Filter
  12. Type: Select / Multi Select
  13. Type: Dynamic
  14. Manage Custom Variables
  15. Add Custom Variable
  16. Subscription URL
  17. Submit for Review
  18. Create New Version
  19. Delete Trigger
  20. Can workflow execute without contact?

Video 1 Open in a new tab

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

Note : workflows.readyonly scope should be turned on to enable actions and triggers.

Prerequisites (image 1 of 22) What this shows Note: workflows.readyonly scope should be turned on to enable actions and triggers. What this shows Illustrates the "Prerequisites" section of "Marketplace Workflow Triggers". 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}}. Image 1 of 22 What this coversNote: workflows.readyonly scope should be turned on to enable actions and triggers. Next stepA 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) What this shows Note: workflows.readyonly scope should be turned on to enable actions and triggers. What this shows Illustrates the "Create Trigger" section of "Marketplace Workflow Triggers". 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}}. Image 2 of 22 What this coversNote: workflows.readyonly scope should be turned on to enable actions and triggers. Next stepA 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) What this shows A unique identifier for this trigger, used to reference the trigger inside the workflow. What this shows Illustrates the "Trigger Information" section of "Marketplace Workflow Triggers". 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. Image 3 of 22 What this coversA unique identifier for this trigger, used to reference the trigger inside the workflow. This value cannot be changed later. Example: {{mycustomtrigger.data.name}} Next stepChoose 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) What this shows Enter a valid sample payload JSON structure that will be sent to the trigger. What this shows Illustrates the "Trigger Data" section of "Marketplace Workflow Triggers". 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. Image 4 of 22 What to fill inEnter a valid sample payload JSON structure that will be sent to the trigger.
Buttons and menus referenced Add sample trigger payload data
Next stepAdd 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) What this shows Add filters using sample trigger data, for users to use in workflows trigger configuration. What this shows Illustrates the "Manage Filters" section of "Marketplace Workflow Triggers". 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. Image 5 of 22 What this coversAdd filters using sample trigger data, for users to use in workflows trigger configuration. Next stepSelect one of the following field types:

Create New Filter

Create New Filter (image 6 of 22) What this shows Add filters using sample trigger data, for users to use in workflows trigger configuration. What this shows Illustrates the "Create New Filter" section of "Marketplace Workflow Triggers". 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. Image 6 of 22 What this coversAdd filters using sample trigger data, for users to use in workflows trigger configuration.
Fields in this part of the guide StringMultiple SelectDynamic
Buttons and menus referenced NameTypeRequiredReferenceAlters Dynamic Filter
Next stepSelect one of the following field types:
All 4 steps in this 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) What this shows If enabled, any changes made to this filter value will trigger/ re-trigger loading the dynamic filters to the workflow trigger configuration UI. What this shows Illustrates the "Type: Select / Multi Select" section of "Marketplace Workflow Triggers". 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. Image 7 of 22 What this coversIf enabled, any changes made to this filter value will trigger/ re-trigger loading the dynamic filters to the workflow trigger configuration UI.
Fields in this part of the guide ConstantsInternal ReferenceExternal API
Next stepOption Type is applicable only for Select and Multi Select field types.
All 3 steps in this 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) What this shows Load options by adding custom Label-Value constants What this shows Illustrates the "Constants" section of "Marketplace Workflow Triggers". 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. Image 8 of 22 What this coversLoad options by adding custom Label-Value constants Next stepLoad 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) What this shows Load options from GHL Customer Care Internal Modules. What this shows Illustrates the "Internal Reference" section of "Marketplace Workflow Triggers". 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. Image 9 of 22 What to chooseLoad options from GHL Customer Care Internal Modules. Select one of the GHL Customer Care Modules to load options list. Next stepSupported GHL Customer Care Modules
Supported GHL Customer Care Modules
Internal Reference (image 10 of 22) What this shows Supported GHL Customer Care Modules What this shows Illustrates the "Internal Reference" section of "Marketplace Workflow Triggers". 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. Image 10 of 22 What this coversSupported GHL Customer Care Modules Next stepLoad option from external API endpoint

External API

Load option from external API endpoint

External API (image 11 of 22) What this shows Load option from external API endpoint What this shows Illustrates the "External API" section of "Marketplace Workflow Triggers". 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. Image 11 of 22 What this coversLoad option from external API endpoint
Buttons and menus referenced URL (GET)HeadersSample Response Data
Next stepProvide 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) What this shows Dynamic filters are used to build custom filters from an API call. What this shows Illustrates the "Type: Dynamic" section of "Marketplace Workflow Triggers". 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. Image 12 of 22 What to fill inDynamic 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.
Buttons and menus referenced URL (POST)HeadersSample structure for each Filter Types
Next stepEnter 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) What this shows Add Custom variables using trigger data, for users to use in workflows. What this shows Illustrates the "Manage Custom Variables" section of "Marketplace Workflow Triggers". 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. Image 13 of 22 What this coversAdd Custom variables using trigger data, for users to use in workflows. Next stepSelect a reference key from the sample trigger data.

Add Custom Variable

Add Custom Variable (image 14 of 22) What this shows Add Custom variables using trigger data, for users to use in workflows. What this shows Illustrates the "Add Custom Variable" section of "Marketplace Workflow Triggers". 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. Image 14 of 22 What this coversAdd Custom variables using trigger data, for users to use in workflows.
Buttons and menus referenced NameReference
Next stepSelect 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) What this shows Collect trigger configuration details through API endpoint. What this shows Illustrates the "Subscription URL" section of "Marketplace Workflow Triggers". 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. Image 15 of 22 What this coversCollect trigger configuration details through API endpoint.
Buttons and menus referenced URL (POST)HeadersTrigger "CREATED" in workflowTrigger "UPDATED" in workflow
Next stepEnter 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) What this shows The trigger version will be in draft state by default. What this shows Illustrates the "Submit for Review" section of "Marketplace Workflow Triggers". 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. Image 16 of 22 What this coversThe trigger version will be in draft state by default. After updating the trigger information and configuration the trigger version should be submitted for review.
Buttons and menus referenced Submit for reviewchangelog
Next stepClick 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) What this shows Click on Submit for review and add required changelog information for the submitted version. What this shows Illustrates the "Submit for Review" section of "Marketplace Workflow Triggers". 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. Image 17 of 22 How to confirmClick on Submit for review and add required changelog information for the submitted version.
Buttons and menus referenced Submit for reviewchangelog
Next stepOnce 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) What this shows Once approved the version submitted for review will be published live to all Sub-accounts. What this shows Illustrates the "Submit for Review" section of "Marketplace Workflow Triggers". 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. Image 18 of 22 What this coversOnce approved the version submitted for review will be published live to all Sub-accounts.
Buttons and menus referenced Submit for reviewchangelog
Next stepClick 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) What this shows Click on + New Version to create a new version for the trigger What this shows Illustrates the "Create New Version" section of "Marketplace Workflow Triggers". 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. Image 19 of 22 What to clickClick on + New Version to create a new version for the trigger
Buttons and menus referenced + New Version
Next stepOn 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) What this shows On clicking + New Version It will create a new draft version with all the previously published data prefilled. What this shows Illustrates the "Create New Version" section of "Marketplace Workflow Triggers". 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…. Image 20 of 22 What this coversOn clicking + New Version It will create a new draft version with all the previously published data prefilled.
Buttons and menus referenced + New Version
Next stepOnce 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) What this shows Once a Trigger is deleted, it will be deleted permanently and cannot be restored. What this shows Illustrates the "Delete Trigger" section of "Marketplace Workflow Triggers". 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. Image 21 of 22 What this coversOnce 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.
Buttons and menus referenced Enter trigger name to confirm delete
Next stepEnter trigger name to confirm delete

Enter trigger name to confirm delete

Delete Trigger (image 22 of 22) What this shows Enter trigger name to confirm delete What this shows Illustrates the "Delete Trigger" section of "Marketplace Workflow Triggers". 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…. Image 22 of 22 What to fill inEnter trigger name to confirm delete
Buttons and menus referenced Enter trigger name to confirm delete
Next stepWorkflow 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

Frequently asked questions

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

Was this guide helpful?

Related guides