{"id":6608,"date":"2023-11-17T08:00:42","date_gmt":"2023-11-17T08:00:42","guid":{"rendered":"https:\/\/www.process.st\/help\/docs\/webhook-triggers\/"},"modified":"2025-07-28T13:56:22","modified_gmt":"2025-07-28T13:56:22","slug":"webhook-triggers","status":"publish","type":"ht_kb","link":"https:\/\/www.process.st\/help\/docs\/webhook-triggers\/","title":{"rendered":"Webhook Triggers"},"content":{"rendered":"

Webhooks are event-driven messages sent from one app to another. The messages contain a payload that you can exploit to pass or receive data into or out of Process Street<\/a>.<\/p>\n

You can use outgoing webhooks<\/strong><\/a> to keep your other tools notified about the status of a workflow run or task in Process Street, or use incoming webhooks (webhook triggers<\/strong>) to run a workflow automatically when something happens in another app.<\/p>\n

Users: You must be an Administrator or a Builder<\/a> with edit permissions in order to set up Webhook Triggers.\u00a0<\/strong><\/em><\/p>\n

Webhook Triggers<\/h2>\n

You can use Process Street\u2019s webhook triggers to listen for event-driven triggers in other apps, to run a workflow in Process Street.<\/p>\n

For example, run a workflow when a candidate is marked as hired in People HR<\/a>, when supplier details change in Hubspot<\/a> or when a new task is added in Asana<\/a>.<\/p>\n

Check your form fields<\/h3>\n

Be sure to have form fields<\/a> set up and ready to capture data from your webhook trigger. For example, Employee First name, Employee Last name, Date of contract, Salary etc.<\/p>\n

Setting up a Webhook Trigger<\/h3>\n

Start by editing the workflow you\u2019d like to set up the webhook trigger on.<\/p>\n

Click Triggers<\/strong> to open the setup modal, as shown below.<\/p>\n

\"\"<\/p>\n

Search for the app you\u2019d like to connect to and give it a name.<\/p>\n

Note:<\/strong> You can also set up a custom webhook for any app you’d like. Type webhook<\/strong> into the search box to set this up.<\/p>\n

For additional guidance, each of the apps has a link to a help document for webhooks inside the set-up modal.<\/p>\n

Note:<\/strong> If your app gives you options for payload content type, be sure to select JSON format.<\/strong><\/p>\n

\"\"<\/p>\n

Click to Copy<\/strong> your webhook URL.<\/p>\n

Next, select the event you\u2019d like to use as the trigger. Some apps only have one option, in which case, select default<\/strong> as shown above.<\/p>\n

Click See Payload<\/strong> to check what data comes in from your chosen webhook.<\/p>\n

Now you can map the fields from the webhook to form fields in your workflow. The webhook fields are automatically created for you. All you need to do is map them to your Process Street form fields.<\/p>\n

When you’re done mapping fields, turn on<\/strong> the webhook with the toggle switch and click Save<\/strong> to finish.<\/p>\n

Now each time the event occurs in your other app, a workflow will be run in Process Street.<\/p>\n

IP addresses used<\/h3>\n

There is no specific IP address used when sending webhooks, but it will always be an AWS IP address.<\/p>\n

Webhook Trigger FAQ\u2019s<\/h3>\n

Why isn\u2019t my workflow running?<\/strong><\/em><\/p>\n

You may not have completed the setup for the webhook. If you see an orange warning sign like the one below, click the app’s name to complete the setup. Turn on<\/strong> the trigger and click Save<\/strong> to finish setting it up.<\/p>\n

\"\"<\/p>\n

I don\u2019t see the app I want to use in the list<\/strong><\/em><\/p>\n

We will be adding more apps to the list over time, but please contact our support team<\/a> to request the app you\u2019d like to use. Alternatively, you can use the other third-party tools shown in the setup modal to run your workflow.<\/p>\n","protected":false},"excerpt":{"rendered":"

Webhooks are event-driven messages sent from one app to another. The messages contain a payload that you can exploit to pass or receive data into or out of Process Street. You can use outgoing webhooks to keep your other tools notified about the status of a workflow run or task in Process Street, or use […]<\/p>\n","protected":false},"author":11,"template":"","meta":{"_acf_changed":false,"available_plan":"All plans","available_product":"Integrations","footnotes":""},"ht_kb_category":[194],"ht_kb_tag":[466,476],"class_list":["post-6608","ht_kb","type-ht_kb","status-publish","hentry","ht_kb_category-integrations","ht_kb_tag-running-workflows","ht_kb_tag-webhooks"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.process.st\/help\/wp-json\/wp\/v2\/ht_kb\/6608","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.process.st\/help\/wp-json\/wp\/v2\/ht_kb"}],"about":[{"href":"https:\/\/www.process.st\/help\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/www.process.st\/help\/wp-json\/wp\/v2\/users\/11"}],"version-history":[{"count":3,"href":"https:\/\/www.process.st\/help\/wp-json\/wp\/v2\/ht_kb\/6608\/revisions"}],"predecessor-version":[{"id":9262,"href":"https:\/\/www.process.st\/help\/wp-json\/wp\/v2\/ht_kb\/6608\/revisions\/9262"}],"wp:attachment":[{"href":"https:\/\/www.process.st\/help\/wp-json\/wp\/v2\/media?parent=6608"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/www.process.st\/help\/wp-json\/wp\/v2\/ht_kb_category?post=6608"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/www.process.st\/help\/wp-json\/wp\/v2\/ht_kb_tag?post=6608"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}