1Shot API n8n integrationAutomate 1Shot API with n8n.

This operation makes an HTTP request to an x402-enabled API endpoint and pays any fee from a 1Shot Wallet. The request itself behaves like a normal HTTP call, the payment happens underneath.

• Wallet Name or ID: the wallet that pays the fee, picked from the list or set with an expression.
• URL: the URL to make the request to, in the form http://example.com/index.html.
• Credential Type and Generic Auth Type: how the call authenticates against the target endpoint.
• Method: GET, POST, PUT, PATCH, DELETE, HEAD or OPTIONS.

Returns the chains supported by 1Shot API, one page at a time. It is the cheapest call to run when you want to confirm the credential works before touching anything that costs gas.

• Page Number: the page to get, starting at 1.
• Page Size: how many chains come back in that page.

Registers a new contract event definition in 1Shot. The definition is what later operations point at, so nothing is monitored until this exists.

• Chain Name or ID: the chain the contract lives on.
• Contract Address: the address of the contract to monitor for events.
• Event Name: the exact name of the event as defined in the contract ABI, spelling included.
• Name and Description: a human-readable name and a description of what this event represents, both required.

Removes a contract event definition. The definition disappears from 1Shot, and any workflow still pointing at that identifier will fail on its next run.

• Contract Event Name or ID: the definition to delete, chosen from the list or set with an expression such as {{ $json.contractEventId }}.

Fetches a single contract event definition and returns its stored details. Useful as a check step rather than as an end in itself.

• Contract Event Name or ID: the identifier of the definition you want back.

Returns your contract event definitions page by page, with filters to narrow the set. This is the inventory view, not the onchain logs.

• Page Number and Page Size: required, and there is no Return All switch here, so loop if you want everything.
• Name, Contract Address, Event Name, Chain Name or ID: optional filters on the definitions returned.

Goes to the blockchain and returns the actual event logs matching a definition. This is the operation that gives you data, where the list operation only gives you definitions.

• Contract Event Name or ID: which definition to search with.
• Start Block and End Block: the block range to search from and to.
• Topics: name and value pairs that filter on indexed event parameters.

Edits an existing definition in place. Only its labels change, which means the identifier your other workflows use keeps working.

• Contract Event Name or ID: the definition to update, required.
• Name and Description: the updated name and description for the event definition, both optional.

Makes sure a set of contract methods is ready to use based on a chosen Prompt. Instead of creating each method by hand, you point at a prompt and let 1Shot prepare what goes with it.

• Prompt ID: the ID of the Prompt to assure contract methods from.
• Contract Address: required, and it can be pulled from the prompt if needed.
• Chain Name or ID: the chain the contract sits on.
• Wallet Name or ID: the wallet to use for the contract methods.

Produces the calldata for a contract method without sending anything. Some other contract methods expect that calldata as an input, which is the main reason this operation exists.

• Contract Method Name or ID: the method to encode.
• Parameters: a JSON object of the values passed to the method, as in {"amount": "10000"}.
• Authorization List: an optional list of ERC-7702 authorizations for the contract method.

Returns an estimate of what a contract method would cost in gas. Read only, so it changes nothing onchain and can run as often as you like.

• Contract Method Name or ID: the method being priced.
• Parameters: the JSON object of values, because the cost depends on what you pass.

Sends the transaction. This is the write operation of the node, and the one worth testing on a test chain before it ever runs on a schedule.

• Contract Method Name or ID and Parameters: what to call and with which values.
• Wallet ID: the wallet used for this execution, when you do not want the default one.
• Value: the amount of native token sent along with the method.
• Memo: optional text attached to the transaction, handy for reconciliation later.
• Gas Limit: the higher of this value and the estimate is what gets used.

Runs a contract method on the blockchain using a stored ERC-7710 delegation, so the transaction happens on behalf of another wallet. The delegation is what grants the right, and you name it in exactly one way.

• Delegation ID: the surest way to point at the right delegation.
• Delegator Wallet Address: the address of the delegator wallet instead of an ID.
• Delegation Data: a JSON delegation object treated as one time use and not stored for reuse. Only one of these three can be set.
• Contract Method Name or ID and Parameters: the call itself.

