Create a self-hosted blockchain payment processor with x402 and 1Shot API

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

This workflow contains community nodes that are only compatible with the self hosted version of n8n. Self Hosted x402 Facilitator In the [x402](https://x402.o...

Best for

Crypto Trading automation workflows
Multimodal AI automation workflows
advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-1shot.oneshot, n8n-nodes-base.webhook, n8n-nodes-base.respondtowebhook, n8n-nodes-1shot.oneshotsynch, n8n-nodes-base.if, n8n-nodes-base.stickynote, n8n-nodes-base.code

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by 1Shot API.

Original n8n.io source

1.1 Workflow description

Title: Create a self-hosted blockchain payment processor with x402 and 1Shot API
Workflow name: Create a self-hosted blockchain payment processor with x402 and 1Shot API

This workflow contains community nodes that are only compatible with the self-hosted version of n8n.

Self-Hosted x402 Facilitator

In the x402 payment protocol, a facilitator is a role which helps sellers settle stablecoin payments onchain without dealing with blockchain complexities. This workflow allows you to run your own fully-featured, specification-compliant facilitator in n8n. You might want to do this if you want to accept payments in tokens not supported by existing facilitators or as your own business!

Details

A facilitator supports three routes: /verify, /settle, and /supported. These routes are all created for you in this workflow with proper error handling and responses.

A seller will first hit /verify with their payment details to ensure the payment information is correct. Next they will hit the /settle endpoint with the same payment information to settle the paymet on the blockchain. The /supported endpoint is used to indicate to sellers which blockchains you choose to support in a programatic fashion.

Setup

Create a 1Shot API account
Create 1Shot API wallets for the networks where you wish to facilitate token payments and load them with sufficient gas tokens.
Using 1Shot Prompts, import the transferWithAuthorization functions for the tokens you will settle payments for.
Import this workflow into n8n and create a credential to link the 1Shot API community node to your 1Shot API business account.
Enter the token and network information into the payment token and network configuration nodes indicated by the sticky nodes.
Turn on your workflow and settle payments!

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Simulate Payment

Type / Role: n8n-nodes-1shot.oneShot - oneShot
Config choices: Version 1

Block 2 - /verify

Type / Role: n8n-nodes-base.webhook - webhook
Config choices: Version 2

Block 3 - /settle

Type / Role: n8n-nodes-base.webhook - webhook
Config choices: Version 2

Block 4 - Settlement Response

Type / Role: n8n-nodes-base.respondToWebhook - respondToWebhook
Config choices: Version 1.3

Block 5 - Verify Response

Type / Role: n8n-nodes-base.respondToWebhook - respondToWebhook
Config choices: Version 1.3

Block 6 - Response: Bad POST Body (/verify)

Type / Role: n8n-nodes-base.respondToWebhook - respondToWebhook
Config choices: Version 1.3

Block 7 - Response: Bad POST Body (/settle)

Type / Role: n8n-nodes-base.respondToWebhook - respondToWebhook
Config choices: Version 1.3

Block 8 - 1Shot API Submit & Wait

Type / Role: n8n-nodes-1shot.oneShotSynch - oneShotSynch
Config choices: Version 1

Block 9 - Check POST Payload

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2.2

Block 10 - /supported

Type / Role: n8n-nodes-base.webhook - webhook
Config choices: Version 2.1

Block 11 - Response: Return Supported Networks

Type / Role: n8n-nodes-base.respondToWebhook - respondToWebhook
Config choices: Version 1.3

Block 12 - Sticky Note

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 13 - Sticky Note1

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 14 - Sticky Note2

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 15 - Sticky Note3

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 16 - Sticky Note4

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 17 - Supported Networks Config

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 18 - Sticky Note5

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 19 - Sticky Note6

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 20 - Unsupported Token

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2.2

Block 21 - verify or settle

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2.2

Block 22 - Response: Unsupported Token (/verify)

Type / Role: n8n-nodes-base.respondToWebhook - respondToWebhook
Config choices: Version 1.3

Block 23 - Response: Unsupported Token (/settle)

Type / Role: n8n-nodes-base.respondToWebhook - respondToWebhook
Config choices: Version 1.3

Block 24 - Bad Payload

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2.2

Showing the first 24 of 26 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow	Create a self-hosted blockchain payment processor with x402 and 1Shot API
Complexity	advanced
Nodes	26
Categories	Crypto Trading, Multimodal AI
Author	1Shot API
Published	14 Aug 2025

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/7364/7364.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Download workflow JSON Original n8n.io source Crypto Trading workflows Multimodal AI workflows

Frequently asked questions

What does Create a self-hosted blockchain payment processor with x402 and 1Shot API do?

This workflow contains community nodes that are only compatible with the self hosted version of n8n. Self Hosted x402 Facilitator In the [x402](https://x402.o...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Crypto Trading, Multimodal AI use case.

1Shot API

9 workflows

Nodes

n8n-nodes-1shot.oneshot n8n-nodes-base.webhook n8n-nodes-base.respondtowebhook n8n-nodes-1shot.oneshotsynch n8n-nodes-base.if n8n-nodes-base.stickynote n8n-nodes-base.code

Complexity

advanced

Published 14 Aug 2025

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/7364/7364.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Send portfolio risk reports with Google Sheets, GPT-4o-mini and Gmail

## Quick Overview This workflow receives a portfolio via webhook (uploaded CSV or Google Sheets), calculates allocation and concentration risk metrics, generates an OpenAI HTML risk report, emails it through Gmail, and returns a JSON API response with the report status. ## How it works 1. Receives a POST webhook request containing a portfolio source type plus user name and email. 2. Loads holdings either by decoding an uploaded base64 CSV into rows or by reading rows from Google Sheets. 3. Combines all holdings into a single dataset and attaches user and source metadata. 4. Calculates portfolio totals, position weights, sector and asset-class breakdowns, concentration flags, top gainers/losers, and an overall risk score and label. 5. If the portfolio is valid, sends the computed metrics to OpenAI to generate a client-ready HTML risk narrative. 6. Builds a formatted HTML email that includes the AI analysis plus sector and top-holdings tables, then sends it to the user via Gmail and returns a success JSON response. 7. If the portfolio is empty or invalid, emails a failure notice via Gmail (when an email is provided) and returns a 422 JSON error response. ## Setup 1. Create and connect credentials for Google Sheets OAuth2, OpenAI, and Gmail OAuth2. 2. Configure the webhook endpoint by copying the production URL and sending POST requests to the /portfolio-analyze path. 3. For CSV submissions, include base64 CSV content in body.fileData (or body.csvBase64/body.file) and ensure the columns include ticker, company, sector, quantity, avg_buy_price, current_price, and asset_class. 4. For Google Sheets submissions, update the spreadsheet document ID and sheet (gid) to the holdings table you want to analyze. 5. Ensure the request includes userEmail (body, query, or x-user-email header) so the workflow can deliver the report or validation error message.

View

Analyze commodity portfolio diversification with Sheets, Gemini, and Gmail

## Quick Overview This workflow reads a gold/silver/oil portfolio from Google Sheets, pulls current commodity prices and a recent gold trend from GoldAPI, EIA, and Twelve Data, calculates allocation and HHI concentration risk, generates a Gemini analysis, and emails an HTML diversification report via Gmail. ## How it works 1. Starts manually and loads configuration values, then reads your portfolio holdings from Google Sheets. 2. Fetches real-time gold and silver prices in INR from GoldAPI, retrieves crude oil prices in USD from the EIA API, and converts oil prices to INR. 3. Pulls the last two daily closes for GLD from Twelve Data and compares them to label the gold market trend as UP or DOWN. 4. Aggregates the latest commodity prices and trend data, then calculates portfolio allocation percentages and an HHI concentration score from the Google Sheets holdings. 5. Sends the allocation, HHI score, and gold trend to Google Gemini to generate a structured risk assessment, rebalancing recommendations, trend impact, and a verdict. 6. Parses Gemini’s response into dedicated fields, builds a formatted HTML report with prices, allocations, risks, recommendations, and verdict, and sends it to the configured recipient via Gmail. ## Setup 1. Add API keys for GoldAPI, the U.S. EIA API, and Twelve Data in the configuration step (and confirm the USD-to-INR conversion rate is correct for your needs). 2. Connect your Google Sheets account, then update the spreadsheet and sheet tab to a portfolio table that includes commodity_name and buy_price for gold, silver, and oil. 3. Connect your Google Gemini (PaLM) API credential and ensure the selected model is available in your account. 4. Connect your Gmail OAuth2 credential and set the recipient email address used for the report delivery.

View

Log gold and silver prices and email Groq insights with Google Sheets

## Quick Overview This workflow manually logs daily Gold and Silver prices from GoldAPI into Google Sheets, summarizes historical monthly averages, generates seasonal insights with Groq (LLM), builds QuickChart bar charts, and emails a formatted report via Gmail. ## How it works 1. Starts manually and loads a two-item asset list (Gold/XAU and Silver/XAG) to process in a loop. 2. For each commodity, calls the GoldAPI endpoint to fetch the latest INR price and converts it into a per-10g value with date and month fields. 3. Checks Google Sheets for an existing row for the same commodity and date, keeps the higher of the two prices, and appends or updates the row in the historical sheet. 4. Reads the full historical dataset from Google Sheets and calculates monthly average, minimum, and maximum prices grouped by month and commodity. 5. Formats the monthly averages into a text block and sends it to a Groq-hosted chat model to generate a structured JSON insight summary for gold, silver, and the overall trend. 6. Creates QuickChart URLs for separate Gold and Silver monthly-average bar charts and emails the AI summary and chart images using Gmail. ## Setup 1. Add a GoldAPI key and set it in the HTTP request header (x-access-token) for the GoldAPI call. 2. Connect Google Sheets OAuth credentials and select the target spreadsheet and sheet tab where rows are stored (e.g., the 04_HistoricalData sheet). 3. Ensure the sheet has columns for ID, Date, Month, Price, and Commodity, and that ID is used as the upsert/matching key. 4. Add Groq API credentials for the Groq chat model used to generate the JSON insights. 5. Connect Gmail OAuth credentials and replace the placeholder recipient address ("RECEIVER MAIL ID") and subject as needed.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Create a self-hosted blockchain payment processor with x402 and 1Shot API

Workflow preview

Important notice

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

Self-Hosted x402 Facilitator

Details

Setup

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Simulate Payment

Block 2 - /verify

Block 3 - /settle

Block 4 - Settlement Response

Block 5 - Verify Response

Block 6 - Response: Bad POST Body (/verify)

Block 7 - Response: Bad POST Body (/settle)

Block 8 - 1Shot API Submit & Wait

Block 9 - Check POST Payload

Block 10 - /supported

Block 11 - Response: Return Supported Networks

Block 12 - Sticky Note

Block 13 - Sticky Note1

Block 14 - Sticky Note2

Block 15 - Sticky Note3

Block 16 - Sticky Note4

Block 17 - Supported Networks Config

Block 18 - Sticky Note5

Block 19 - Sticky Note6

Block 20 - Unsupported Token

Block 21 - verify or settle

Block 22 - Response: Unsupported Token (/verify)

Block 23 - Response: Unsupported Token (/settle)

Block 24 - Bad Payload

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions