You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/triggering.md
+23Lines changed: 23 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,6 +46,29 @@ Webhooks are configured automatically when you [enable](./enabling.md) your work
46
46
When you enable your %WORKFLOW%, the runner will automatically create a webhook in the third-party application to listen for events.
47
47
When an event occurs, the third-party application will send a request to your %WORKFLOW%'s webhook URL, triggering the %WORKFLOW% to run.
48
48
49
+
### Testing webhook-based app event triggers
50
+
51
+
After configuring a trigger that uses webhooks, you can test and capture webhook requests using the **Test** tab in the trigger's configuration drawer.
52
+
You can see your %WORKFLOW%'s unique test webhook URLs, by clicking **Webhook URLs**.
We can save the captured webhook request for use in testing our %WORKFLOW% by giving it a name and clicking **Save**.
67
+
We can then use that saved webhook request and use it later in our testing.
68
+
Saved payloads are available in the **Test** tab of the trigger's configuration drawer under **Saved Payloads**, and you can run your %WORKFLOW% using that payload by clicking **Run** button that appears when your mouse overs over the payload.
69
+
70
+
If you would like to test your %WORKFLOW% with a custom webhook payload, you can click **Configure Payload** to edit the payload data.
71
+
49
72
### App event triggers with polling
50
73
51
74
Some applications do not support webhooks, or webhook configuration is tedious.
0 commit comments