FlowRunner
PricingContact
Theme
Start Free

Solana

Finance

Query the Solana blockchain over JSON-RPC. Agents read wallet balances and SPL token holdings, look up transactions and signature history, fetch blockhashes and slots, broadcast pre-signed transactions, and call any other RPC method through an escape hatch.

9 actions API key available
Solana website ↗ Platform Documentation ↗ Capability data verified 2026-07-28
A scheduled sweep runs against the treasury wallets every fifteen minutes
Get Signatures For Address checks each wallet for transactions newer than the last processed signature
Get Transaction decodes any new activity: instructions, balance changes, fees, and the counterparty accounts
The agent classifies each transaction against expected activity, known payment runs, staking operations, scheduled transfers
Expected activity logs quietly to the ledger sheet; anything unrecognized posts to the treasury channel immediately
The treasury owner reviews unrecognized outflows and decides whether this is an unlogged legitimate operation or an incident in progress
The confirmed classification is recorded, keeping the on-chain ledger and the internal books reconciled

What This Integration Enables

A blockchain is a ledger that never closes, which makes it a natural fit for agents and a terrible fit for manual monitoring. This connector gives FlowRunner agents direct JSON-RPC access to Solana: wallet balances in SOL and SPL tokens, full transaction decoding with jsonParsed structure, signature history paging, the blockhash and slot primitives that transaction-building workflows need, and an escape hatch to every other RPC method. Point it at the public mainnet endpoint or your own Helius, QuickNode, or Alchemy URL. The design stance is deliberate: this connector reads the chain aggressively and touches it reluctantly. Signing happens off-platform, in your key management, and the one action that broadcasts is treated as what it is, the irreversible step. - Monitor SOL balances and SPL token holdings across treasury and operational wallets - Decode confirmed transactions into structured JSON for reconciliation and audit - Page through an address's full signature history for reporting - Fetch blockhashes and slots to support off-platform transaction building - Reach getBlock, getSupply, getProgramAccounts, simulateTransaction, and any other RPC method via the escape hatch

Without FlowRunner

Wallet checks by block explorer Someone pastes addresses into a browser when they remember to, and on-chain activity between checks is invisible
Reconciliation after the fact The books meet the chain at month end, and every mismatch is an archaeology project by then
Balance questions interrupt engineers Every "what does the treasury hold" from finance becomes a request to whoever knows the tooling

With FlowRunner

Wallets watched continuously Balances, token holdings, and signature history stream on schedule, and unrecognized outflows page a human in minutes
A ledger that reconciles itself Every confirmed transaction is decoded and classified as it lands, so the books and the chain never drift far
Treasury data self-serve Balance and holdings snapshots land in the reporting sheet automatically, current to the last sweep

Use Case Scenarios

The treasury snapshot that finance reads at standup

Every hour, Get Balance and Get Token Accounts By Owner sweep the treasury wallets, and the SOL and per-mint token balances append to [Google Sheets](/integrations/google-sheets) with a timestamp. The sheet becomes the treasury's time series: holdings over time, inflow and outflow patterns, and a number finance can cite without asking engineering. When a balance moves outside its expected band between sweeps, the flow posts the delta to [Slack](/integrations/slack) with the triggering signatures attached.

On-chain activity alerts with the decoding already done

Get Signatures For Address detects a new transaction on a watched wallet. Get Transaction decodes it, jsonParsed turns recognized instructions into readable structure, and the agent posts a human-legible alert to [Discord](/integrations/discord): what moved, where, what it cost in fees, and its confirmation status. The community managers and the ops team see the same decoded truth at the same time, and nobody is squinting at base58 in a block explorer.

Payment verification for operations that settle on-chain

A partner reports paying an invoice by SPL token transfer and provides the signature in a shared sheet. The flow picks up the new row, calls Get Transaction, verifies the destination address, mint, and amount against the invoice, and checks confirmation status. Verified payments mark the invoice settled in the ERP and confirm to the partner; mismatches route to the finance owner with the decoded transaction attached. Settlement verification becomes minutes of machine work instead of a support thread.

Human-in-Loop Highlight

Send Transaction broadcasts value movement that no one can reverse: once the cluster confirms a transfer of SOL or tokens, there is no chargeback, no support ticket, no undo, only the counterparty's goodwill. The connector's design already respects this, the transaction must be built, signed, and serialized off-platform, keys never touch FlowRunner, but the broadcast itself is still the moment of no return, and FlowRunner flows gate it accordingly. The agent prepares everything around the edge: fetches the blockhash via Get Latest Blockhash, runs simulateTransaction through Call RPC Method to preview effects, and presents the decoded intent, destination, amount, mint, fee, to the treasury owner through a [human-in-the-loop](/concepts/human-in-the-loop) step. Only that approval triggers the broadcast, and the flow then confirms inclusion with Get Transaction rather than assuming success. Reads run continuously and free. The one write on this page moves money forever, and it waits for a human every single time.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

9 actions

Accounts

2
  • Get Balance Returns an account's SOL balance, reported in lamports with a convenience sol field converted at 1 SOL to 1,000,000,000 lamports. Commitment level controls how finalized the queried state must be.
  • Get Account Info Returns detailed account information: owner program, lamport balance, executable flag, and parsed data. jsonParsed encoding returns recognized account types, such as SPL token accounts and mints, as structured JSON. Returns null for nonexistent accounts.

Transactions

3
  • Get Transaction Returns full details for a confirmed transaction by signature: instructions, account keys, balances before and after, logs, and fees, with versioned transaction support and jsonParsed instruction decoding. Returns null when unconfirmed or not found.
  • Get Signatures For Address Returns the most recent transaction signatures involving an address, newest first, each with signature, slot, block time, confirmation status, and any error. Page history with before, until, and limit, up to 1000 signatures per call.
  • Send Transaction Broadcasts an already-signed, serialized transaction and returns its signature. Advanced and high-risk: transfers are irreversible, and this action submits without confirming, so verify inclusion afterward. The write this page's human gate exists for.

Cluster

2
  • Get Latest Blockhash Returns the latest blockhash and the last block height at which it remains valid. Required input for building and signing a transaction before broadcast.
  • Get Slot Returns the current slot the node is processing, Solana's fundamental time unit at roughly 400ms. Useful for cluster-position checks and slot-based logic.

Tokens

1
  • Get Token Accounts By Owner Returns all SPL token accounts owned by a wallet for a chosen token program, standard SPL Token or Token-2022, with each account's mint, owner, amount, and decimals as structured JSON.

Advanced

1
  • Call RPC Method Escape hatch for any Solana JSON-RPC method without a dedicated action: provide the exact method name and params array per the RPC documentation and receive the raw result. Covers getBlock, getEpochInfo, getSupply, getProgramAccounts, simulateTransaction, and more.

Frequently Asked Questions

What can FlowRunner do with Solana?

FlowRunner agents can run Get Balance, Get Account Info, and Get Transaction in Solana, plus 6 more actions.

Does connecting Solana to FlowRunner require OAuth?

No. Solana connects to FlowRunner with an API key, no OAuth flow required.

Can Solana trigger a FlowRunner workflow automatically?

Solana doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Solana

$100 in credits. No card required. Connect in minutes.