# Email Sequences with Customer.io and Calendly



Run email sequences in **Customer.io** when leads submit your Surface form, whether they complete it or drop off partway. The sequence exits automatically once a lead books a **Calendly** meeting, so nobody who has already scheduled a call keeps getting emails.

## How It Works [#how-it-works]

<Steps>
  <Step title="Form submission">
    A lead submits your Surface form (partial or completed). Surface sends a
    webhook to the appropriate Customer.io URL based on the trigger.
  </Step>

  <Step title="Person & event">
    Two webhook-triggered campaigns in Customer.io (one for partial, one for
    completed) create or update the person and add the appropriate event.
  </Step>

  <Step title="Email sequence">
    An event-triggered campaign starts a customizable follow-up email sequence
    with delays between each email.
  </Step>

  <Step title="Meeting check">
    Before each follow-up (after the first), a webhook checks the Calendly API.
    If the lead has booked a meeting, the campaign exits. Otherwise, it
    continues.
  </Step>
</Steps>

## Prerequisites [#prerequisites]

You need:

* A **Surface** account with a form that supports partial submissions (e.g., multi-step form with email capture)
* A **Customer.io** account with Campaigns and Journeys access
* A **Calendly** account with API access (Personal Access Token or OAuth)
* Your Calendly event type URI for the meeting type you want to check

## Setup Steps [#setup-steps]

<CardGroup cols="2">
  <Card title="Step 1: Webhook Trigger Campaigns" icon="webhook" href="/guides/email-sequences-customerio-calendly/step-1-webhook-trigger">
    Create two webhook-triggered campaigns in Customer.io, one for partial and one for completed, each with its own URL
  </Card>

  <Card title="Step 2: Configure Surface Workflow" icon="diagram-project" href="/guides/email-sequences-customerio-calendly/step-2-surface-workflow">
    Set up the Surface Workflow Builder to send form data to the correct
    Customer.io webhook URL based on trigger path (Dropped Off or Form Submission)
  </Card>

  <Card title="Step 3: Event-Based Email Campaigns" icon="envelope" href="/guides/email-sequences-customerio-calendly/step-3-event-campaigns">
    Create two event-triggered campaigns, one for partial submissions and one for
    completed, with your follow-up emails and delays
  </Card>

  <Card title="Step 4: Calendly Meeting Check" icon="calendar-check" href="/guides/email-sequences-customerio-calendly/step-4-calendly-check">
    Add a webhook node before each follow-up (after the first) to check if the lead booked a meeting and exit the campaign if so
  </Card>
</CardGroup>

## Campaign Flow Diagram [#campaign-flow-diagram]

```mermaid
flowchart LR
    %% Participants & Subgraphs
    subgraph S [Surface]
        direction TB
        Lead([Lead])
        Form[Form Submission]
    end

    subgraph C [Customer.io]
        direction TB
        Webhook[Webhook Trigger]
        Campaign[Start Campaign]
        Email1[Send Email 1]
        Delay[Wait X Days]
        Check[Check Meeting]
        Decision{Booked?}
        Exit[Exit Campaign]
        Next[Send Follow-up]
    end

    subgraph K [Calendly]
        direction TB
        API[Calendly API]
    end

    %% Connections
    Lead -->|Submits| Form
    Form -->|Webhook Data| Webhook
    Webhook --> Campaign
    Campaign --> Email1
    Email1 --> Delay
    Delay --> Check

    Check -.->|Query| API
    API -.->|Status| Check

    Check --> Decision
    Decision -->|Yes| Exit
    Decision -->|No| Next
    Next --> Delay

    %% Styling
    classDef plain fill:#fff,stroke:#333,stroke-width:1px;
    classDef check fill:#e6f7ff,stroke:#1890ff,stroke-width:2px;

    class Lead,Form,Webhook,Campaign,Email1,Delay,Exit,Next plain;
    class Check,Decision,API check;
```