Connect LetSign to Zapier through the MCP Client by Zapier app - Zapier's MCP support, currently in beta - and a won deal can stage the proposal, the pricing options and the contract as a Zap action, ready for your review. Your client opens one link, picks a plan, signs and pays into your own Stripe.
Your Zap does the triggering, LetSign does the contracting, Stripe does the collecting. You stay in the loop exactly once - at send time.
No SDK, no webhooks to write, no integration project. The whole setup is two connections and one Zap.
In the Zap editor, add the "MCP Client by Zapier" app - this is how Zapier consumes MCP servers today, and it is in beta. Enter the LetSign remote MCP server URL (get it free at app.letsign.ai), pick the transport, and add an optional bearer token. Once connected, the LetSign server's tools become Zap actions you can drop into any Zap. Note the framing: this is a workflow-step integration through a beta client app, not a plain native Zapier integration.
In the LetSign app, connect your own Stripe account once. From then on every payment - one-off, subscription, or save-card-on-file - is collected through your Stripe and lands in your account. LetSign never holds your money.
Keep the shape simple: one trigger, one LetSign action, one human checkpoint. The proven outline:
Trigger: "Deal won" in your CRM → Action: "LetSign: create proposal" via MCP Client by Zapier (beta), mapping the deal fields to the tiers you discussed → Human review: you check the staged proposal in LetSign before anything goes out.
The Zap stages the proposal; nothing sends itself. You read it, tweak anything you like (a discount, net-60 terms, a different tier), and press send. The human send-gate is a feature, not a limitation - especially while Zapier's MCP support is in beta.
Your client opens one public link, chooses between the plans you offered (conditional pricing built in), verifies their email, signs a binding e-signature and pays through your Stripe - in a single sitting. Remember: the sender never signs. The client does.
Prefer a node-based automation canvas? The same stack runs in n8n and Make. Want a conversational agent instead of a workflow? There is a ChatGPT playbook too.
A deal-won trigger fires and the LetSign action drafts the whole proposal with up to several plans your client can choose from - three tiers, optional add-ons, the works - straight from your CRM fields.
A LetSign status action checks any proposal through the MCP: opened, plan picked, signed, paid - so later Zap steps can route on it without you opening a dashboard.
Client asks for net-60 or a 10% discount? Update the terms with a LetSign action or by hand in the app, and the proposal is restaged for your review before it goes back out.
One-off invoices, subscriptions, or save-card-on-file - collected through your own Stripe account at signature time, not weeks later.
And everything your Zaps do here, you can also do by hand. Every proposal, template and setting is fully editable in the LetSign app - full parity with the MCP. That two-way door is the essence of an agent-native contract: your automation and you work on the same object, and neither is a second-class citizen.
Not yet - it is in beta. Zapier consumes MCP servers through the MCP Client by Zapier app, a beta app: you enter the server URL, pick the transport and optionally add a bearer token, and the server's tools become Zap actions. It runs as a workflow step inside a Zap rather than as a fully agentic assistant, so treat it as beta and keep a human review step in the Zap.
No. MCP Client by Zapier is configured inside the Zap editor: paste the LetSign server URL, choose the transport and optionally add a bearer token. You connect Stripe once inside LetSign, then the Zap does the rest. And if you ever prefer to work by hand, every proposal and template is fully editable in the LetSign app.
The Free plan is $0 with a 0.20% fee on payments collected through it. The launch plan is $19 per month until October 1, 2026, and that price is locked until October 1, 2028; after launch the standard price is $49 per month. Paid plans pay 0% on payments up to $20,000 per month, then 0.05% above that.
You do. Your Zap stages the proposal, but nothing sends itself: a human reviews and presses send. And the sender never signs. Your client opens the link, picks a plan, verifies their email, signs a binding e-signature and pays through your Stripe.
Add MCP Client by Zapier (beta), connect Stripe, and let your Zap stage the next proposal for your review.
START LETSIGN FREE