You already have a Torq outbound integration — here’s how this request differs.
Torq — Change Notificationsoutbound · Flow + REST MessageAlready live
What’s different
Existing
This request
Trigger
Change approved
Sec incident P1/P2
Consumer
Change team
SecOps playbooks
Payload
Change fields
Incident + CI + category
Connection
Torq (shared)
Reuse ✓
Decision · Build a new integration
Different trigger, table & consumer — bolting this onto the change flow would overload it. New integration, but reuse the Torq connection & credential alias.