The agent processes all Ko-fi webhook payment types: one-time donations (coffees), recurring memberships (subscriptions), shop purchases, and commission payments. Each type is identified through the webhook payload's 'type' field, and the agent can apply different logic to each payment category.

Ko-fi sends an HTTP POST request to a configured URL whenever a payment is made. You set this URL in your Ko-fi account settings under the webhook section. The Tars agent receives the payload containing supporter name, email, amount, currency, payment type, and any attached message, then acts on it in real time.

Yes. The Ko-fi webhook payload includes an is_first_subscription_payment field. The agent checks this flag to determine whether to trigger a welcome flow for new members or a renewal acknowledgment for existing subscribers. Each scenario can have completely different automated responses.

Yes. The webhook payload includes the supporter's email, name, and a unique transaction verification token. The agent uses this information to personalize responses, match supporters to existing records in your CRM or email list, and verify the authenticity of the webhook using the verification token.

Yes. When a shop purchase webhook arrives, the agent can parse the item details and trigger a delivery action, such as sending a download link, granting access to a members-only page, or adding the buyer to a specific email sequence. This works well for digital art packs, templates, e-books, and other downloadable products.

Ko-fi's API is currently webhook-only, meaning it sends payment events to you but does not support querying past transactions or managing your page settings via API. The agent processes events as they happen in real time. For historical data, you would still use Ko-fi's dashboard. The agent excels at real-time automation, not historical reporting.

Zapier triggers simple actions from Ko-fi events but cannot hold conversations. Tars processes the Ko-fi webhook and uses the data within an interactive AI conversation. Your agent can ask follow-up questions, personalize responses based on payment amount, and combine Ko-fi data with other tools in a single conversational flow.

Tars receives the webhook payload to process the event but does not store credit card numbers or financial details. Ko-fi handles all payment processing. The webhook contains supporter names, emails, amounts, and messages, which are handled according to your Tars data retention settings.