docs: add Vaultak runtime security integration guide

[samueloladji-beep]

Summary

Adds a new integration guide for Vaultak — a runtime security platform that adds real-time protection to Dify API calls by risk-scoring user inputs, enforcing policy rules, and masking PII in responses.

Install: pip install vaultak

Changes

en/use-dify/monitor/integrations/integrate-vaultak.mdx (new)

Covers two integration patterns with complete code examples:

• Chat API (POST /v1/chat-messages) — score the user message before sending, mask PII in the response
• Workflow API (POST /v1/workflows/run) — check each workflow input against policy, mask PII in all output fields

Includes a configuration reference table and links to the Vaultak dashboard and Dify API reference.

docs.json — registers integrate-vaultak in the monitor/integrations nav group for all three language trees (en, zh, ja).

Note on integration approach

Unlike the observability-only tools in this section (Langfuse, LangSmith, Arize, etc.), Vaultak sits between the application and the Dify API rather than receiving traces from Dify. The page makes this distinction clear in the opening section.

Test plan

• Page renders correctly at /en/use-dify/monitor/integrations/integrate-vaultak
• Page appears in sidebar under Monitor → Integrations
• Code snippets are syntactically correct Python

🤖 Generated with Claude Code

[samueloladji-beep]

@AllenWriter @alterxyz — ready for review. This adds a Vaultak runtime security integration guide to the Dify monitoring docs.

[samueloladji-beep]

Hey @RiskeyL, all CI checks are passing — would appreciate a review when you get a chance. Thanks!

[RiskeyL]

@samueloladji-beep Thanks for the contribution, and for taking the time to write this up.

We're not able to merge integration guides for third-party products like Vaultak into the official Dify docs. This repo covers Dify's own features and its first-party integrations, so vendor-specific guides fall outside what we maintain here. Keeping that boundary lets us keep the docs focused and verifiable.

We'd still love for Dify users to find your integration. Better places to share it:

• The Dify community (Discord or GitHub Discussions), where users actively look for integrations
• Your own product docs or blog
• The Dify Marketplace, if you package it as a plugin, which gives it an installable surface inside Dify

Thanks again, and apologies we can't take this one.