Workflow Templates

📝 Description This workflow allows you to extract all links (URLs) contained in a PDF file by converting it to HTML via PDF.co and then extracting the URLs present in the resulting HTML. Unlike the traditional Read PDF node, which only returns visible link text, this flow provides the full active URLs, making further processing and analysis easier. 📌 Use Cases Extract all hyperlinks from PDF documents. Automate URL verification and monitoring within documents. Extract links from reports, contracts, catalogs, newsletters, or manuals. Prepare URLs for validation, classification, or storage. 🔗 Workflow Overview User uploads a PDF file via a web form. The PDF is uploaded to PDF.co. The PDF is converted to HTML (preserving links). The converted HTML is downloaded. URLs are extracted from the HTML using a custom code node. ⚙️ Node Breakdown 1. Load PDF (formTrigger) Uploads a .pdf file. Single file upload. 2. Upload (PDF.co API) Uploads the PDF file to PDF.co using binary data. 3. PDF to HTML (PDF.co API) Converts the uploaded PDF to HTML using its URL. 4. Get HTML (HTTP Request) Downloads the converted HTML from PDF.co. 5. Code1 (Function / Code) Parses the HTML content to extract all URLs (http, https, www). Uses a regex to identify URLs within the HTML text. Outputs an array of objects containing the extracted URLs. 📎 Requirements Active PDF.co account with API key. Set up PDF.co credentials in n8n (PDF.co account). Enable webhook to expose the upload form. 🛠️ Suggested Next Steps Add nodes to validate extracted URLs (e.g., HTTP requests to check status). Store URLs in a database, spreadsheet, or send via email. Extend the flow to filter URLs by domain, type, or pattern. 📤 Importing the Template Import this workflow into n8n via Import workflow and paste the provided JSON. If you want help adding extra steps or optimizing the URL extraction, just ask! If you want, I can also prepare this as a Canva visual template for you. Would you like that?

