Automation Adapter Manifests

Updated: 2026-06-03 Status: Manifest registry implemented, live execution still gated by provider tasks

CaseSolo now has a typed adapter manifest registry at src/lib/automation-adapters/. These manifests describe how each provider plugs into the Command Graph before the live trigger/action registry, webhook wizard, Integration Reliability Center, and provider execution clients are fully built.

Registry Scope

The registry covers the task-0599 adapter set:

| Adapter | Category | Status | Primary role | |---|---|---|---| | Custom Webhook | Webhook | Manifest ready | HMAC delivery, sample payloads, delivery history, replay | | Zapier | Automation platform | Manifest ready | Published app bridge for long-tail triggers/actions | | Make | Automation platform | Manifest ready | Custom webhook/scenario bridge | | n8n | Automation platform | Manifest ready | Self-hosted/cloud workflow bridge | | Slack | Communications | Manifest ready | Notifications, approval prompts, slash commands | | Microsoft Teams | Communications | Manifest ready | Notifications, approval cards, channel messages | | Twilio | Communications | Live capable | SMS, delivery receipts, inbound threading, TCPA signals | | Google Calendar | Calendar | Manifest ready | Two-way calendar/deadline sync | | Outlook Calendar | Calendar | Manifest ready | Microsoft Graph calendar sync | | DocuSign | Document signature | Live capable | Envelope send/status/signed-document capture | | Adobe Acrobat Sign | Document signature | Live capable | Agreement send/status/signed-document capture | | QuickBooks Online | Accounting | Live capable | Invoice, payment, expense, sync, replay | | Google Workspace | Workspace | Planned | Gmail and Drive case context sync | | Microsoft 365 | Workspace | Planned | Outlook mail, OneDrive, SharePoint sync | | LawPay | Payments | Planned | Legal payment links and trust-safe payment recording | | Court E-Filing | Court | Planned | Rule validation, filing, stamped-copy capture |

What Each Manifest Defines

Each manifest includes:

• Provider ID, slug, category, version, implementation status, and docs path.
• Auth requirements, required environment variables, scopes, callback paths, and signing headers.
• Supported events with Command Graph event mapping, direction, replay class, and sample payloads.
• Supported actions with Command Graph action mapping, input fields, risk, approval requirement, and replay class.
• Health signals for the future Integration Reliability Center.
• Command Graph source kind, actor type, required scopes, idempotency key strategy, and audit prefix.
• Reliability metadata for replay, dead letters, delivery history, and health-check expectations.

Automation Platform Coverage

Zapier is now generated into the adapter manifest layer from the published Zapier app manifest:

• 30 Zapier triggers are promoted into adapter events.
• 30 Zapier actions and 5 Zapier searches are promoted into adapter actions.
• High-risk Zapier actions are approval-gated before production workflow use.
• Make and n8n reuse the same Command Graph payloads through signed scenario/workflow webhooks instead of duplicating business logic.

See Automation Platform Coverage for the exact mapping and verification path.

Safety Defaults

• High-risk and critical actions are approval-gated by default.
• Replay actions require a human reason and approval.
• Financial, payment, signature, e-filing, client-facing message, and webhook replay actions are treated as high-risk or critical.
• Idempotency strategies include firmId so provider retries cannot cross tenant boundaries.
• Provider secrets and tokens are represented as auth fields, not event/action payload fields.

Verification

Focused manifest tests:

npm run test:run -- src/__tests__/lib/automation-adapters.test.ts

The test suite verifies required adapter coverage, unique IDs/slugs, required manifest metadata, approval defaults for high-risk actions, replay reason requirements, lookup helpers, and summary output for future Reliability Center surfaces.