SVD OnlineSVD Online
EN|NL
← All workflows
Proposals and paymentsUses AI

Post-call document

The moment a discovery call ends, I trigger a workflow from my admin. Claude turns my notes into a structured document, with a deposit link ready to send.

Post-call document: canvas view of the real n8n workflow, 16 nodes. true false true Post-Call Webhook Build Post-Call Request Email Draft to Shoka Error: Send Alert Check Doc Type Create Mollie Deposit Link Store Payment Link Inject Payment Link Store Thinkover Build Email HTML Respond to Webhook Save Handover Notes Admin Copy: Agreement Email Was Sent Directly? Save Required Tools Call API
The real workflow, redrawn from n8n so it stays sharp on any screen. Every node is here.

The problem it solves

Every call ends with the same chain of manual work: write the document, create a payment link, store the details and email the client. Each step is small, and each one is easy to forget or get slightly wrong when you are busy.

Why I built it before I needed it

I built this before my first client call ever happened. I did not want the first time I used it to be the first time I worked out how it should behave.

Getting the output right took rounds of testing: running the workflow, reviewing what came back and adjusting the prompt until it matched what I actually needed. That is the part that takes time with AI-integrated workflows. The automation is rarely the hard part. Getting the output to be genuinely useful is.

Now it is ready. When the call happens, it runs.

How it runs

  1. 1

    Trigger

    I submit my call notes

    From my admin page, right after the call. That single action starts everything below.

  2. 2

    Type

    The workflow checks which document it is

    An agreement for someone who is ready to go, or a proposal for someone who needs time to think it over.

  3. 3

    Payment

    A deposit link is created

    For an agreement, a Mollie payment link for the deposit is generated, stored and placed inside the document. For a proposal, the think-over is stored instead.

  4. 4

    Draft

    Claude writes the document

    A structured summary of what was discussed, the problems described and the scope that came out of the call, turned into a ready-to-send email.

  5. 5

    Review

    The draft comes back to my admin

    I read it and adjust it before anything reaches the client.

  6. 6

    Prepare

    Handover details are saved

    Handover notes and the tools I will need access to are stored, ready for onboarding.

  7. 7

    Send

    A separate workflow sends it

    When I approve, a small send workflow emails the client and keeps a copy for me.

If something fails, an error alert reaches my inbox straight away. Nothing breaks quietly.

What it connects

  • n8n

    Runs the workflow and connects the other tools.

  • Claude API

    Turns my notes into the document.

  • Mollie

    Creates the deposit payment link.

  • Supabase

    Stores the payment link, handover notes and required tools.

Works well with

Proposals and paymentsPayment and invoicingTwo connected workflows run the full payment cycle: a payment link and invoice go out when a project is ready, and a paid payment turns into a receipt, a booked invoice and a follow-up.View workflow →
Leads and salesIntake formWhen someone applies, they get a confirmation within seconds, the application is logged, and I get a notification with everything I need to review it.View workflow →