docs: consolidate deletion audit events on streaming-events page (replaces #695, #709, #712, #722)

[jordanc-relevanceai]

Summary

Consolidates the four open PRs that all documented deletion audit events on enterprise/streaming-events.mdx into a single change, and corrects the attribute tables against the OTEL event definitions in relevance-api-node. Branched from main.

Adds to Supported events:

• conversation_deleted — new ### Conversation events section
• workforce_task_deleted — under Workforce events
• workforce_type — new optional attribute on the existing workforce_deleted event
• trigger_deleted — new ### Trigger events section
• knowledge_table_deleted — new ### Knowledge events section

Replaces these PRs (now closed)

PR	What it covered	Status here
#695	workforce_task_deleted	Folded in — its table was the most accurate of the four and is kept as-is
#709	conversation_deleted, workforce_task_deleted	Folded in, 2 attribute corrections
#712	trigger_deleted, knowledge_table_deleted	Folded in, 1 field rename + 1 scope fix
#722	conversation_deleted, workforce_task_deleted, workforce_type	Folded in, 3 attribute corrections

#709 and #722 were near-duplicates of each other (both drafted from relevance-api-node#16143) and #695 documented the same workforce_task_deleted event a month earlier. Merging them as-is would have produced duplicate event entries on one page.

Corrections applied during consolidation

Each was verified against the event definitions in relevance-api-node:

• agent_id on conversation_deleted is optional, not required. docs(TSP-1339): add conversation_deleted and workforce_task_deleted audit events #709 and docs(TSP-1348): add deletion audit events to streaming-events page #722 both marked it Yes. Code: .optional() in apps/nodeapi/src/modules/shared/services/data_streaming/otel/definitions/audit_logs/conversations.ts.
• workforce_id is not an attribute of workforce_task_deleted. docs(TSP-1339): add conversation_deleted and workforce_task_deleted audit events #709 and docs(TSP-1348): add deletion audit events to streaming-events page #722 both listed it as required. The event defines only workforce_task_id — see audit_logs/workforces.ts.
• workforce_task_id and workforce_type are not attributes of conversation_deleted. docs(TSP-1348): add deletion audit events to streaming-events page #722 added both to that event's table. conversation_deleted defines only conversation_id and agent_id.
• workforce_type values are not "direct" / "cascade". docs(TSP-1348): add deletion audit events to streaming-events page #722 documented those. The field holds the workforce's configured type (e.g. chat) and lives on workforce_deleted, which is where it is documented here.
• The trigger provider field is trigger_provider, not integration_provider. Add trigger_deleted and knowledge_table_deleted OTEL audit events to streaming events docs #712 used the latter. See audit_logs/triggers.ts.
• trigger_provider is not limited to external_relay triggers. Add trigger_deleted and knowledge_table_deleted OTEL audit events to streaming events docs #712 said it only appears for relay-type triggers; the code describes it as present for any trigger backed by an integration. Provider values are lowercase (slack, gmail), not title-case.
• trigger_type is a free-form string, so the three known values are given as examples rather than a closed set.

Decisions worth a look

• conversation_deleted gets its own section rather than sitting under Agent events (docs(TSP-1339): add conversation_deleted and workforce_task_deleted audit events #709's placement). This matches how the code groups it — conversationEvents is a separate definition file from the agent events — and keeps the Agent events section focused on the agent entity itself.
• Dropped the per-event "only emitted for organizations with the customer OTEL integration configured" note that Add trigger_deleted and knowledge_table_deleted OTEL audit events to streaming events docs #712 added inline. The entire page describes the customer OTEL integration and no other event on it carries that caveat, so it read as inconsistent. Happy to add it back as a single note at the section level if you'd prefer it stated explicitly.

Test plan

• Mintlify preview renders the three new sections and both new tables
• Section order reads Agent → Conversation → Tool → Workforce → Trigger → Knowledge → Permission
• No duplicate event entries on the page

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
relevanceai	🟢 Ready	View Preview	Jul 31, 2026, 6:54 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.