[ Payments ]
Ko-fi integration for your workflows.
Connect Ko-fi to Collabase once and use 0 actions and 4 triggers in your workflows. No code needed, hosted in Switzerland.
Ko-fi in Collabase
Connect Ko-fi to Collabase once and use 0 actions and 4 triggers in your workflows. No code needed, hosted in Switzerland.
[ About the service ]
Receive triggers for donations, subscriptions, commissions, and shop orders from Ko-fi.
How to connect it
- Open the integrations in the workspace settings.
- Choose Ko-fi and connect your account.
- Add a trigger or an action to the workflow.
Ko-fi triggers
| Name | Description | Fields |
|---|---|---|
| New DonationInstant via webhook | Triggers when a new one-time donation is received on Ko-fi. |
|
| New SubscriptionInstant via webhook | Triggers when a new subscription is received on Ko-fi. |
|
| New CommissionInstant via webhook | Triggers when a new commission is received on Ko-fi. |
|
| New Shop OrderInstant via webhook | Triggers when a new shop order is received on Ko-fi. |
|
Ko-fi actions
Ko-fi brings no actions, only triggers.
[ Payments ]
Related integrations
Tools that often share a workflow.
Questions about Ko-fi
What can I automate with Ko-fi in Collabase?
Ko-fi brings 4 triggers, for example New Donation, New Subscription, New Commission and 1 more. They start workflows whenever something happens in the service.
How do I connect Ko-fi to Collabase?
You open the integrations in the workspace settings, choose Ko-fi and connect your account once, using an API key. After that all triggers and actions are available in the workflow.
Can Ko-fi start a workflow?
Yes. Ko-fi provides 4 triggers, for example New Donation, New Subscription, New Commission and 1 more. The workflow runs as soon as the event happens.
Does the Ko-fi integration cost extra?
No. All integrations are included in every licence, in the Isolated Cloud and in Self-Hosted operation. There is no module price.
Test it against your own content. A proof of concept is ready within days.
We set up an instance with your content and you test it against real workflows. In a first conversation we clarify scope, operating model and timing.
