SVD OnlineSVD Online
← All workflows
Client delivery

Post-delivery follow-up

After a project is delivered, every client gets a short sequence of follow-up emails, sent on schedule without me having to remember.

Post-delivery follow-up: canvas view of the real n8n workflow, 5 nodes. Daily Schedule Get Post-Delivery Records Build Post-Delivery Emails Send Post-Delivery Email Mark Email Sent
The real workflow, redrawn from n8n so it stays sharp on any screen. Every node is here.

The problem it solves

Delivery is not the end of the client relationship, but for most service businesses it accidentally becomes the end. Following up is easy to put off, and then it never happens.

How the pieces connect

The queue is built by the payment workflow. When a payment clears, it writes a post-delivery record to the database, and this workflow is the one that looks for it. The two do not call each other directly. They share a table, and this one runs on its own schedule.

The result is that every delivered client gets a follow-up without me remembering to send one. This is a Spark-size build: one scheduled trigger, one database check, the emails out and one record updated. Simple in structure, immediately useful.

How it runs

  1. 1

    Schedule

    Every morning

    The workflow runs on its own once a day.

  2. 2

    Check

    It checks the database

    It looks for clients whose project is delivered and whose payment is confirmed, with follow-ups still to send.

  3. 3

    Send

    The right email goes out

    When the support period ends: their options. After 14 days: a check-in. After 21 days: a gentle ask for a referral.

  4. 4

    Record

    Each email is marked as sent

    So every email goes out once per client, never twice.

What it connects

  • n8n

    Runs on a daily schedule and decides what is due.

  • Supabase

    Holds the queue of delivered clients and which emails were sent.

  • Email

    Sends the follow-ups in English or Dutch.