Process Ko-fi Donations, Subscriptions, and Shop Orders with Webhook Verification - n8n Workflow

Content creators and streamers using Ko-fi for monetization.
Users requiring secure, verified webhook processing within an n8n workflow.
Automation specialists seeking reliable n8n templates for payment routing and data standardization.
Anyone needing to trigger specific downstream actions (like CRM updates or email automation) based on different Ko-fi transaction types.

This professional n8n workflow is designed to provide a secure and structured method for handling payment notifications from the Ko-fi platform. The primary value lies in its mandatory security verification step: every incoming webhook must pass a token check before the n8n workflow proceeds. This ensures the integrity and origin of the data. Once verified, the n8n automation efficiently routes the payment details—whether it's a simple donation, a recurring subscription payment, or a shop order—into standardized variables, making the data easily accessible for integration with third-party tools. Using this n8n template saves time and ensures consistent, reliable processing of all Ko-fi income events.

The n8n workflow initiates when the dedicated Webhook n8n node receives a POST request from Ko-fi, acting as the primary n8n trigger.

1. Preparation and Security: The flow moves to the Prepare n8n node, which defines the required verificationToken (which you must set up based on your Ko-fi settings) and extracts the payment details into a standardized body object.


2. Verification Check: The Check token n8n node (an If node) compares the token provided by Ko-fi in the payload against the required token. If the token does not match, the n8n workflow is halted immediately by the Stop and Error n8n node.


3. Type Routing: If verification succeeds, the Check type n8n node (a Switch node) inspects the type field (Donation, Subscription, or Shop Order) and directs the execution to the appropriate branch.


4. Data Extraction: Three parallel Set n8n nodes (Donation, Subscription, Shop Order) capture and standardize the relevant fields for each transaction type. For example, the Subscription path extracts the tiername and isfirstsubscriptionpayment data.


5. New Subscriber Logic: Finally, the Is new subscriber? n8n node further processes subscription events, using an If condition to detect if the payment marks the beginning of a new subscription. This allows you to easily tailor subsequent actions—the next steps in this n8n workflow—for welcoming first-time members.

To deploy this expert n8n workflow and start processing Ko-fi payments, follow these steps:

1. Import the n8n Template: Copy the provided JSON and import it into your n8n instance.


2. Configure the Webhook n8n Trigger: Click the Webhook n8n node and copy the URL path displayed (e.g., /webhook/83f4e1de-2011-487c-a9f7-be6ccbac0782).


3. Configure Ko-fi: Go to your Ko-fi Webhooks settings (https://ko-fi.com/manage/webhooks). Paste the n8n webhook URL into the designated field.


4. Set Verification Token: In the same Ko-fi settings page, find your verification token (often under 'Advanced Settings').


5. Update the Prepare n8n Node: Click the Prepare n8n node and replace the placeholder value for verificationToken with the actual token copied from Ko-fi. This is critical for the security of your n8n workflow.


6. Finalize: Enable the n8n workflow and test the connection from your Ko-fi settings page. You can then replace the final Set nodes with your desired automation logic.

Webhook (n8n trigger): Listens for incoming POST requests from Ko-fi. It provides the unique URL that links the Ko-fi payment system to this n8n automation.
Prepare (Set n8n node): Essential preparation step. It sets the secure, expected verificationToken and restructures the raw incoming data by moving the specific payment details from the Ko-fi wrapper (body.data) into the main workflow item as body.
Check token (If n8n node): Performs the necessary security check. It ensures the verificationtoken from the Ko-fi payload matches the token defined in the n8n workflow, protecting against unauthorized requests.
Check type (Switch n8n node): A powerful flow control mechanism that inspects the body.type field (Donation, Subscription, Shop Order) and routes the execution stream to the correct processing path within the n8n template.
Donation / Subscription / Shop Order (Set n8n node): Three distinct Set n8n nodes dedicated to extracting and naming specific fields relevant to each transaction type (e.g., amount, email, shopitems). This standardizes the data for further automation steps in the n8n workflow.
Is new subscriber? (If n8n node): Checks the boolean field isfirstsubscription_payment to filter only brand new subscribers, enabling specific welcome automations.