AgentGatePay N8N Quick Start Guide Get your AI agents paying for resources autonomously in under 10 minutes. > ⚠️ BETA VERSION: These templates are currently in beta. We're actively adding features and improvements based on user feedback. Expect updates for enhanced functionality, additional blockchain networks, and new payment options. What You'll Build Buyer Agent: Automatically pays for API resources using **USDC, USDT, or DAI on Ethereum, Base, Polygon, or Arbitrum blockchains Seller API**: Accepts multi-token payments and delivers resources Monitoring**: Track spending and revenue in real-time across all chains and tokens Supported Tokens: USDC (6 decimals) - Recommended USDT (6 decimals) DAI (18 decimals) Supported Blockchains: Ethereum (mainnet) Base (recommended for low gas fees ~$0.001) Polygon Arbitrum Prerequisites (5 minutes) 1. Create AgentGatePay Accounts Buyer Account (agent that pays): curl -X POST https://api.agentgatepay.com/v1/users/signup \ -H "Content-Type: application/json" \ -d '{ "email": "buyer@example.com", "password": "SecurePass123!", "user_type": "agent" }' Seller Account (receives payments): curl -X POST https://api.agentgatepay.com/v1/users/signup \ -H "Content-Type: application/json" \ -d '{ "email": "seller@example.com", "password": "SecurePass123!", "user_type": "merchant" }' Save both API keys - shown only once! 2. Deploy Transaction Signing Service (2 minutes) One-Click Render Deploy: Click: Enter: AGENTGATEPAY_API_KEY: Your buyer API key WALLET_PRIVATE_KEY: Your wallet private key (0x...) Deploy → Copy service URL: https://your-app.onrender.com 3. Fund Wallet Send USDC, USDT, or DAI to your buyer wallet Default: Base network (lowest gas fees) Need $1 in tokens for testing + $0.01 ETH for gas (on Ethereum) or ~$0.001 on Base Installation (3 minutes) Step 1: Import Templates In N8N: Go to Workflows → Add Workflow Click ⋮ (three dots) → Import from File Import all 3 workflows: 🤖 Create a Cryptocurrency-Powered API for Selling Digital Resources with AgentGatePay 💲Create a Cryptocurrency-Powered API for Selling Digital Resources with AgentGatePay 📊 AgentGatePay - Monitoring Dashboard Step 2: Create Data Table In N8N Settings: Go to Settings → Data → Data Tables Create table: AgentPay_Mandates Add column: mandate_token (type: String) Save Configuration (2 minutes) Configure Seller API First Open: 💲Seller Resource API - CLIENT TEMPLATE Edit Node 1 (Parse Request): const SELLER_CONFIG = { merchant: { wallet_address: "0xYourSellerWallet...", // ← Your seller wallet api_key: "pk_live_xyz789..." // ← Your seller API key }, catalog: { "demo-resource": { id: "demo-resource", price_usd: 0.01, // $0.01 per resource description: "Demo API Resource" } } }; Activate workflow → Copy webhook URL Configure Buyer Agent Open: 🤖 Buyer Agent - CLIENT TEMPLATE Edit Node 1 (Load Config): const CONFIG = { buyer: { email: "buyer@example.com", // ← Your buyer email api_key: "pk_live_abc123...", // ← Your buyer API key budget_usd: 100, // $100 mandate budget mandate_ttl_days: 7 // 7-day validity }, seller: { api_url: "https://YOUR-N8N.app.n8n.cloud/webhook/YOUR-WEBHOOK-ID" // ← Seller webhook base URL ONLY (see README.md for extraction instructions) }, render: { service_url: "https://your-app.onrender.com" // ← Your Render URL } }; Run Your First Payment (1 minute) Execute Buyer Agent Open Buyer Agent workflow Click Execute Workflow Watch the magic happen: Mandate created ($100 budget) Resource requested (402 Payment Required) Payment signed (2 transactions: merchant + commission) Payment verified on blockchain Resource delivered Total time: ~5-8 seconds Verify on Blockchain Check transactions on BaseScan: https://basescan.org/address/YOUR_BUYER_WALLET You'll see: TX 1:** Commission to AgentGatePay (0.5% = $0.00005) TX 2:** Payment to seller (99.5% = $0.00995) Monitor Activity - Choose Buyer/Seller or both Buyer Monitoring Open: 📊 AgentGatePay - Monitoring Dashboard Edit Node 1: Set your buyer wallet address and API key Execute → See: Mandate budget remaining Payment history Total spent Average transaction size Seller Monitoring Open: 📊 AgentGatePay - Monitoring Dashboard Edit Node 1: Set your seller wallet address and API key Execute → See: Total revenue Commission breakdown Top payers Payment count How It Works Payment Flow Buyer Agent requests resource ↓ Seller returns 402 Payment Required (includes: wallet address, price, token, chain) ↓ Buyer signs TWO blockchain transactions via Render: Merchant payment (99.5%) Gateway commission (0.5%) ↓ Buyer resubmits request with transaction hashes ↓ Seller verifies payment with AgentGatePay API ↓ Seller delivers resource Key Concepts AP2 Mandate: Pre-authorized spending authority Budget limit ($100 in example) Time limit (7 days in example) Stored in N8N Data Table for reuse x402 Protocol: HTTP 402 "Payment Required" status code Seller specifies payment details Buyer pays and retries with proof Two-Transaction Model: Transaction 1: Merchant receives 99.5% Transaction 2: Gateway receives 0.5% Both verified on blockchain Customization Change Resource Price Edit seller Node 1: catalog: { "expensive-api": { id: "expensive-api", price_usd: 1.00, // ← Change price description: "Premium API access" } } Add More Resources catalog: { "basic": { id: "basic", price_usd: 0.01, description: "Basic API" }, "pro": { id: "pro", price_usd: 0.10, description: "Pro API" }, "enterprise": { id: "enterprise", price_usd: 1.00, description: "Enterprise API" } } Buyer requests by ID: ?resource_id=pro Change Blockchain and Token By default, templates use Base + USDC. To change: Edit buyer Node 1 (Load Config): const CONFIG = { buyer: { /* ... */ }, seller: { /* ... */ }, render: { /* ... */ }, payment: { chain: "polygon", // Options: ethereum, base, polygon, arbitrum token: "DAI" // Options: USDC, USDT, DAI } }; Important: Ensure your wallet has the selected token on the selected chain Update Render service to support the chain (add RPC URL) Gas fees vary by chain. Token Decimals: USDC/USDT: 6 decimals (automatic conversion) DAI: 18 decimals (automatic conversion) Schedule Monitoring Replace "Execute Workflow" trigger with Schedule Trigger: Buyer monitoring: Every 1 hour Seller monitoring: Every 6 hours Add Slack/Email node to send alerts. Troubleshooting "Mandate expired" Fix: Delete mandate from Data Table → Re-execute workflow "Transaction not found" Fix: Wait 10-15 seconds for blockchain confirmation → Retry "Render service unavailable" Fix: Render free tier spins down after 15 min → First request takes ~5 sec (cold start) "Insufficient funds" Fix: Send more tokens (USDC/USDT/DAI) to buyer wallet Check balance on blockchain explorer (BaseScan for Base, Etherscan for Ethereum, etc.) "Webhook not responding" Fix: Ensure seller workflow is Active (toggle in top-right) Production Checklist Before going live: [ ] Use separate wallet for agent (not your main wallet) [ ] Set conservative mandate budgets ($10-100) [ ] Monitor spending daily (use monitoring workflows) [ ] Upgrade Render to paid tier ($7/mo) for no cold starts [ ] Set up Slack/email alerts for low balance [ ] Test with small amounts first ($0.01-0.10) [ ] Keep API keys secure (use N8N credentials manager) [ ] Review transactions on blockchain explorer weekly Summary You just built: Autonomous payment agent (buys resources automatically) Monetized API (sells resources for USDC, USDT, or DAI) Multi-chain support** (Ethereum, Base, Polygon, Arbitrum) Real blockchain transactions (verified on-chain) Budget management (AP2 mandates) Monitoring dashboard (track spending/revenue) Total setup time: ~10 minutes Total cost: $0 (Render free tier + AgentGatePay free) Ready to scale? Connect multiple agents, add more resources, integrate with your existing systems! Questions? Check README.md or contact support@agentgatepay.com Website: https://www.agentgatepay.com