Bundles several contract methods into a single transaction. One submission, one set of gas, and a choice about what happens when one of the calls fails.

• Contract Methods: the collection of calls, each with its Contract Method Name or ID and its Parameters.
• Wallet Name or ID: the wallet used for the whole batch.
• Atomic: on, every call must succeed or the entire batch is rolled back.
• Memo and Gas Limit: optional text on the transaction, and the floor for the gas used.

Same batching, performed as a delegator. Several calls go out in one transaction on behalf of an address that delegated the right to act.

• Contract Methods and Wallet Name or ID: the calls and the wallet that submits them.
• Delegator Address, Delegation ID or Delegation Data: pick exactly one of the three to identify the delegation.
• Atomic: decides whether a single failure rolls the batch back.
• Authorization List: the ERC-7702 authorizations for the batch execution.

Returns a single smart contract method with its stored details. Nothing here is required, which is unusual for this node.

• Contract Method ID: the ID of the Contract Method you want to get. It is optional, so an empty value simply returns nothing useful rather than raising an error.

Pages through the contract methods you have defined, with filters that make the result usable. The Method Type filter is the one that saves the most time.

• Page Number and Page Size: required on every call.
• Method Type: Read, Write, or None to skip the filter.
• Name, Contract Address, Prompt ID, Chain Name or ID: the other optional filters.

Reads from a view or pure function on the contract. No transaction, no gas, just a value coming back into the workflow.

• Contract Method Name or ID: the read method to call.
• Parameters: the JSON object of arguments the function expects.

Plays the call against the current state of the chain and tells you whether it would succeed. Think of it as the dry run you put in front of every execute step.

• Contract Method Name or ID and Parameters: exactly what the execute step will receive.
• Gas Limit: optional, and the default gas limit applies when you leave it empty.

Runs a semantic search over 1Shot Prompts and returns the tools you can use in a dynamic workflow. Semantic means you describe what you want in words, not by exact name.

• Query: the search text, required.
• Chain Name or ID: an optional filter when you only care about one chain.

Returns 1Shot API transactions inside a time window, with a long list of optional filters. Every call is bounded in time, which is what makes it safe to schedule.

• After Time and Before Time: unix timestamps that frame the window, both required.
• Page Number and Page Size: also required.
• Status: Pending, Submitted, Completed, Retrying, Failed, or None.
• Wallet ID, Contract Method ID, API Credential ID, User ID, Memo, Chain Name or ID: the optional filters.

Pulls one specific Transaction back. Pair it with a wait or a loop when you want to follow a submission until its status settles.

• Transaction Name or ID: the Transaction ID you want to get, typically {{ $json.id }} carried over from the execute step.

A new Wallet is created and stays empty until you add funds to it. The name matters, because that is what shows up in the dropdowns of every other operation.

• Chain Name or ID: the chain the wallet belongs to, chosen from the list or set with an expression.
• Name: the name of the wallet, required.
• Description: an optional description of the wallet.

Deletes a Wallet. Nothing else is asked for, so treat the step as final and put whatever check you need in front of it.

• Wallet Name or ID: the wallet to delete, picked from the list or supplied with an expression such as {{ $json.walletId }}.

Looks up one Wallet from its identifier and hands back what 1Shot stores about it. The field is a plain string here, not a dropdown.

• Wallet Name or ID: the ID of the Wallet you want to get, update or delete, typed in directly or built with an expression.

Walks through the Wallets of a given chain, page by page. The chain filter is optional, so leaving it empty widens the result instead of breaking the call.

• Page Number and Page Size: both required.
• Chain Name or ID: an optional filter on the chain.
• Name: filters wallets by name.

Changes what 1Shot stores about an existing Wallet. The identifier does not move, so the workflows already pointing at it keep running.

• Wallet Name or ID: the wallet being modified, required.
• Name: the name of the wallet, required even for a simple edit.
• Chain Name or ID and Description: the two optional fields.