Govern enterprise marketplace support actions with OSuite approvals
UnknownWhat this workflow does
This workflow has 15 nodes and runs manually, when you click “Execute workflow”. Along the way it connects Osuite (community).
How it runs
Trigger: Manually, when you click “Execute workflow”.
- Set Enterprise Action Data (Edit Fields (Set)): sets 17 fields: case_id, action_title, requester…
- Execute Preflight Checks (Code): runs custom JavaScript code
- If: checks a condition and branches into true / false
- Capture Runtime Exposure Snapshot (Osuite): summarize runtime exposure
- Prepare Fix Intake Data (Edit Fields (Set)): sets 4 fields: status, blockers, warnings…
- Analyze Planned Work (Osuite): review planned work
- Build Approval Packet (Edit Fields (Set)): sets 8 fields: status, action_id, blocked…
- Check OSuite Block Status (If): checks a condition and branches into true / false
- Log OSuite Block Details (Edit Fields (Set)): sets 4 fields: status, action_id, approval_packet…
- Verify OSuite Approval (Osuite): check if approved
…plus 4 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that n8n-nodes-osuite is verified or supports 3.0 (used in Capture Runtime Exposure Snapshot, Analyze Planned Work, Verify OSuite Approval).
Nodes used (5)
- Manual Trigger
n8n-nodes-base.manualTrigger - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - Osuite
n8n-nodes-osuite.osuite
From the author
Quick overview This workflow runs on demand to preflight a high-value marketplace support action and send it to OSuite for governance review, then blocks, waits for approval, or proceeds to draft a safe internal refund-risk recommendation and records the…