AgentGatePay N8N Quick Start Guide Get your AI agents paying for resources autonomously in under 10 minutes. > ⚠️ BETA VERSION: These templates are currently in beta. We're actively adding features and improvements based on user feedback. Expect updates for enhanced functionality, additional blockchain networks, and new payment options. What You'll Build Buyer Agent: Automatically pays for API resources using **USDC, USDT, or DAI on Ethereum, Base, Polygon, or Arbitrum blockchains Seller API**: Accepts multi-token payments and delivers resources Monitoring**: Track spending and revenue in real-time across all chains and tokens Supported Tokens: USDC (6 decimals) - Recommended USDT (6 decimals) DAI (18 decimals) Supported Blockchains: Ethereum (mainnet) Base (recommended for low gas fees ~$0.001) Polygon Arbitrum Prerequisites (5 minutes) 1. Create AgentGatePay Accounts Buyer Account (agent that pays): curl -X POST https://api.agentgatepay.com/v1/users/signup \ -H "Content-Type: application/json" \ -d '{ "email": "buyer@example.com", "password": "SecurePass123!", "user_type": "agent" }' Seller Account (receives payments): curl -X POST https://api.agentgatepay.com/v1/users/signup \ -H "Content-Type: application/json" \ -d '{ "email": "seller@example.com", "password": "SecurePass123!", "user_type": "merchant" }' Save both API keys - shown only once! 2. Deploy Transaction Signing Service (2 minutes) One-Click Render Deploy: Click: Enter: AGENTGATEPAY_API_KEY: Your buyer API key WALLET_PRIVATE_KEY: Your wallet private key (0x...) Deploy → Copy service URL: https://your-app.onrender.com 3. Fund Wallet Send USDC, USDT, or DAI to your buyer wallet Default: Base network (lowest gas fees) Need $1 in tokens for testing + $0.01 ETH for gas (on Ethereum) or ~$0.001 on Base Installation (3 minutes) Step 1: Import Templates In N8N: Go to Workflows → Add Workflow Click ⋮ (three dots) → Import from File Import all 4 workflows: 🤖 Create a Cryptocurrency-Powered API for Selling Digital Resources with AgentGatePay 💲Create a Cryptocurrency-Powered API for Selling Digital Resources with AgentGatePay 📊 Buyer Agent [Monitoring] - AgentGatePay Autonomous Payment Workflow 💲 Seller Agent [Monitoring] - AgentGatePay Autonomous Payment Workflow Step 2: Create Data Table In N8N Settings: Go to Settings → Data → Data Tables Create table: AgentPay_Mandates Add column: mandate_token (type: String) Save Configuration (2 minutes) Configure Seller API First Open: 💲Seller Resource API - CLIENT TEMPLATE Edit Node 1 (Parse Request): const SELLER_CONFIG = { merchant: { wallet_address: "0xYourSellerWallet...", // ← Your seller wallet api_key: "pk_live_xyz789..." // ← Your seller API key }, catalog: { "demo-resource": { id: "demo-resource", price_usd: 0.01, // $0.01 per resource description: "Demo API Resource" } } }; Activate workflow → Copy webhook URL Configure Buyer Agent Open: 🤖 Buyer Agent - CLIENT TEMPLATE Edit Node 1 (Load Config): const CONFIG = { buyer: { email: "buyer@example.com", // ← Your buyer email api_key: "pk_live_abc123...", // ← Your buyer API key budget_usd: 100, // $100 mandate budget mandate_ttl_days: 7 // 7-day validity }, seller: { api_url: "https://YOUR-N8N.app.n8n.cloud/webhook/YOUR-WEBHOOK-ID" // ← Seller webhook base URL ONLY (see README.md for extraction instructions) }, render: { service_url: "https://your-app.onrender.com" // ← Your Render URL } }; Run Your First Payment (1 minute) Execute Buyer Agent Open Buyer Agent workflow Click Execute Workflow Watch the magic happen: Mandate created ($100 budget) Resource requested (402 Payment Required) Payment signed (2 transactions: merchant + commission) Payment verified on blockchain Resource delivered Total time: ~5-8 seconds Verify on Blockchain Check transactions on BaseScan: https://basescan.org/address/YOUR_BUYER_WALLET You'll see: TX 1:** Commission to AgentGatePay (0.5% = $0.00005) TX 2:** Payment to seller (99.5% = $0.00995) Monitor Activity Buyer Monitoring Open: 📊 Buyer Monitoring - AUDIT LOGS Edit Node 1: Set your buyer wallet address and API key Execute → See: Mandate budget remaining Payment history Total spent Average transaction size Seller Monitoring Open: 💲 Seller Monitoring - AUDIT LOGS Edit Node 1: Set your seller wallet address and API key Execute → See: Total revenue Commission breakdown Top payers Payment count How It Works Payment Flow Buyer Agent requests resource ↓ Seller returns 402 Payment Required (includes: wallet address, price, token, chain) ↓ Buyer signs TWO blockchain transactions via Render: Merchant payment (99.5%) Gateway commission (0.5%) ↓ Buyer resubmits request with transaction hashes ↓ Seller verifies payment with AgentGatePay API ↓ Seller delivers resource Key Concepts AP2 Mandate: Pre-authorized spending authority Budget limit ($100 in example) Time limit (7 days in example) Stored in N8N Data Table for reuse x402 Protocol: HTTP 402 "Payment Required" status code Seller specifies payment details Buyer pays and retries with proof Two-Transaction Model: Transaction 1: Merchant receives 99.5% Transaction 2: Gateway receives 0.5% Both verified on blockchain Customization Change Resource Price Edit seller Node 1: catalog: { "expensive-api": { id: "expensive-api", price_usd: 1.00, // ← Change price description: "Premium API access" } } Add More Resources catalog: { "basic": { id: "basic", price_usd: 0.01, description: "Basic API" }, "pro": { id: "pro", price_usd: 0.10, description: "Pro API" }, "enterprise": { id: "enterprise", price_usd: 1.00, description: "Enterprise API" } } Buyer requests by ID: ?resource_id=pro Change Blockchain and Token By default, templates use Base + USDC. To change: Edit buyer Node 1 (Load Config): const CONFIG = { buyer: { /* ... */ }, seller: { /* ... */ }, render: { /* ... */ }, payment: { chain: "polygon", // Options: ethereum, base, polygon, arbitrum token: "DAI" // Options: USDC, USDT, DAI } }; Important: Ensure your wallet has the selected token on the selected chain Update Render service to support the chain (add RPC URL) Gas fees vary by chain. Token Decimals: USDC/USDT: 6 decimals (automatic conversion) DAI: 18 decimals (automatic conversion) Schedule Monitoring Replace "Execute Workflow" trigger with Schedule Trigger: Buyer monitoring: Every 1 hour Seller monitoring: Every 6 hours Add Slack/Email node to send alerts. Troubleshooting "Mandate expired" Fix: Delete mandate from Data Table → Re-execute workflow "Transaction not found" Fix: Wait 10-15 seconds for blockchain confirmation → Retry "Render service unavailable" Fix: Render free tier spins down after 15 min → First request takes ~5 sec (cold start) "Insufficient funds" Fix: Send more tokens (USDC/USDT/DAI) to buyer wallet Check balance on blockchain explorer (BaseScan for Base, Etherscan for Ethereum, etc.) "Webhook not responding" Fix: Ensure seller workflow is Active (toggle in top-right) Production Checklist Before going live: [ ] Use separate wallet for agent (not your main wallet) [ ] Set conservative mandate budgets ($10-100) [ ] Monitor spending daily (use monitoring workflows) [ ] Upgrade Render to paid tier ($7/mo) for no cold starts [ ] Set up Slack/email alerts for low balance [ ] Test with small amounts first ($0.01-0.10) [ ] Keep API keys secure (use N8N credentials manager) [ ] Review transactions on blockchain explorer weekly Summary You just built: Autonomous payment agent (buys resources automatically) Monetized API (sells resources for USDC, USDT, or DAI) Multi-chain support** (Ethereum, Base, Polygon, Arbitrum) Real blockchain transactions (verified on-chain) Budget management (AP2 mandates) Monitoring dashboard (track spending/revenue) Total setup time: ~10 minutes Total cost: $0 (Render free tier + AgentGatePay free) Ready to scale? Connect multiple agents, add more resources, integrate with your existing systems! Questions? Check README.md or contact support@agentgatepay.com Website: https://www.agentgatepay.com

