Read data. Move funds.
Look up an account or transaction, list receivables, send an exact amount, receive funds, or change a representative.
AccountsTransactionsReceivablesRepresentatives
BuildAtto N8N
Payments belong
in your workflow.
Add ATTO cryptocurrency payments to self-hosted N8N with an action node and a live-event trigger. Read an account, react to an incoming payment, or make a payment part of your next automation.
Self-hosted N8N with community nodes enabled · Node.js 22.22.0 or newer, plus N8N’s own runtime requirements. Check installation →
Package on npm ↗INCOMING PAYMENT0.0001 ATTO
- ATTO TRIGGERPayment eventA receivable appears
- ATTOReceive fundsCredit the account
- YOUR WORKFLOWNext stepUse the payment result
AMOUNT RECEIVED0.0001 ATTO
NETWORK FEE0 ATTO
The trigger observes the payment. The receive step signs a transaction using your workflow credentials.
Two nodes.
Your next connection.
Use one to act on the network and the other to listen. Connect them to the rest of the workflow you already own.
Start when something happens.
Listen for incoming payments, account updates, transactions, or account entries. Live streams reconnect when a connection closes.
Incoming paymentsAccount updatesLedger events
Start with a workflow.
Make it your own.
Begin with a public account lookup or explore the importable examples. Add your own credentials before running a signing operation.
Inspect a public account.
Connect a Manual Trigger to Account → Get. Read a balance, representative, and frontier without giving the workflow a wallet secret.
Build the read-only example →Receive an incoming payment.
Connect Atto Trigger to Receivable → Receive. The first node observes; the second signs the receive transaction and credits your account.
View the importable workflow ↗Return the full amount.
The ping-pong example receives a payment and sends the same raw amount back. There is no protocol transaction fee to subtract.
Explore the payment loop ↗The receive and send-back examples publish real transactions when run with signing credentials. Review the nodes, addresses, and execution behavior before activating them.
Observe with an address.
Sign with credentials.
A read-only workflow and a payment workflow need different access. Keep that distinction visible in what you build.
Network reads need no wallet secret.
Use a public address and the Node endpoint for account lookups and manually addressed payment triggers. Observing a receivable does not receive the funds.
Set up an incoming-payment trigger →Signing access belongs to the workflow.
Sending, receiving, and representative changes need wallet signing material and a Worker endpoint. Keep secrets in encrypted N8N credentials, not exported workflows.
Review signing requirements →N8N does not inherit CLI or MCP spending caps and terminal approvals. Use a dedicated wallet, restrict credential access, and build any approval or amount checks into your workflow. Review execution-data retention before using real funds.
Another way to build.
Choose the interface that fits the work. Each connects to the same feeless Atto network.
Build with Atto N8N.
Open the guide for setup, requirements, and implementation details.