1SHOT API n8n INTEGRATION: SMART CONTRACTS & WALLETS ON AUTOPILOT

The "List chains" action retrieves all blockchain networks available in your 1Shot account. This is your starting point for any multi-chain workflow—knowing which chains are accessible before executing operations on them.

Key parameters: Credential to connect with: Select your 1Shot account credentials from the dropdown. Required. Resource: Set to "Chain" to indicate you're working with blockchain networks. Required. Operation: Automatically set to "List Chains". Page Number: Specify which page of results to retrieve. Accepts numeric input, defaults to page 1. Page Size: Define how many chains to return per page. Defaults to 25 results.

Use cases: Build a dynamic chain selector in your automation that adapts to newly supported networks. Audit which chains are configured in your account before deploying contracts. Create monitoring workflows that iterate through all available chains.

This action ensures contract methods are available based on a prompt identifier—essential when you need to guarantee that specific contract interactions are ready before executing workflows that depend on them.

Key parameters: Credential to connect with: Your 1Shot authentication credentials. Required. Resource: Set to "Contract Method". Required. Operation: "Assure Contract Methods From Prompt". Chain Name or ID: Text input identifying which blockchain to use. Required. Contract Address: The smart contract's address. Required. Prompt ID: Unique identifier for the prompt. Required. Wallet Name or ID: Identifier for the wallet involved in transactions. Required.

Use cases: Pre-flight checks before batch contract executions to ensure all methods are available. Automated setup workflows when deploying to new chains. Validation steps in CI/CD pipelines for smart contract deployments.

The "Encode" action generates the encoded data for a smart contract method call. This is particularly useful when you need to prepare transaction data without immediately executing it—perfect for multisig workflows or transaction batching.

Key parameters: Credential to connect with: 1Shot account credentials. Required. Resource: Set to "Contract Method". Required. Operation: "Encode". Contract Method Name or ID: Specify which method to encode. Required. Parameters: Additional fields for method parameters. Add multiple fields as needed based on the contract method's requirements.

Use cases: Prepare transactions for multisig approval workflows. Generate encoded calldata for meta-transaction systems. Build transaction queues where encoding and execution are separated.

Before executing any transaction on-chain, knowing the gas cost prevents unexpected failures and budget overruns. This action returns gas estimates for specific contract method calls.

Key parameters: Credential to connect with: Your 1Shot credentials. Required. Resource: "Contract Method". Required. Operation: "Estimate". Contract Method Name or ID: The method you want to estimate gas for. Required. Parameters: Optional additional parameters for the contract method, typically in JSON format.

Use cases: Pre-check gas costs before batch operations to ensure wallet has sufficient funds. Build cost-aware automation that chooses optimal execution times. Alert workflows that notify when gas estimates exceed thresholds.

This is the core action for blockchain automation—actually executing a smart contract method on-chain. The transaction is signed and broadcast through your configured wallet.

Key parameters: Credential to connect with: 1Shot credentials. Required. Resource: "Contract Method". Required. Operation: "Execute". Contract Method Name or ID: Which method to execute. Required. Parameters: Optional JSON-formatted parameters for the method. Additional Fields: Expandable section for extra configuration like gas limits or value transfers.

Use cases: Automate token transfers based on external triggers. Execute DAO governance actions programmatically. Trigger on-chain state changes from off-chain events.

Similar to standard execution, but specifically designed for delegated transactions where a separate delegator wallet handles the gas payment. This enables gasless experiences for end users.

Key parameters: Credential to connect with: 1Shot credentials. Required. Resource: "Contract Method". Required. Operation: "Execute as Delegator". Contract Method Name or ID: Method identifier. Required. Parameters: Optional method parameters as object format. Delegator Wallet Address: The wallet address that will pay for gas. Required. Additional Fields: Extra configuration options.

Use cases: Sponsor gas fees for users in your dApp. Build gasless NFT minting experiences. Enable meta-transactions in gaming applications.

The "Execute Batch" operation lets you execute multiple contract methods in a single workflow step—dramatically reducing complexity when you need to perform several on-chain operations together.

Key parameters: Credential to connect with: 1Shot credentials. Required. Resource: "Contract Method". Required. Operation: "Execute Batch". Contract Methods: Select specific contract methods to execute. Required. Wallet Name or ID: Optional specification of which wallet to use. Additional Fields: Expandable for extra parameters.

Use cases: Bundle multiple token approvals and swaps into single workflows. Execute complex DeFi strategies with multiple contract interactions. Batch update multiple on-chain records simultaneously.

Combines batch execution with delegation—execute multiple smart contracts while having a separate wallet cover all gas costs.

Key parameters: Credential to connect with: 1Shot credentials. Required. Resource: "Contract Method". Required. Operation: "Execute Batch as Delegator". Contract Methods: Select the methods to batch execute. Required. Wallet Name or ID: Specify the wallet. Required. Additional Fields: Extra configuration options.

Use cases: Onboard users with multiple initial transactions without requiring them to hold native tokens. Execute complex sponsored transactions for premium users. Build white-label services where your infrastructure handles gas.

Retrieve detailed information about a specific contract method—useful for validation, documentation generation, or building dynamic interfaces based on contract capabilities.

Key parameters: Credential to connect with: 1Shot credentials. Required. Resource: "Contract Method". Required. Operation: "Get". Contract Method ID: Unique identifier for the method. Required.

Use cases: Validate contract methods exist before building workflows around them. Generate documentation dynamically from contract metadata. Build admin interfaces that display contract method details.

Get a comprehensive list of all contract methods you have access to, with powerful filtering options to narrow down exactly what you need.

