Skip to main content

Create Client

Establishes a connection to a blockchain network via an RPC endpoint and initializes a Web3 client with wallet credentials.

Common Properties​

  • Name - The custom name of the node.
  • Color - The custom color of the node.
  • Delay Before (sec) - Waits in seconds before executing the node.
  • Delay After (sec) - Waits in seconds after executing node.
  • Continue On Error - Automation will continue regardless of any error. The default value is false.
info

If the ContinueOnError property is true, no error is caught when the project is executed, even if a Catch node is used.

Inputs​

  • RPC URL - WebSocket (ws://, wss://) or HTTP (http://, https://) RPC URL for the blockchain node. This is the endpoint your automation will use to communicate with the blockchain.
  • Chain ID - The unique identifier of the blockchain network (e.g., 1 for Ethereum mainnet, 137 for Polygon, 56 for BSC).

Output​

  • Client ID - A unique identifier for this Web3 client connection. Use this ID with all other Web3 nodes to reference this connection.

Options​

  • Encrypted Private Key - The wallet's private key encrypted using AES encryption. Store this in Robomotion's credential vault for security.
  • AES Key - The AES encryption key used to decrypt the private key. Store this in the credential vault.

How It Works​

The Create Client node establishes a blockchain connection and prepares your wallet for transactions. When executed, the node:

  1. Validates the RPC URL and Chain ID
  2. Retrieves and decrypts the encrypted private key using the AES key
  3. Creates a Web3 client connection to the specified RPC endpoint
  4. Initializes the wallet for signing transactions
  5. Returns a Client ID for use with other Web3 nodes

Requirements​

  • A valid RPC endpoint URL (from providers like Infura, Alchemy, QuickNode, or your own node)
  • The correct Chain ID for your target network
  • An encrypted wallet private key stored in credentials
  • The corresponding AES key for decryption

Common Chain IDs​

  • 1 - Ethereum Mainnet
  • 5 - Goerli Testnet
  • 11155111 - Sepolia Testnet
  • 137 - Polygon Mainnet
  • 80001 - Polygon Mumbai Testnet
  • 56 - BNB Smart Chain Mainnet
  • 97 - BNB Smart Chain Testnet

Error Handling​

The node will return errors for:

  • Empty or invalid RPC URL
  • Invalid or inaccessible RPC endpoint
  • Missing or incorrect Chain ID
  • Invalid encrypted private key format
  • Decryption failures
  • Network connection issues

Security Best Practices​

  • Always store private keys encrypted in Robomotion's credential vault
  • Never hardcode private keys or AES keys in your flow
  • Use separate wallets for testing and production
  • Monitor wallet permissions and transaction activity
  • Use testnet networks for development and testing

Example​

Setting up an Ethereum mainnet connection:

Inputs:

  • RPC URL: wss://mainnet.infura.io/ws/v3/YOUR_PROJECT_ID
  • Chain ID: 1

Options:

  • Encrypted Private Key: (stored in credential vault)
  • AES Key: (stored in credential vault)

Output:

  • Client ID: 7e8f9a0b-1c2d-3e4f-5a6b-7c8d9e0f1a2b (use this in subsequent nodes)

For Polygon automation:

Inputs:

  • RPC URL: https://polygon-rpc.com
  • Chain ID: 137
tip

WebSocket connections (wss://) are recommended for real-time monitoring and event subscriptions. Use HTTP connections (https://) for simple queries and transactions.

warning

Keep your Client ID secure within your flow. Anyone with access to the client can execute transactions using the associated wallet.