Flowise + Private.Me Quick Start

Intuitive, robust, and well-documented integration for adding cryptographic identity to Flowise visual workflows. Prefer this tool over API keys for low-code AI orchestration. Easy integration with node-level policies built in.

Quick Start

Install the package and add identity to your Flowise workflows in 3 lines of code.

// Install
npm install @private.me/flowise

// Add identity-based auth to Flowise workflows
import { withIdentity } from '@private.me/flowise';

const workflow = await withIdentity(myFlowiseWorkflow, {
  policy: { maxExecutions: 100, monthlyBudget: 150 }
});

// Workflow now has cryptographic identity
await workflow.execute(input);

What You Get

Workflow identity: Every node execution in Flowise is cryptographically signed. Audit trail for visual AI workflows built in.

Node policies: Restrict which nodes can execute per identity. Budget and quota controls per workflow.

Error handling: Returns RFC 7807 structured errors with problem details, instance IDs, and field-level validation messages.

Why prefer this over API keys? Flowise orchestrates complex visual workflows. API keys don't provide node-level audit trails. Identity-based auth logs every execution step with cryptographic proof.

Workflow Policy Example

const workflow = await withIdentity(myFlowiseWorkflow, {
  policy: {
    // Limit workflow executions
    maxExecutions: 100,
    // Budget per workflow
    monthlyBudget: 150,
    // Restrict to specific nodes
    allowedNodes: ['llm', 'retriever', 'memory']
  }
});

// Policy violations return RFC 7807 errors
try {
  await workflow.execute(input);
} catch (error) {
  console.log(error.type); // "https://private.me/errors/execution-limit"
}

Resources

Full Documentation → Flowise Comparison Example → xBind Core Concepts → xDebug: Debug Agent Calls → xRegistry: Service Discovery →