How It Works: The 5-Node Security Flow This workflow efficiently performs a scheduled file integrity audit. 1. Scheduled Check (Cron Node) This is the workflow's trigger. It schedules the workflow to run at a specific, regular interval. Function:** Continuously runs on a set schedule, for example, daily at 3:00 AM. Process:** The Cron node automatically initiates the workflow on its schedule, ensuring consistent file integrity checks without manual intervention. 2. List Files & Checksums (Code Node) This node acts as your static database, defining which files to monitor and their known-good checksums. Function:** Stores the file paths and their verified checksums in a single, easy-to-update array. Process:** It configures the file paths and their valid checksums, which are then passed on to subsequent nodes for processing. 3. Get Remote File Checksum (SSH Node) This node connects to your remote server to get the current checksum of the file being monitored. Function:** Executes a command on your server via SSH. Process:** It runs a command like sha256sum /path/to/file on the server. The current checksum is then captured and passed to the next node for comparison. 4. Checksums Match? (If Node) This is the core detection logic. It compares the newly retrieved checksum from the server with the known-good checksum you stored. Function:** Compares the two checksum values. Process:* If the checksums *do not match**, it indicates a change in the file, and the workflow is routed to the notification node. If they do match, the workflow ends safely. 5. Send Alert (Slack Node) / End Workflow (No-Op Node) These nodes represent the final action of the workflow. Function:** Responds to a detected file change. Process:* If the checksums don't match, the *Slack* node sends a detailed alert with information about the modified file, the expected checksum, and the detected checksum. If the checksums match, the *No-Op** node ends the workflow without any notification. How to Set Up Implementing this essential cybersecurity monitor in your n8n instance is quick and straightforward. 1. Prepare Your Credentials & Server Before building the workflow, ensure all necessary accounts are set up and their credentials are ready. SSH Credential:* Set up an *SSH credential** in n8n with your server's hostname, port, and authentication method (e.g., private key or password). The SSH user must have permission to run sha256sum on the files you want to monitor. Slack Credential:* Set up a *Slack credential* in n8n and note the *Channel ID** of your security alert channel (e.g., #security-alerts). Get Checksums:* *This is a critical step.** Manually run the sha256sum [file_path] command on your server for each file you want to monitor. Copy and save the generated checksum values—these are the "known-good" checksums you will use as your reference. 2. Import the Workflow JSON Get the workflow structure into your n8n instance. Import:** In your n8n instance, navigate to the "Workflows" section. Click the "New" or "+" icon, then select "Import from JSON." Paste the provided JSON code into the import dialog and import the workflow. 3. Configure the Nodes Customize the imported workflow to fit your specific monitoring needs. Scheduled Check (Cron):** Set the schedule according to your preference (e.g., daily at 3:00 AM). List Files & Checksums (Code):* Open this node and *edit the filesToCheck array**. Enter your actual server file paths and paste the "known-good" checksums you manually obtained in step 1. Get Remote File Checksum (SSH):* Select your *SSH credential**. Send Alert (Slack):* Select your *Slack credential* and replace YOUR_SECURITY_ALERT_CHANNEL_ID with your actual *Channel ID**. 4. Test and Activate Verify that your workflow is working correctly before setting it live. Manual Test:** Run the workflow manually. Verify that it connects to the server and checks the files without sending an alert (assuming the files haven't changed). Verify:** To test the alert, manually change one of the files on your server and run the workflow again. Check your Slack channel to ensure the alert is sent correctly. Activate:** Once you're confident in its function, activate the workflow. n8n will now automatically audit the integrity of your critical files on the schedule you set.

