Connect LetSign to Make and your scenario drafts the proposal, the pricing options and the contract from the deal data you already track - then stages it for your review. Your client opens one link, picks a plan, signs and pays into your own Stripe.
Make does the orchestrating, LetSign does the contracting, Stripe does the collecting. You stay in the loop exactly once - at send time.
No SDK, no webhooks to hand-roll, no integration project. The whole setup is two connections and one scenario.
In your Make scenario, add the "MCP Client" app module and enter the LetSign remote MCP server URL. Make auto-loads the tools the server exposes, so LetSign's actions appear in the module right away. Authentication is OAuth or token, whichever you prefer - and because LetSign is hosted, the endpoint is already publicly reachable. You will find your MCP endpoint URL in the LetSign app at app.letsign.ai.
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.
Build the flow the way you would sketch it on a whiteboard. One proven outline:
1. Trigger: "Deal stage = Won" - your CRM module fires the moment a deal closes.
2. MCP Client: "LetSign: create proposal" - drafts the tiers and terms from the deal fields.
3. Human review: the proposal waits staged in LetSign until you read it and press send.
The scenario 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.
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.
Team standardized on a different automation platform? The same stack runs in n8n and Zapier. Prefer a conversational assistant over a canvas? There is a Claude playbook too.
One scenario run drafts the whole proposal with up to several plans your client can choose from - three tiers, optional add-ons, the works - straight from the deal fields in your CRM.
A scheduled scenario checks proposal status through the MCP: opened, plan picked, signed, paid - then routes the update to Slack, email or your CRM without you opening a dashboard.
Client asks for net-60 or a 10% discount? One MCP Client call updates the terms and restages the proposal for your review.
One-off invoices, subscriptions, or save-card-on-file - collected through your own Stripe account at signature time, not weeks later.
And everything Make does 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.
Through Make's MCP Client app module. Add the module to a scenario and enter the LetSign remote MCP server URL; Make auto-loads the tools the server exposes, so LetSign's actions are ready to use as module operations. Authentication is OAuth or a token, whichever you prefer, and because LetSign is hosted the endpoint is already publicly reachable.
No. The MCP Client module is configured in Make's visual scenario builder, not a config file. You connect Stripe once inside LetSign, then your scenario handles 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 scenario drafts and 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 the MCP Client module, connect Stripe, and let your scenario stage the next proposal for your review.
START LETSIGN FREE