Resoproof

Integrations

Resoproof is built to turn evidence from your existing tools into proof. Today that means our own email chase and export. More sources are added as firms need them — every one writes to the same append-only, hash-chained log.

Resend

Email deliveryBuilt-in

Resoproof uses Resend to send document-request emails and automatic reminder sequences. Delivery, open, and click events flow back via signed webhooks and are written directly to the case event log.

  • Templated initial requests with merge fields
  • Automatic reminder sequences on your cadence
  • Delivery, open, and link-click tracking
  • Signed webhook verification (Svix)
  • Simulate mode for preview environments

Setup

Add RESEND_API_KEY, RESEND_FROM_EMAIL, and RESEND_WEBHOOK_SECRET as environment variables. Point your Resend webhook at /api/webhooks/resend and enable the email.delivered, email.opened, email.clicked, and email.bounced events.

Supabase

Database, Auth & StorageBuilt-in

The entire Resoproof data layer runs on Supabase: PostgreSQL with Row Level Security for multi-tenant isolation, native Auth for staff logins, and private Storage for client document uploads.

  • PostgreSQL with per-firm RLS on every table
  • Append-only events table with trigger enforcement
  • SHA-256 hash-chain verification function
  • Native email + password auth with session refresh
  • Private storage bucket with signed URL serving

Setup

Connect your Supabase project in the v0 Settings panel. The required environment variables (NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY) are injected automatically.

Vercel Cron

Scheduled jobsBuilt-in

A daily cron job runs the cadence engine, finds all overdue reminder schedules, and fires the next step for each. It is protected by a CRON_SECRET header and runs automatically on your Vercel deployment.

  • Daily cadence runner (configurable in vercel.json)
  • CRON_SECRET header protection
  • Idempotent — safe to trigger manually for testing
  • Writes reminder events to the hash chain
  • Deactivates schedules when all items are accepted

Setup

Set CRON_SECRET as an environment variable. The cron schedule is defined in vercel.json and activates automatically on deploy. You can trigger it manually via POST /api/cron/cadence with the Authorization header.

Coming soon

These integrations are on the roadmap. Each one will write events to the hash chain like every other action.

Slack notifications

Get a Slack message when a client submits a document or a case closes.

Zapier / Make webhooks

Fire an outbound webhook on any event type to connect your practice management system.

DocuSign / HelloSign

Request e-signatures as a first-class item type alongside uploads and forms.

IRS transcript pull

Fetch transcripts directly and mark items accepted without client involvement.

Custom domain emails

Send from a fully custom domain with DKIM/SPF aligned to your firm.