AgentGatePay N8N Quick Start Guide Get your AI agents paying for resources autonomously in under 10 minutes. > ⚠️ BETA VERSION: These templates are currently in beta. We're actively adding features and improvements based on user feedback. Expect updates for enhanced functionality, additional blockchain networks, and new payment options. What You'll Build Buyer Agent: Automatically pays for API resources using **USDC, USDT, or DAI on Ethereum, Base, Polygon, or Arbitrum blockchains Seller API**: Accepts multi-token payments and delivers resources Monitoring**: Track spending and revenue in real-time across all chains and tokens Supported Tokens: USDC (6 decimals) - Recommended USDT (6 decimals) DAI (18 decimals) Supported Blockchains: Ethereum (mainnet) Base (recommended for low gas fees ~$0.001) Polygon Arbitrum Prerequisites (5 minutes) 1. Create AgentGatePay Accounts Buyer Account (agent that pays): curl -X POST https://api.agentgatepay.com/v1/users/signup \ -H "Content-Type: application/json" \ -d '{ "email": "buyer@example.com", "password": "SecurePass123!", "user_type": "agent" }' Seller Account (receives payments): curl -X POST https://api.agentgatepay.com/v1/users/signup \ -H "Content-Type: application/json" \ -d '{ "email": "seller@example.com", "password": "SecurePass123!", "user_type": "merchant" }' Save both API keys - shown only once! 2. Deploy Transaction Signing Service (2 minutes) One-Click Render Deploy: Click: Enter: AGENTGATEPAY_API_KEY: Your buyer API key WALLET_PRIVATE_KEY: Your wallet private key (0x...) Deploy → Copy service URL: https://your-app.onrender.com 3. Fund Wallet Send USDC, USDT, or DAI to your buyer wallet Default: Base network (lowest gas fees) Need $1 in tokens for testing + $0.01 ETH for gas (on Ethereum) or ~$0.001 on Base Installation (3 minutes) Step 1: Import Templates In N8N: Go to Workflows → Add Workflow Click ⋮ (three dots) → Import from File Import all 3 workflows: 🤖 Create a Cryptocurrency-Powered API for Selling Digital Resources with AgentGatePay 💲Create a Cryptocurrency-Powered API for Selling Digital Resources with AgentGatePay 📊 AgentGatePay - Monitoring Dashboard Step 2: Create Data Table In N8N Settings: Go to Settings → Data → Data Tables Create table: AgentPay_Mandates Add column: mandate_token (type: String) Save Configuration (2 minutes) Configure Seller API First Open: 💲Seller Resource API - CLIENT TEMPLATE Edit Node 1 (Parse Request): const SELLER_CONFIG = { merchant: { wallet_address: "0xYourSellerWallet...", // ← Your seller wallet api_key: "pk_live_xyz789..." // ← Your seller API key }, catalog: { "demo-resource": { id: "demo-resource", price_usd: 0.01, // $0.01 per resource description: "Demo API Resource" } } }; Activate workflow → Copy webhook URL Configure Buyer Agent Open: 🤖 Buyer Agent - CLIENT TEMPLATE Edit Node 1 (Load Config): const CONFIG = { buyer: { email: "buyer@example.com", // ← Your buyer email api_key: "pk_live_abc123...", // ← Your buyer API key budget_usd: 100, // $100 mandate budget mandate_ttl_days: 7 // 7-day validity }, seller: { api_url: "https://YOUR-N8N.app.n8n.cloud/webhook/YOUR-WEBHOOK-ID" // ← Seller webhook base URL ONLY (see README.md for extraction instructions) }, render: { service_url: "https://your-app.onrender.com" // ← Your Render URL } }; Run Your First Payment (1 minute) Execute Buyer Agent Open Buyer Agent workflow Click Execute Workflow Watch the magic happen: Mandate created ($100 budget) Resource requested (402 Payment Required) Payment signed (2 transactions: merchant + commission) Payment verified on blockchain Resource delivered Total time: ~5-8 seconds Verify on Blockchain Check transactions on BaseScan: https://basescan.org/address/YOUR_BUYER_WALLET You'll see: TX 1:** Commission to AgentGatePay (0.5% = $0.00005) TX 2:** Payment to seller (99.5% = $0.00995) Monitor Activity - Choose Buyer/Seller or both Buyer Monitoring Open: 📊 AgentGatePay - Monitoring Dashboard Edit Node 1: Set your buyer wallet address and API key Execute → See: Mandate budget remaining Payment history Total spent Average transaction size Seller Monitoring Open: 📊 AgentGatePay - Monitoring Dashboard Edit Node 1: Set your seller wallet address and API key Execute → See: Total revenue Commission breakdown Top payers Payment count How It Works Payment Flow Buyer Agent requests resource ↓ Seller returns 402 Payment Required (includes: wallet address, price, token, chain) ↓ Buyer signs TWO blockchain transactions via Render: Merchant payment (99.5%) Gateway commission (0.5%) ↓ Buyer resubmits request with transaction hashes ↓ Seller verifies payment with AgentGatePay API ↓ Seller delivers resource Key Concepts AP2 Mandate: Pre-authorized spending authority Budget limit ($100 in example) Time limit (7 days in example) Stored in N8N Data Table for reuse x402 Protocol: HTTP 402 "Payment Required" status code Seller specifies payment details Buyer pays and retries with proof Two-Transaction Model: Transaction 1: Merchant receives 99.5% Transaction 2: Gateway receives 0.5% Both verified on blockchain Customization Change Resource Price Edit seller Node 1: catalog: { "expensive-api": { id: "expensive-api", price_usd: 1.00, // ← Change price description: "Premium API access" } } Add More Resources catalog: { "basic": { id: "basic", price_usd: 0.01, description: "Basic API" }, "pro": { id: "pro", price_usd: 0.10, description: "Pro API" }, "enterprise": { id: "enterprise", price_usd: 1.00, description: "Enterprise API" } } Buyer requests by ID: ?resource_id=pro Change Blockchain and Token By default, templates use Base + USDC. To change: Edit buyer Node 1 (Load Config): const CONFIG = { buyer: { /* ... */ }, seller: { /* ... */ }, render: { /* ... */ }, payment: { chain: "polygon", // Options: ethereum, base, polygon, arbitrum token: "DAI" // Options: USDC, USDT, DAI } }; Important: Ensure your wallet has the selected token on the selected chain Update Render service to support the chain (add RPC URL) Gas fees vary by chain. Token Decimals: USDC/USDT: 6 decimals (automatic conversion) DAI: 18 decimals (automatic conversion) Schedule Monitoring Replace "Execute Workflow" trigger with Schedule Trigger: Buyer monitoring: Every 1 hour Seller monitoring: Every 6 hours Add Slack/Email node to send alerts. Troubleshooting "Mandate expired" Fix: Delete mandate from Data Table → Re-execute workflow "Transaction not found" Fix: Wait 10-15 seconds for blockchain confirmation → Retry "Render service unavailable" Fix: Render free tier spins down after 15 min → First request takes ~5 sec (cold start) "Insufficient funds" Fix: Send more tokens (USDC/USDT/DAI) to buyer wallet Check balance on blockchain explorer (BaseScan for Base, Etherscan for Ethereum, etc.) "Webhook not responding" Fix: Ensure seller workflow is Active (toggle in top-right) Production Checklist Before going live: [ ] Use separate wallet for agent (not your main wallet) [ ] Set conservative mandate budgets ($10-100) [ ] Monitor spending daily (use monitoring workflows) [ ] Upgrade Render to paid tier ($7/mo) for no cold starts [ ] Set up Slack/email alerts for low balance [ ] Test with small amounts first ($0.01-0.10) [ ] Keep API keys secure (use N8N credentials manager) [ ] Review transactions on blockchain explorer weekly Summary You just built: Autonomous payment agent (buys resources automatically) Monetized API (sells resources for USDC, USDT, or DAI) Multi-chain support** (Ethereum, Base, Polygon, Arbitrum) Real blockchain transactions (verified on-chain) Budget management (AP2 mandates) Monitoring dashboard (track spending/revenue) Total setup time: ~10 minutes Total cost: $0 (Render free tier + AgentGatePay free) Ready to scale? Connect multiple agents, add more resources, integrate with your existing systems! Questions? Check README.md or contact support@agentgatepay.com Website: https://www.agentgatepay.com