Key parameters: Credential to connect with: 1Shot credentials. Required. Resource: "Contract Method". Required. Operation: "List". Name: Optional filter by method name. Contract Address: Optional filter by contract. Prompt ID: Optional filter by prompt. Method Type: Dropdown to filter by type (default: None). Chain Name or ID: Optional blockchain filter. Page Number: Pagination control, defaults to 1. Page Size: Results per page, defaults to 25.

Use cases: Inventory all available contract methods in your account. Build method selectors for user-facing interfaces. Audit contract method access across your organization.

Test contract execution without actually sending a transaction on-chain. Simulation reveals potential errors, return values, and gas consumption before committing real resources.

Key parameters: Credential to connect with: 1Shot credentials. Required. Resource: "Contract Method". Required. Operation: "Simulate". Contract Method Name or ID: Which method to simulate. Required. Parameters: Optional JSON parameters for the simulation. Gas Limit: Optional numeric gas limit for the simulation.

Use cases: Pre-validate transactions before batch execution. Test contract interactions during development workflows. Build "dry run" features in dApp interfaces.

Query blockchain state without sending transactions. This read-only operation retrieves data from view/pure contract functions—perfect for monitoring and data collection.

Key parameters: Credential to connect with: 1Shot credentials. Required. Resource: "Contract Method". Required. Operation: "Read". Contract Method Name or ID: The view function to call. Required. Parameters: Optional JSON parameters for methods that require inputs.

Use cases: Monitor token balances across multiple addresses. Track on-chain metrics for dashboards and reporting. Validate state before triggering write operations.

Retrieve details about a specific transaction by its name or ID—essential for tracking transaction status and building confirmation workflows.

Key parameters: Credential to connect with: 1Shot credentials. Required. Resource: "Transaction". Required. Operation: "Get Transaction". Transaction Name or ID: Unique identifier for the transaction. Required.

Use cases: Check transaction confirmation status in follow-up workflows. Build receipt generation after successful transactions. Debug failed transactions by retrieving full details.

Get a filtered list of all transactions, with extensive options to narrow down by status, wallet, time range, and more.

Key parameters: Credential to connect with: 1Shot credentials. Required. Resource: "Transaction". Required. Operation: "List Transactions". Status: Optional dropdown filter by transaction status. Wallet ID: Optional filter by specific wallet. Contract Method ID: Optional filter by contract method. API Credential ID: Optional credential filter. User ID: Optional user filter. Memo: Optional text search in memos. After Time: Numeric timestamp filter (default: 0). Before Time: Numeric timestamp filter (default: 0). Page Number: Pagination control.

Use cases: Build transaction history pages in applications. Monitor pending transactions and alert on stuck operations. Generate accounting reports with filtered transaction data.

Programmatically create new wallets in your 1Shot account. Essential for user onboarding flows and multi-wallet architectures.

Key parameters: Credential to connect with: 1Shot credentials. Required. Resource: "Wallet". Required. Operation: "Create Wallet". Chain Name or ID: Specify the blockchain for this wallet. Required. Name: Give the wallet a recognizable name. Required. Description: Optional detailed description.

Use cases: Auto-create wallets when users sign up for your platform. Provision chain-specific wallets for multi-chain applications. Build treasury management systems with organized wallet structures.

Find specific prompts using search queries and chain filters. Prompts in 1Shot help define reusable contract interaction patterns.

Key parameters: Credential to connect with: 1Shot credentials. Required. Resource: "Prompt". Required. Operation: "Search Prompts". Query: Optional text search term. Chain Name or ID: Optional blockchain filter.

Use cases: Build prompt discovery features in your applications. Find specific prompts before assuring contract methods. Audit available prompts across different chains.

Remove a wallet from your 1Shot account. Use carefully—this operation may be irreversible depending on your account configuration.

Key parameters: Credential to connect with: 1Shot credentials. Required. Resource: "Wallet". Required. Operation: "Delete Wallet". Wallet Name or ID: Specify which wallet to remove. Required.

Use cases: Clean up test wallets after development cycles. Remove deprecated wallets from decommissioned applications. Build account management workflows with wallet lifecycle control.

Retrieve all wallets in your account with optional filters—the foundation for any wallet management workflow.

Key parameters: Credential to connect with: 1Shot credentials. Required. Resource: "Wallet". Required. Operation: "List Wallets". Chain Name or ID: Optional chain filter. Name: Optional search by wallet name. Page Number: Pagination control, defaults to 1. Page Size: Results per page, defaults to 25.

Use cases: Build wallet selection interfaces in your applications. Audit all wallets across your organization. Monitor wallet inventory and generate reports.

Retrieve detailed information about a specific wallet, including balances, configuration, and metadata.

Key parameters: Credential to connect with: 1Shot credentials. Required. Resource: "Wallet". Required. Operation: "Get Wallet". Wallet Name or ID: Specify the wallet to retrieve. Required.

Use cases: Check wallet details before initiating transactions. Build wallet detail pages in user interfaces. Validate wallet existence in pre-flight workflow checks.

Modify wallet properties like name and description. Useful for keeping wallet metadata organized as your systems evolve.

Key parameters: Credential to connect with: 1Shot credentials. Required. Resource: "Wallet". Required. Operation: "Update Wallet". Chain Name or ID: Identify the chain context. Required. Wallet Name or ID: Specify which wallet to update. Required. Name: Optional new name for the wallet. Description: Optional new description.

Use cases: Rename wallets as project requirements change. Add descriptions to document wallet purposes. Build wallet management admin panels.