Back to Catalog

Create autonomous payment agents using AgentGatePay and multi-chain tokens

AgentGatePayAgentGatePay
57 views
2/3/2026
Official Page

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:

  1. Click: Deploy to Render
  2. Enter:
    • AGENTGATEPAY_API_KEY: Your buyer API key
    • WALLET_PRIVATE_KEY: Your wallet private key (0x...)
  3. 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:

  1. Go to WorkflowsAdd Workflow
  2. Click (three dots) → Import from File
  3. 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:

  1. Go to SettingsDataData Tables
  2. Create table: AgentPay_Mandates
  3. Add column: mandate_token (type: String)
  4. 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

  1. Open Buyer Agent workflow
  2. Click Execute Workflow
  3. 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

1. Buyer Agent requests resource
   ↓
2. Seller returns 402 Payment Required
   (includes: wallet address, price, token, chain)
   ↓
3. Buyer signs TWO blockchain transactions via Render:
   - Merchant payment (99.5%)
   - Gateway commission (0.5%)
   ↓
4. Buyer resubmits request with transaction hashes
   ↓
5. Seller verifies payment with AgentGatePay API
   ↓
6. 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:

  1. Ensure your wallet has the selected token on the selected chain
  2. Update Render service to support the chain (add RPC URL)
  3. 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

n8n Workflow: Create Autonomous Payment Agents using AgentGatePay and Multi-Chain Tokens

This n8n workflow provides a foundational structure for building and managing autonomous payment agents. It integrates with external APIs, processes data conditionally, and allows for custom code execution, laying the groundwork for sophisticated payment automation using platforms like AgentGatePay and multi-chain tokens.

What it does

This workflow is a template designed to be extended for creating autonomous payment agents. Here's a breakdown of its current components:

  1. Manual Trigger: Initiates the workflow manually, allowing for on-demand execution and testing.
  2. HTTP Request: This node is set up to make an API call. In a real-world scenario, this would likely interact with the AgentGatePay API or a similar payment gateway to initiate transactions, query payment statuses, or manage agent configurations.
  3. If Node: Introduces conditional logic into the workflow. It can be configured to evaluate the response from the HTTP Request (e.g., check for successful payment, specific token type, or agent status) and route the workflow accordingly.
  4. Code Node: Provides the flexibility to execute custom JavaScript code. This is crucial for complex data manipulation, custom business logic, or integrating with services not directly supported by existing n8n nodes. For payment agents, this could involve token calculations, cryptographic operations, or dynamic payload generation.
  5. Data Table: A helper node that can store and display structured data within the workflow. This could be used for debugging, logging payment agent states, or holding configuration parameters.
  6. Sticky Note: A documentation node for adding comments and explanations directly within the workflow canvas, making it easier to understand and maintain.

Prerequisites/Requirements

To fully utilize and extend this workflow for its intended purpose, you will likely need:

  • AgentGatePay Account: For integrating with the payment gateway.
  • API Keys/Credentials: For authenticating with AgentGatePay or any other external services used for multi-chain token interactions.
  • Understanding of JavaScript: For customizing the "Code" node to implement specific agent logic.
  • n8n Instance: A running n8n instance to import and execute the workflow.

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure HTTP Request: Update the "HTTP Request" node with the correct API endpoint, method (GET, POST, etc.), headers, and body required to interact with AgentGatePay or your chosen multi-chain token platform.
  3. Set Up Credentials: If your API calls require authentication, configure the appropriate credentials in n8n and link them to the "HTTP Request" node.
  4. Customize If Node: Define the conditions in the "If" node based on the expected API responses or business logic for your payment agents.
  5. Develop Custom Logic (Code Node): Write your JavaScript code in the "Code" node to handle specific actions, data transformations, or integrations required for your autonomous payment agents.
  6. Utilize Data Table: Use the "Data table" node for temporary data storage, debugging, or displaying key information during workflow execution.
  7. Add Documentation (Sticky Note): Use the "Sticky Note" to add comments and explanations for future reference.
  8. Execute: Click "Execute Workflow" to run the workflow manually and test its functionality. Once configured and tested, you can set up a different trigger (e.g., Webhook, Cron) for autonomous operation.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942