Privent icon

Privent

Privent DLP: session-scoped tokenization, detokenization, risk scoring, audit events and agent handoffs for AI agent workflows.

Actions6

Session → Open

AI-generated

Summary

Open a Privent session and add its session ID and optional agent name to each output item. In API Key or Tokenless mode, the session ID can be generated automatically or supplied manually; Local mode does not offer session settings for this operation.

Inputs

  • Authentication (required) — Choose API Key, Tokenless (Visitor), or Local (No Backend). The session ID, agent name, framework, and webhook settings are shown only for API Key and Tokenless modes.
  • Session ID Mode (required) — In API Key or Tokenless mode, choose Auto-Generate to create a UUID for each workflow execution, or Manual to resume a session using your own ID.
  • Session ID (required) — Required in Manual mode; a stable string identifying the session.
  • Agent Name — Optional logical agent identifier. Added to output items and forwarded to downstream Privent nodes; audit events use it as agent_name.
  • Framework — Select Manual / Custom or Native (n8n); identifies the orchestration framework in audit logs. Defaults to Native.
  • Webhook Node Name — Optional upstream Webhook node name, defaulting to Webhook. When set, the SDK attempts to read client IP and User-Agent from its headers for the session record; parse failures are silent.

Output shape

One output item per input item, retaining its data and adding session context.

In API Key and Tokenless modes, items include the session ID and configured agent name. Auto-generated IDs are per workflow execution; manual IDs can be reused to resume a session. Local mode has no backend session handling.

Examples

Example 1: Choose API Key mode when the session should use Privent's vault, audit, handoff, and risk scoring features. Provide a Privent API key credential for this mode.

Select API Key authentication, choose Auto-Generate or enter a stable Session ID in Manual mode, and optionally set Agent Name and Framework.

Example 2: Choose Tokenless (Visitor) mode when you want in-memory tokenization and risk scoring tied to an anonymous visitor ID without an API key. The backend must have visitor authentication enabled.

Select Tokenless authentication, choose Auto-Generate or enter a stable Session ID in Manual mode, and optionally set Agent Name, Framework, and the upstream Webhook node name.

Example 3: Choose Local (No Backend) mode when you want local tokenization and detokenization with regex detection and no backend calls.

Select Local authentication. Session ID mode, Session ID, Agent Name, Framework, and Webhook Node Name are unavailable in this mode.

Links

Discussion