Skip to main content

Closed-Loop Approval Workflows

Workflows C through E handle the complete approval lifecycle for project-type tickets.

WF C: Solution Doc + DTO Group Assign​

Triggered by Webhook #1 (new ticket). Filters for project tickets, generates AI solution document, assigns to DTO group, and posts followup.

WF C2: DTO Member Self-Assignment Detection​

Triggered by Webhook #3 (ticket update). Detects when a DTO member first self-assigns to a ticket and creates a DTO validation request to start the approval loop.

WF D: Validation Response Handler​

Workflow ID: fzvNTI3TJzmldi0P

Triggered by Webhook #2 (approval/rejection). Routes based on:

  • DTO Approve → Triggers WF E for BRD generation
  • DTO Reject → AI regenerates solution document
  • Requester Approve → Closes the approval loop
  • Requester Reject → Routes back for revision

Uses Switch node (typeVersion 3.4) with rules.values[] format.

WF E: BRD + ClickUp + Smart Assignment​

Workflow ID: hwwofEuJF68kbgp0

Triggered internally by WF D. Generates Business Requirements Document (BRD), creates PDF, uploads to GLPI, creates ClickUp task, and performs smart assignment based on technical skills matching.

Complete Chain Flow​

New Project Ticket
  → WF C: AI doc + DTO assign
  → WF C2: Self-assignment detected → create validation
  → WF D: DTO approves → trigger WF E
  → WF E: BRD + PDF + ClickUp + smart assign
  → WF D: Requester approves → done