Generate Animated Human Videos from Images & Audio with Bytedance Omni Human Built with n8n + Replicate This workflow takes an image + audio, sends them to Bytedance’s omni-human model, waits for processing, and returns a generated video. ⚡ Section 1: Start & Authenticate ▶️ On clicking ‘execute’** → Manual trigger to start the workflow. 🔑 Set API Key** → Stores your Replicate API key so future requests are authorized. Benefit: Secures your API credentials in one place for easy re-use. 🛠️ Section 2: Send Video Generation Request 📡 Create Prediction** → Makes a POST request to Replicate with: image: input image URL audio: input audio URL Model version: 7ec44f5140c7338b3496cbf99ee8ea391a4bc18ff5d1677a146dfc936a91f65b Benefit: Combines visual and audio inputs to start AI-powered video generation. 🔍 Section 3: Track the Prediction 📦 Extract Prediction ID** → Saves predictionId, status, and predictionUrl for polling. ⏳ Wait** → Pauses 2 seconds between status checks (to avoid spamming the API). 🔁 Check Prediction Status** → Queries Replicate using the stored prediction URL. ✅ Check If Complete** → Branches: If status = succeeded → move forward. Else → loop back to Wait until completion. Benefit: Ensures workflow patiently waits for the video instead of timing out. 📽️ Section 4: Process & Return Results 📦 Process Result** → Cleans the API response, returning: status video_url (generated video) metrics created_at & completed_at model: bytedance/omni-human Benefit: Gives you a neat, structured output with the generated video link ready to use. 📊 Workflow Overview | Section | Purpose | Key Nodes | Benefit | | ------------------- | --------------------------- | --------------------------------------------- | -------------------------------- | | ⚡ Start & Auth | Initialize & secure API key | Manual Trigger, Set API Key | Keeps credentials safe | | 🛠️ Send Request | Start video generation | Create Prediction | Submits image+audio to Replicate | | 🔍 Track Prediction | Poll status until done | Extract Prediction ID, Wait, Check Status, If | Reliable async handling | | 📽️ Process Result | Format output | Process Result | Easy access to final video link | ✅ Final Benefits 🎬 Turns static image + audio into full AI-generated video. 🔑 API key stored securely in workflow. 🔄 Handles async generation with auto-polling. 📤 Outputs clean JSON with direct video link. 🧩 Modular — you can connect results to Slack, Gmail, or Google Drive for auto-sharing.

