Include Ko-fi supporter context when planning a Linear project
Starting a project can bring supporter commitments into focus. Review relevant Ko-fi payment data as part of the planning workflow.
Trigger
Project Created
Fires when a new Linear project is created. Covers projects in both public and private teams — polls with the connected user's token, so visibility matches what the connected user can see in Linear.
Action
Receive Ko-fi payment webhook
Receives and validates Ko-fi payment webhook events. Use this to process real-time notifications for donations, subscriptions, commissions, and shop orders from Ko-fi. The webhook includes payment details, supporter information, and transaction metadata. Returns validated payment data to confirm receipt (Ko-fi expects 200 OK to prevent retries).
Why this helps
New project planning can overlook supporter context when donation and project information live in separate tools.
- Review available payment context during project planning.
- Keep supporter-related follow-up visible in a run report.
- Avoid claiming a connection when payment details do not identify the project.
Setup
Build it in a few focused steps.
- 1Connect Linear and Ko-fi once in the Notis portal.
- 2Create an automation in Automations, New Automation, or describe it to Notis from any channel.
- 3In one instruction, describe what Ko-fi payment context to review for a newly created project and how to report uncertain relevance.
- 4Pick the Project Created trigger and choose where run reports should go.
- 5Test with one real example and inspect the report.
Questions about this workflow
Can the automation tell which donations fund a project?
Only if the available payment details establish that relationship. Otherwise, the report should say the connection is unknown.
Does this work for private projects?
The Project Created event covers projects in public and private teams visible to the connected Linear user.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Ko fi. A trigger fires from one place; an action lands in another.
Linear triggers
Ko fi actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Receive Ko-fi payment webhook
Receives and validates Ko-fi payment webhook events. Use this to process real-time notifications for donations, subscriptions, commissions, and shop orders from Ko-fi. The webhook includes payment details, supporter information, and transaction metadata. Returns validated payment data to confirm receipt (Ko-fi expects 200 OK to prevent retries).
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Comment Received Trigger
Triggered when a comment is received.
Issue Created Trigger
Triggered when a new issue is created.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Connect any two apps with Notis in the middle.
Linear and Ko fi, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Ko fi.