From 615307ae01a7e0a0a1031e6d63a79585344df204 Mon Sep 17 00:00:00 2001 From: Max Helmetag Date: Fri, 31 Jan 2025 18:28:35 -0500 Subject: [PATCH] remove webhooks section for now since endpoints aren't public --- tutorials/tutorial_workflows_v2.md | 16 ---------------- 1 file changed, 16 deletions(-) diff --git a/tutorials/tutorial_workflows_v2.md b/tutorials/tutorial_workflows_v2.md index ea2f13f..d9d5509 100644 --- a/tutorials/tutorial_workflows_v2.md +++ b/tutorials/tutorial_workflows_v2.md @@ -58,22 +58,6 @@ This is how to determine which API endpoints should be used for the specific too ## Example Known Use Cases -### Webhooks - -Instances fire a number of events that can be used as triggers for webhooks. This new event driven system for webhooks doesn't have a UI yet so this section has some info needed for creating a trigger. - -The `resource_name` is "Workflow Instance". - -The `event_type` can be one of: -- "STARTED" -- “CURRENT_STEP_ASSIGNEES_CHANGED” -- “RESPONSE_RECEIVED” -- “TRANSITIONED” -- “ENDED” -- “TERMINATED” -- “RESTARTED” -- “DELETED” - ### Integration Driven Workflow When routing an instance step with an integration, the integration steps (a step where you expect the integration to chose a path) must have the integration user listed as one of the assignees.