Sync recurring subscription buyers to your custom storefront
When a new customer signs up in Stripe (Legacy), make a custom API request in KlimAPI to provision their store access instantly.
See all KlimAPI + Stripe (Legacy) integrations or talk to a human
Opens Claude with Knit filled in: click Continue. Claude web and desktop share one connector list. Or paste this link in Settings > Connectors > Add custom connector.
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents claude
Run in your own terminal, then restart Claude Code. Adds the server, the Knit skill and a CLAUDE.md note.
Turn on developer mode, then create a connector named Knit with this link and No Auth.
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents codex
Run in your own terminal (not through Codex), then start a new Codex session.
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents antigravity
Run in your own terminal, then reload MCP servers (/mcp in the CLI, refresh in the IDE).
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents cursor
Run in your own terminal, restart Cursor, then paste the note it prints into User Rules.
Google for Startups AcceleratorHow Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
KlimAPI Explore KlimAPI →
TriggersFires when a climate or offset order is processed in KlimAPI.
Funds tree planting through KlimAPI.
Estimates the carbon emissions of an activity with KlimAPI.
Buys a carbon offset through KlimAPI.
Stripe (Legacy) Explore Stripe (Legacy) →
TriggersFires when a new customer is created in Stripe (Legacy).
Fires when a subscription is canceled in Stripe (Legacy).
Fires when a new invoice is generated in Stripe (Legacy).
Fires when a payment attempt fails in Stripe (Legacy).
Creates a new customer in Stripe (Legacy).
Creates a new subscription in Stripe (Legacy).
Cancels an existing subscription in Stripe (Legacy).
Updates a customer's billing details in Stripe (Legacy).
More KlimAPI + Stripe (Legacy) workflows
See all KlimAPI + Stripe (Legacy) integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Sync recurring subscription buyers to your custom storefront” between KlimAPI and Stripe (Legacy)?
Yes — describe it in the box above and Knit's Integrations Agent researches KlimAPI and Stripe (Legacy)'s public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
Can new customer accounts in Stripe (Legacy) update storefront permissions in KlimAPI?
Yes, when a customer subscribes in Stripe (Legacy), you can issue a custom API request in KlimAPI to grant specific storefront privileges.
How does this integration handle affiliate commissions for recurring payments?
When recurring invoices are generated or payments fail in Stripe (Legacy), custom API requests can be sent to KlimAPI to accurately adjust affiliate earnings.