Send payment recovery emails for failed charges
When a payment fails in Stripe (Legacy), automatically send a transactional email via MailerCheck guiding the customer to update their payment details.
See all MailerCheck + 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.
MailerCheck Explore MailerCheck →
TriggersFires when a list or bulk verification job finishes in MailerCheck.
Checks whether an email address is valid and deliverable with MailerCheck.
Runs a bulk verification on a list of addresses in MailerCheck.
Returns the remaining verification credits in MailerCheck.
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 MailerCheck + Stripe (Legacy) workflows
See all MailerCheck + Stripe (Legacy) integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Send payment recovery emails for failed charges” between MailerCheck and Stripe (Legacy)?
Yes — describe it in the box above and Knit's Integrations Agent researches MailerCheck 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.
How does connecting MailerCheck and Stripe (Legacy) help reduce subscriber churn?
When payment failures or subscription cancellations happen in Stripe (Legacy), automated workflows can immediately route customers into targeted re-engagement or recovery email sequences in MailerCheck.
Can subscriber preference updates in MailerCheck reflect in Stripe (Legacy)?
Yes, when contacts unsubscribe or update preferences in MailerCheck, workflows can automatically update their customer profile in Stripe (Legacy) to maintain consistent communication preferences.