See How Teams Use Ferrule
Real-world scenarios showing how organizations connect their tools to AI assistants
AI-Powered Legal Practice Management
Sarah — Office Manager at a 15-attorney firm
The Problem
The firm uses PracticePanther, Lawmatics, Zoom, Slack. Attorneys want AI assistants for research, drafting, and scheduling, but each AI needs separate integrations to each tool. Managing credentials across systems is a security nightmare.
The Solution
Sarah connects all four tools through Ferrule once, creates API keys per attorney's AI assistant, and sets up RBAC so paralegals access case data but not billing.
Workflow
- 1Connect PracticePanther, Lawmatics, Zoom Phone, and Slack through Ferrule's OAuth flow
- 2Create an organization and invite attorneys and paralegals with appropriate roles
- 3Generate scoped API keys for each attorney's AI assistant
- 4AI assistants access matters, contacts, call logs, and messages through one MCP endpoint
Integrations
Benefits
- Single credential management instead of four separate integrations per AI assistant
- AES-256-GCM encrypted token storage — no plaintext credentials
- Role-based access so paralegals see case data but not billing
- One connection point per tool, shared across all AI assistants
Unified Business Intelligence for AI Assistants
Marcus — Owner of a marketing consultancy
The Problem
Uses QuickBooks, GA, GSC, CallRail, Notion. Wants AI to pull cross-tool data for client reports, but each tool has different APIs and auth methods.
The Solution
Connects all five tools through Ferrule. AI queries financial data, analytics, call metrics, and project status through a single MCP endpoint. No raw credentials exposed.
Workflow
- 1Connect QuickBooks and Notion via OAuth, CallRail via API key — Ferrule handles both auth types
- 2Configure jq response projection to filter large API responses and reduce token usage
- 3Generate a single API key for the business AI assistant
- 4AI pulls cross-tool data for client reports through one gateway endpoint
Integrations
Benefits
- Cross-tool reporting without building custom integrations
- Secure credential storage — AI never sees raw OAuth tokens or API keys
- Mixed auth types (OAuth2 and API keys) handled automatically
- jq response filtering reduces token costs for AI assistants
Enterprise-Grade AI Tool Access
Priya — IT Manager at a growing professional services firm
The Problem
Multiple teams want AI assistants with company tools, but needs security compliance. Can't hand out raw credentials, needs MFA, audit trails, access control. Standalone MCP servers with local token files are unacceptable.
The Solution
Sets up Ferrule with multi-tenant orgs, RBAC, enforced 2FA, scoped API keys with 30-day expiry. All tokens encrypted with AES-256-GCM.
Workflow
- 1Set up a Ferrule organization and connect all 15 business tools
- 2Configure role-based access: owners manage integrations, admins manage keys, members use AI tools
- 3Enforce two-factor authentication for all organization members
- 4Issue scoped API keys with 30-day expiry and 100 req/min rate limits for each AI assistant
Integrations
Benefits
- Centralized security with AES-256-GCM encrypted credential storage
- MFA enforcement with TOTP, WebAuthn passkeys, or email OTP
- Role-based access control with owner, admin, and member tiers
- API key expiry, revocation, and rate limiting prevent abuse