Who is this for? This workflow is tailored for content creators, artists, and developers who use Ko-fi to receive financial support through donations, subscriptions, or product sales. Use case This workflow automates the process of receiving and categorizing payment notifications from Ko-fi, ensuring that creators can focus on their work rather than administrative tasks. What this workflow does Webhook Reception**: The workflow listens for incoming payment notifications from Ko-fi via a configured webhook. Token Verification**: It validates incoming requests to ensure they originate from Ko-fi using a verification token for enhanced security. Type Differentiation**: It categorizes payments into types—donations, subscriptions, and shop orders—allowing for tailored handling for each payment type. Custom Response Options**: Depending on the payment type received, the workflow activates specific actions or processes, enabling seamless integration with other applications or services. Setup Webhook Configuration: Access the Webhook node within the workflow and take note of your unique webhook URL. Visit your Ko-fi webhooks management page at Ko-fi Webhooks Management and input this URL.
Tags
Related workflows
See all General Automation→Handle Shopify Admin GraphQL requests with error handling and retries
Quick Overview This sub-workflow is called by another n8n workflow to execute Shopify Admin GraphQL queries and mutations via HTTP, adding input validation, detailed error detection (including rate limits), and automatic retries with exponential backoff before returning the final Shopify response. How it works Receives input from a parent workflow execution, including a Shopify GraphQL query, shop API endpoint, and Admin API access token. Validates required inputs, normalizes the shop endpoint, and builds the Shopify Admin GraphQL request payload with variables and API version defaults. Sends the POST request to the Shopify Admin GraphQL endpoint with the X-Shopify-Access-Token header and captures the full HTTP response. Parses the response to detect HTTP/network failures, GraphQL errors, Shopify userErrors, bulk/job failures, and throttle status from Shopify cost extensions. If throttled or encountering retryable server/network errors, waits for the calculated backoff interval and retries the same Shopify GraphQL request up to the configured maximum. If non-retryable errors remain, stops the execution and returns a formatted error object; otherwise returns the Shopify data, rate-l
Send personalized cold emails from Google Sheets with Claude MCP and Gmail
Quick overview This template turns a Google Sheet of leads into an outreach engine controlled by any MCP-compatible AI assistant, including Claude, ChatGPT,and others. Instead of manually drafting emails, you instruct the assistant to draft or send them through rotating Gmail accounts, while every action logs back to the sheet automatically How it works Receives a tool-call request from any MCP-capable assistant (Claude, ChatGPT, or others) via the MCP Server Trigger endpoint Reads all rows from a Google Sheets "Leads" tab so the assistant can find queued leads and avoid contacting anyone twice Creates a Gmail draft in one of several connected Gmail accounts, using the recipient, subject, and plain-text body the assistant provides Optionally sends the email immediately from one of the three Gmail accounts when the assistant provides the final recipient, subject, and body. Updates the matching row in Google Sheets with status, assigned account, sent date, and any error note, keeping the sheet as the single source of truth Setup Connect your Google Sheets OAuth credentials, then set the Spreadsheet document ID and the "Leads" sheet name in both the read and update nodes Connect Gmail
Generate llms.txt from a website sitemap using forms and HTTP requests
Quick overview This workflow uses an n8n Form and HTTP requests to read a website sitemap, fetch each listed page, extract the page title and meta description, and generate an llms.txt file that you can preview, copy, or download. How it works Receives a form submission with the site name, site description, sitemap URL, and a maximum page limit. Fetches the sitemap XML and, if it is a sitemap index, extracts the child sitemap URLs. Fetches each leaf sitemap and extracts, deduplicates, and caps page URLs while grouping them into sections based on the first URL path segment. Requests each page’s HTML content and continues even if some pages fail to load. Extracts the HTML title and meta description (or falls back to a title derived from the URL), then compiles the results into a sectioned llms.txt markdown file. Renders a completion page that displays the generated llms.txt content and provides Copy and Download actions. Setup Copy the n8n Form URL from the Form Trigger node and open it in your browser (or use the test form in the editor). Submit your site name, sitemap URL, and optionally a site description and max pages value. Upload the downloaded or copied llms.txt file to your w