Audit permissions in Confluence to ensure compliance This workflow scans selected Confluence spaces for public exposure risks, helping teams identify unintended access and potential data leakage. What it does Detects public exposure risks in Confluence spaces, including: Anonymous access permissions at space level Whether public links are enabled Pages with active or blocked public links Uses Confluence REST API v2 together with the Atlassian GraphQL API. Produces a consolidated per-space report containing: Anonymous access permissions Public link status Pages with public links (title, status, URL, enabled-by user) Ideal for security audits, compliance reviews, and data leakage prevention. How it works The workflow starts via a Manual Trigger. A Set Variables node defines: atlassianDomain spaceKeys (comma-separated) Get Spaces (v2)** retrieves matching spaces and splits them into individual items. For each space, three GraphQL queries run in parallel: Retrieve anonymous access permissions Check public link feature status at space level Fetch pages with public links (ON / BLOCKED) Results from all three queries are merged and normalized into a single per-space report. Setup Configure the Set Variables node: atlassianDomain → your Confluence base URL spaceKeys → comma-separated list (e.g. ENG, HR) Create an HTTP Basic Auth credential for Atlassian: Email + API token Assign it to all HTTP and GraphQL nodes Ensure the credential has permission to: Read spaces Read space permissions Access GraphQL endpoints Execute the workflow manually to generate the report. Notes Uses the Atlassian GraphQL API, which exposes permission and public-link data not fully available via REST. Pages with blocked public links are included for visibility. The GraphQL page query fetches up to 250 pages per space.

This workflow contains community nodes that are only compatible with the self-hosted version of n8n. What this workflow does Monitors Google Drive for new video file uploads Downloads and processes videos using VLM Run AI transcription Generates accurate transcripts with timestamps, audio content, and video descriptions Saves formatted reports to Google Docs for instant access and sharing Setup Prerequisites: Google Drive account, VLM Run API credentials, Google Docs access, self-hosted n8n. You need to install VLM Run community node Quick Setup: Configure Google Drive OAuth2 and create video upload folder Add VLM Run API credentials Set up Google Docs integration for transcript storage Update folder/document IDs in workflow nodes Test with sample video files and activate Perfect for Meeting transcription and documentation Content creation and video accessibility Educational content processing and analysis Interview transcription and note-taking Podcast and webinar documentation Legal deposition and testimony recording Customer support call analysis Key Benefits Asynchronous processing** handles large video files without timeouts Multi-format support** for MP4, AVI, MOV, WebM, MKV formats Dual content extraction** captures both audio transcripts and video descriptions Eliminates manual transcription** saving hours of documentation time High accuracy speech recognition** with multi-language support Structured output** with timestamps and scene descriptions How to customize Extend by adding: Speaker identification and voice separation Sentiment analysis and keyword extraction Integration with project management tools Email notifications for transcription completion Summary generation and key point extraction Multi-language translation capabilities Search indexing for transcript databases Integration with video editing software This workflow transforms manual video transcription into an automated, accurate, and efficient process, making video content accessible and searchable for your business operations, educational needs, or content creation workflows.

Transform your expense tracking with automated AI receipt processing that extracts data and organizes it instantly. What this workflow does Monitors Google Drive for new receipt uploads (images/PDFs) Downloads and processes files automatically Extracts key data using verified VLM Run node (merchant, amount, currency, date) Saves structured data to Airtable for easy tracking Setup Prerequisites: Google Drive account, Airtable account, VLM Run API credentials, n8n instance. Install the verified VLM Run node by searching for VLM Run in the node list, then click Install. Once installed, you can start using it in your workflows. Quick Setup: Configure Google Drive OAuth2, Airtable OAuth2 Create receipt upload folder Add VLM Run API credentials Create Airtable table with columns: Customer, Merchant, Amount, Currency, Date Update folder/table IDs in workflow nodes Test and activate How to customize this workflow to your needs Extend functionality by: Adding expense categories and approval workflows Connecting to accounting software (QuickBooks, Xero) Including Slack notifications for processed receipts Adding data validation and duplicate detection This workflow transforms manual receipt processing into an automated system that saves hours while improving accuracy. > ⚠️ Disclaimer: This workflow requires a self-hosted n8n setup because it uses custom nodes (VLM Run) that are not available on the managed n8n.cloud service.

Animate Any Face into a Video with Fal.ai Create stunning deepfake-style videos automatically by swapping a face from an image onto a source video. This workflow provides a powerful, automated pipeline to perform video face-swapping using the Fal.ai API. It's designed to handle the entire asynchronous process: accepting a source video and a target face image, uploading them to cloud storage, initiating the AI job, polling for completion, and retrieving the final, rendered video. | Services Used | Features | | :--- | :--- | | 🤖 Fal.ai | Leverages the powerful Wan 2.2 model for high-quality face animation. | | ☁️ AWS S3 | Uses enterprise-grade cloud storage for reliable public file hosting. | | 🔄 Polling Loop | Intelligently waits for the asynchronous AI job to complete before proceeding. | | 📥 n8n Form Trigger | Provides a simple UI to upload your source image and video. | How It Works ⚙️ 📥 Get User Input: The workflow starts when you upload a source video and a face image via the n8n Form Trigger. ☁️ Upload to Cloud: Both files are automatically uploaded to a specified AWS S3 bucket to generate the publicly accessible URLs required by the AI model. 🚀 Start AI Job: The public URLs for the video and image are sent in an HTTP Request to the Fal.ai API, which starts the asynchronous face animation process and returns a request_id. ⏳ Wait & Check: The workflow enters a polling loop. It Waits for one minute, then makes another HTTP Request to the Fal.ai status endpoint using the request_id. ✅ Check for Completion: An IF node checks if the job status is COMPLETED. If not, the workflow loops back to the Wait node. 🎬 Retrieve Final Video: Once the job is complete, the workflow makes a final HTTP Request to fetch the finished animated video. 🛠️ How to Set Up 🔑 Set Up Fal.ai Credentials: Get your API Key from Fal.ai. In n8n, go to Credentials, add a new Header Auth credential, and save your key. Connect this credential to all three HTTP Request nodes in the workflow. ☁️ Configure AWS S3: Add your AWS credentials in n8n. In the two AWS S3 nodes (Upload Video1 and Upload Image1), update the Bucket Name parameter to your own S3 bucket. Ensure your bucket permissions allow for public reads. ▶️ Activate and Run: Activate the workflow. Open the Form Trigger URL from the n8n editor, upload your files, and submit. The final video will be available in the execution log of the Get Final Video node. Requirements An active Fal.ai account and API key. An AWS account with an S3 bucket configured for public access. Alternative Storage:* For a personal setup, you can replace the AWS S3 nodes with *Cloudinary** nodes. Just ensure the output is a public URL. 💬 Need Help or Want to Learn More? Join my Skool community for n8n + AI automation tutorials, live Q&A sessions, and exclusive workflows: 👉 https://www.skool.com/n8n-ai-automation-champions Template Author: Sandeep Patharkar Category: Content Generation / Content Marketing Difficulty: Intermediate Estimated Setup Time: ⏱️ 20 minutes

