自動販売
PLAYBOOK - N8N

Automate your sales with n8n.

Wire LetSign into n8n and an AI Agent node drafts the proposal, the pricing options and the contract straight from a workflow trigger - then stages it for your review. Your client opens one link, picks a plan, signs and pays into your own Stripe.

START LETSIGN FREE SEE PRICING
THE STACK

Five links in one chain.

n8n does the orchestrating, LetSign does the contracting, Stripe does the collecting. You stay in the loop exactly once - at send time.

THE STACK Triggerdeal hits Won AI Agent nodedrafts from deal notes LetSign MCPtools, not copy-paste Client signspicks a plan, verifies Stripe payoutyour Stripe, not ours One trigger in, one signed and paid contract out.
SETUP

From trigger to signed and paid, in five steps.

No SDK, no webhooks, no integration project. The whole setup is one node, one Stripe connection and one instruction.

1

Attach the MCP Client Tool node to an AI Agent node

In your n8n workflow, add an AI Agent node, then attach n8n's built-in "MCP Client Tool" node to it. In the node's settings, enter the LetSign MCP endpoint URL (you get it from app.letsign.ai), select the HTTP Streamable transport, and authenticate with a Bearer token or OAuth2. n8n loads LetSign's tools into the agent automatically - no custom code, no community package.

2

Connect your Stripe inside LetSign

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.

3

Give the agent node its instruction

The agent node's instruction text is where the selling happens. One proven instruction:

PROMPT

"When a deal reaches Won in the CRM, draft the proposal from the deal notes - three tiers, the middle one at the number in the deal record - and stage it for my review."

4

Review, then send

The workflow stages the proposal; nothing sends itself. You read it in LetSign, 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.

5

Your client picks a plan, signs and pays

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 Zaps to workflow canvases? The same stack runs in Zapier and in Make. Want a conversational assistant instead of a canvas? There is a Claude playbook too.

WHAT YOUR WORKFLOW CAN DO

Your workflow, now closing.

AUTHOR PROPOSALS

Conditional pricing, built in

The agent node 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 notes.

TRACK STATUS

Ask, and it knows

"Has Meridian signed yet?" A status step in any workflow reads proposal state through the MCP: opened, plan picked, signed, paid - without you opening a dashboard.

ADAPT TERMS

Renegotiate in one sentence

Client asks for net-60 or a 10% discount? One more run through the agent node updates the terms and restages the proposal for your review.

COLLECT PAYMENT

Your Stripe, your money

One-off invoices, subscriptions, or save-card-on-file - collected through your own Stripe account at signature time, not weeks later.

And everything the workflow 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 agent and you work on the same object, and neither is a second-class citizen.

FAQ

n8n questions, answered.

How does n8n talk to the LetSign MCP?

Through n8n's built-in MCP Client Tool node. You attach it to an AI Agent node, enter the LetSign MCP endpoint URL, select the HTTP Streamable transport and authenticate with a Bearer token or OAuth2. n8n loads the LetSign tools into the agent, and any workflow can call them.

Do I need to write code?

No. The MCP Client Tool node is configured in n8n's visual editor: an endpoint URL, a transport and a credential. You connect Stripe once inside LetSign, then the agent node does the drafting. And if you ever prefer to work by hand, every proposal and template is fully editable in the LetSign app.

What does LetSign cost?

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.

Who sends the contract?

You do. The agent node 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.

READY WHEN YOUR WORKFLOW IS

Your next contract is one trigger away.

Attach the node, connect Stripe, and let your workflow stage the next proposal for your review.

START LETSIGN FREE