The Real Problem
n8n workflow creators and automation agencies want to charge users per workflow execution (e.g. per report, lead enrichment, or data processing job), but embedding complex checkout flows inside webhook triggers requires custom DB tables and manual logic.
Real-World Example: For example, an n8n workflow for lead enrichment or PDF report creation can process input data after an HTTP 402 payment is verified.
How aipp Solves It
aipp provides an n8n monetization workflow pattern. Your n8n webhook trigger receives an incoming payload, queries aipp to check payment status (/invoice/status/:hash), and if unpaid, returns an HTTP 402 response with your Smart Tag link. When settled, execution proceeds.
Step-by-Step Payment Flow
STEP 01
Webhook Triggered
User or script posts data to n8n Webhook node.
STEP 02
Payment Check
n8n HTTP Request node queries aipp invoice status.
STEP 03
HTTP 402 Challenge
If unpaid, n8n responds HTTP 402 with aipp checkout link.
STEP 04
Workflow Executes
Once payment status = settled, n8n runs automation and returns result.
Scope & Boundaries
What aipp Does
- ✓ Provides machine-readable invoice verification endpoint for n8n nodes
- ✓ Generates payment pages for human workflow triggers
- ✓ Auto-forwards net merchant proceeds to your specified wallet
What aipp Does Not Do
- ✗ Does not host your n8n server or store your n8n workflow credentials
- ✗ Does not require maintaining a manual withdrawal balance
Implementation Pattern
Below is the minimal implementation pattern using standard aipp endpoints / SDK:
{
"nodes": [
{
"name": "Check aipp Settlement",
"type": "n8n-nodes-base.httpRequest",
"parameters": {
"url": "=https://aipp.dev/invoice/status/{{ $json.payment_hash }}",
"method": "GET"
}
}
]
}
Settlement Architecture Note:
• Lightning Rail: In hosted Lightning flows, payments route through aipp's Lightning gateway before net proceeds are automatically forwarded to your configured wallet address.
• Base USDC Rail: USDC transfers settle directly on-chain to your designated EVM wallet address.
• No Merchant Spending Balance: aipp does not maintain a spendable merchant balance or require manual withdrawal steps.
Requirements & Limitations
- aipp does not host or execute n8n engine itself; it provides the payment verification layer
- n8n workflow must use the HTTP Response node to return 402 headers
Frequently Asked Questions
Where do I get the n8n workflow template?
You can copy the ready-to-import JSON blueprint directly from the aipp open-source repository (examples/n8n_aipp_monetization_workflow.json).
Related Use Cases
Implement Paid n8n Workflow with aipp
Read the developer documentation or generate your API key to gate requests behind Lightning and Base USDC payments.