Short description Transcribe Telegram voice/audio messages to text using Groq’s OpenAI-compatible Whisper endpoint. Replies are delivered either as a Telegram message or as a downloadable .txt file, plug-and-play for n8n with minimal setup. Who’s it for / Uses Educators, podcasters, interviewers, and support teams who need quick voice → text conversions. Automating meeting notes, voice feedback, voicemail transcription, or speech logging. Useful when you want transcripts pushed to chat or saved as files for archiving. How it works (overview) Telegram Trigger — workflow starts on incoming message. Switch (Audio/Voice) — detects voice or audio. If neither, replies “Wrong file type” and stops. Telegram Download — downloads the audio using the file_id, outputs file path/binary. Set Node (credentials + options) — stores Groq_API and Telegram_access_token (required) and transcript_output_format (message or file). HTTP Request → Groq (Whisper) — uploads audio (multipart/form-data) to Groq’s transcription endpoint and receives text. Reply Switch — routes to either: Message branch: send transcribed text as a Telegram message. File branch: convert transcript to .txt and send as a document. Requirements n8n instance (cloud or self-hosted) with internet access Telegram bot token (create via BotFather) Groq API key (create at https://console.groq.com/keys) Basic n8n nodes: Telegram Trigger, Switch, Telegram Download, Set, HTTP Request, Convert to File, Telegram Send Message/Document Important setup & notes Mandatory:* Add Groq_API and Telegram_access_token in the *Set** node (or use n8n Credentials). The workflow will fail without them. Do not hardcode** keys in HTTP node fields that will be exported/shared. Use Set fields or n8n Credentials. Include sticky notes explaining each node (yellow note with full description recommended). Sticky notes should show setup steps and required fields. Before publishing: remove personal IDs and secrets, test with sample voice messages, and verify Groq response schema to map the transcript field correctly. Security & best practices Use n8n Credentials or environment variables in production. Rotate API keys if they become exposed. Keep the Set node private when sharing templates; instruct users to replace keys with their own.

Step 1: Slack Trigger The workflow starts whenever your Slack bot is mentioned or receives an event in a channel. The message that triggered it (including text and channel info) is passed into the workflow. Step 2: Extract the Sheet ID The workflow looks inside the Slack message for a Google Sheets link. If it finds one, it extracts the unique spreadsheet ID from that link. It also keeps track of the Slack channel where the message came from. If no link is found, the workflow stops quietly. Step 3: Read Data from Google Sheet Using the sheet ID, the workflow connects to Google Sheets and reads the data from the chosen tab (the specific sheet inside the spreadsheet). This gives the workflow all the rows and columns of data from that tab. Step 4: Convert Data to CSV The rows pulled from Google Sheets are then converted into a CSV file. At this point, the workflow has the spreadsheet data neatly packaged as a file. Step 5: Upload CSV to Slack Finally, the workflow uploads the CSV file back into Slack. It can either be sent to a fixed channel or directly to the same channel where the request came from. Slack users in that channel will see the CSV as a file upload. How it works The workflow is triggered when your Slack bot is mentioned or receives a message. It scans the message for a Google Sheets link. If a valid link is found, the workflow extracts the unique sheet ID. It then connects to Google Sheets, reads the data from the specified tab, and converts it into a CSV file. Finally, the CSV file is uploaded back into Slack so the requesting user (and others in the channel) can download it. How to use In Slack, mention your bot and include a Google Sheets link in your message. The workflow will automatically pick up the link and process it. Within a short time, the workflow will upload a CSV file back into the same Slack channel. You can then download or share the CSV file directly from Slack. Requirements Slack App & Credentials: Your bot must be installed in Slack with permissions to receive mentions and upload files. Google Sheets Access: The Google account connected in n8n must have at least read access to the sheet. n8n Setup: The workflow must be imported into n8n and connected to your Slack and Google Sheets credentials. Correct Sheet Tab: The workflow needs to know which tab of the spreadsheet to read (set by name or by sheet ID). Customising this workflow Channel Targeting: By default, the file can be sent back to the channel where the request came from. You can also set it to always post in a fixed channel. File Naming: Change the uploaded file name (e.g., include the sheet title or today’s date). Sheet Selection: Adjust the configuration to read a specific tab or allow the user to specify the tab in their Slack message. Error Handling: Add extra steps to send a Slack message if no valid link is detected, or if the Google Sheet cannot be accessed. Formatting: Extend the workflow to clean, filter, or enrich the data before converting it into CSV.