RevLine Docs

Reference guide for workspace setup, integrations, and platform architecture

What is RevLine?

RevLine is a multi-workspace automation platform for managing integrations, workflows, booking flows, email capture, and payment processing. It centralizes all workspace configurations with encrypted secrets, configurable workflows, and a two-layer automation system.

Built on five core principles: agnostic, extensible, decoupled, secure, reliable.

Before RevLine

  • • Per-workspace environment variables
  • • Hardcoded automation logic
  • • Manual webhook management
  • • No centralized monitoring
  • • No booking or form infrastructure

With RevLine

  • • Database-backed encrypted secrets
  • • Two-layer automation (forms + workflows)
  • • Public REST API, signed webhooks & ingest URLs
  • • Health monitoring, event logs, network graph
  • • Provider-agnostic booking and form system

Core Concepts

Organizations

Top-level container. Each organization has members with granular permissions, templates for forms, and one or more workspaces. See the Organizations tab for details.

Workspaces

Each business you manage. Has a unique slug for routing, customizable lead stages, optional custom domain, and its own integrations, leads, and workflows. Example: acme_fitness

Integrations

Connections to external services. 7 adapters: MailerLite, Stripe, Calendly, ManyChat, ABC Ignite, RevLine (forms), and Resend (transactional email). Each has encrypted secrets and JSON configuration.

Forms & Templates

Layer 1 of automation. Forms declare baked-in operations that run automatically (e.g., the booking flow: lookup → eligibility → magic link → enroll). Templates provide org-scoped copy and branding. See the Forms & Sites tab.

Workflows

Layer 2 of automation. User-configured rules that connect triggers to actions. Example: When a booking is confirmed, update the lead stage and add to a MailerLite group. See the Workflows tab.

Events

Append-only audit log. Every email capture, payment, booking, workflow execution, and integration call is logged with timestamps, success/failure, and error details. Events are the primary debugging surface.

Leads

Pipeline tracking for captured contacts. Each lead has a stage (customizable per workspace — defaults: CAPTURED, BOOKED, PAID, DEAD), source, event history, and custom properties (schema-validated fields like barcode, member type, etc.). Unique per workspace+email. See the Organizations tab for custom lead properties.

Data Hierarchy

Organization
→ Members (owner + members with permissions)
→ Templates (booking, signup copy/branding)
→ Workspace
→ Integrations (7 types, encrypted secrets)
→ Leads (email, stage, source, events)
→ Workflows (trigger → filter → actions)
→ Forms (booking, signup — baked-in ops)
→ Events (append-only audit log)

Workspace Onboarding Flow

  1. 1

    Create Organization

    Set up the org, invite team members, configure permissions.

  2. 2

    Create Workspace

    Add the workspace with name, slug, and timezone. Optionally set up custom domain and lead stages.

  3. 3

    Add Integrations

    Configure each integration with secrets and settings (MailerLite, Stripe, ABC Ignite, Resend, etc.)

  4. 4

    Enable Forms

    Configure the RevLine integration, enable forms (booking, signup), customize copy via templates.

  5. 5

    Build Workflows

    Create workflows to react to form triggers and webhook events (update stages, add to groups, etc.)

  6. 6

    Test & Verify

    Run health checks, test each flow, verify events in the dashboard. Use the testing panel for API testing.

💡

Time Estimate

A complete workspace onboarding typically takes 1-2 hours: 15 min setup, 30 min integrations, 30 min workflows, 15 min testing.

Quick Reference

Public API Endpoints

Create LeadPOST /api/v1/leads
Look up LeadGET /api/v1/leads
Publish EventPOST /api/v1/events
Poll EventsGET /api/v1/events
Inbound IngestPOST /api/v1/ingest/{token}
Health CheckGET /api/v1/health

Full reference, auth, and webhook signing in the Platform API tab.

Default Lead Stages

CAPTURED— Email submitted
BOOKED— Appointment scheduled
PAID— Payment received
DEAD— Inactive/unsubscribed

Stages are customizable per workspace. See the Organizations tab.

For Developers

Building an integration on top of RevLine? Start with the Platform API tab for the REST API, webhooks, and ingest URLs. New to the codebase itself? The Architecture tab covers the two-layer system, security patterns, and a key files reference.

Recommended Reading

Platform API — REST API, webhooks, ingest, event catalog

Architecture — Directory structure, patterns, key files

Organizations — Permissions, roles, access control

Forms & Sites — Two-layer system, baked-in operations

Testing — Test flows, testing panel, debugging

+ New WorkspaceView Workspaces