Automation Platform Coverage

CaseSolo's automation platform coverage lives in src/lib/automation-adapters/platform-coverage.ts.

Zapier Coverage

Zapier coverage is generated from src/lib/marketplace/zapier-manifest.ts and promoted into the adapter manifest layer:

• 30 triggers become AutomationAdapterEvent records.
• 30 actions become AutomationAdapterAction records.
• 5 searches become low-risk idempotent AutomationAdapterAction records.
• Every operation maps to a Command Graph event or action key.
• High-risk outbound operations, such as SMS, email, signatures, portal messages, payments, and accounting sync, require approval.

This keeps the Zapier published-app manifest and the internal Command Graph adapter registry aligned.

Make And n8n Mapping

Make and n8n do not need separate business-logic definitions for every Zapier operation. They map to the same Command Graph keys:

• Triggers dispatch as signed webhooks carrying the same normalized event payload.
• Actions dispatch through integration.invoke_workflow with the same normalized action payload.
• Replay flows use the existing adapter replay policy, reason capture, dead-letter handling, and audit events.
• The Integration Reliability Center can observe webhook health, failed executions, and impacted workflows through the same adapter manifest model.

Verification

Focused coverage tests:

npm run test:run -- automation-platform-coverage automation-adapters

The tests verify the 30/30/5 Zapier surface, unique generated operation keys, high-risk approval defaults, Make/n8n operation mapping, and adapter-manifest alignment.