Log and route Ko-fi donations, subscriptions and orders

Every Ko-fi donation, subscription, or shop order is verified and automatically sorted by type as it comes in.

How the work actually flows

It branches. Exactly one path is taken.

Pattern: Exclusive Choice (4) · Simple Merge (5)

flowchart TD trig>"Ko-fi payment notification arrives"]:::trig s0["verify notification is genuine"]:::task s1["classify event type"]:::task s2[("record categorized event")]:::store trig --> s0 s0 --> s1 gx{"× what type of event"}:::gate s1 --> gx p00["match donation record"]:::task gx -->|"donation received"| p00 p10["match subscription record"]:::task gx -->|"subscription started"| p10 p20["match order record"]:::task gx -->|"shop order placed"| p20 jn{"○ logged as event"}:::gate p00 --> jn p10 --> jn p20 --> jn jn --> s2 out[/"verified categorized payment record"/]:::out pay{{"support income stays organized automatically"}}:::pay s2 --> out out --> pay classDef task fill:#e7f6fe,stroke:#34b8f0,color:#2c2a29 classDef svc fill:#f6f8fa,stroke:#7c8795,color:#2c2a29 classDef mi fill:#e7f6fe,stroke:#0079a8,color:#2c2a29,stroke-width:2px classDef human fill:#fff,stroke:#0079a8,color:#0079a8 classDef store fill:#f6f8fa,stroke:#0079a8,color:#2c2a29 classDef trig fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigtime fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigdata fill:#8ad4f5,stroke:#0079a8,color:#06314c,font-weight:bold classDef gate fill:#fff,stroke:#e8a23d,color:#6b4708,font-weight:bold classDef out fill:#1f9d6b,stroke:#167a53,color:#fff,font-weight:bold classDef pay fill:#06314c,stroke:#021f33,color:#fff
Starts itA stepA record or sheetOne path onlyPaths rejoinResultPayoff
Build size
Standard

A mid-size build with several tools working together.

Business functions
API & Webhook IntegrationFinance & Accounting
Connects
Ko-fi

The problem it solves

When support comes in through Ko-fi, donations, subscriptions, and shop orders all look the same until you open each one. Sorting through them by hand to figure out what happened and what needs a response wastes time you'd rather spend creating.

Who it fits

Content creators, artists, or developers who accept support through Ko-fi.

How it works

  1. A Ko-fi payment notification arrives
  2. The system checks that the notification is genuinely from Ko-fi
  3. It sorts the event into donation, subscription, or shop order
  4. The matching process runs automatically for that type
  5. You get a categorized record of exactly what came in
What you get

Ko-fi payments sorted the moment they arrive

Every Ko-fi donation, subscription, and shop order is verified and automatically sorted by type as soon as it comes in.

What you get

A verified, categorized record of each Ko-fi payment event.

What you need

A Ko-fi account with webhook access.

We can build this. But should you?

The hard question is not how to build it. It is whether this is the right thing to build first.

That is what a Fractional Chief AI Officer figures out with you, before anyone writes a line of code.

Let's Talk Strategy

Related automations

Announce new Ko-fi supporters automatically in Telegram

Posts a message in your Telegram channel every time someone donates or subscribes through Ko-fi.

Standard

Automatically manage new Patreon and Ko-fi supporters

Adds new Patreon and Ko-fi supporters to your newsletter and sends the right welcome message automatically.

Advanced

Read invoices from Gmail and log them to Google Sheets automatically

Pulls invoice attachments out of your inbox, reads the details with AI, and records them in a spreadsheet.

Advanced

Ask questions about your P&L and balance sheet with AI chat

Lets your finance team ask plain-English questions and get instant answers pulled straight from your financial data.

Standard
Back to the AI Playbook