Otomato
  • OTOMATO
  • Overview
    • Platform Description
  • Otomato OS
    • How to set up the SDK
  • Smart Account ERC 4337
  • Product Guides
    • Smart Notification
    • Yield Optimiser
    • Builder Mode: Product Overview
      • Create An Agent
        • Triggers
          • Token transfer
          • Balance Check Trigger
          • On Chain Price Movement Trigger
          • Ethena Yield Trigger
          • Splice.fi
          • IONIC
          • Odos
          • Fear and greed index
          • IBIT Blackrock's Bitcoin ETF
        • Actions
          • Swap (odos)
          • Email
          • Discord
          • Slack
          • Transfer Action
          • IONIC
          • ODOS
          • 🟡Mode Network
          • Delay Action
        • Conditions
      • Execution History
  • Supported Chains
    • 🔵BASE
    • ⚪Ethereum
    • 🟡Mode Network
    • 🟣Oasis
Sapphire
  • Fundamentals
    • Use Cases
      • Inspiration wall
    • Roadmap
    • Team
  • Technical documentation
    • Architecture
Powered by GitBook
On this page
  1. Product Guides
  2. Builder Mode: Product Overview
  3. Create An Agent
  4. Actions

Transfer Action

The Transfer Action block allows users to automate the transfer of tokens within a blockchain network. This action can be configured to send specific tokens to designated addresses, making it a versatile tool for any workflow involving token transactions.

  1. Templates:

    • Users can select from predefined templates to quickly configure common transfer actions:

      • Transfer USDC: An example template for transferring USDC, showing a sample setup of transferring 100 USDC to a specified address (e.g., vitalik.eth on Mode network).

  2. Network:

    • Allows users to select the blockchain network on which the transfer will occur. Selecting the correct network is crucial to ensure that the transfer is executed within the intended environment (e.g., Ethereum, Binance Smart Chain, or Mode network).

  3. Contract Address:

    • Specifies the contract address of the token to be transferred. This field ensures that the automation targets the correct token within the network. Users can select or manually enter the token’s contract address to initiate a transfer of the specified token (e.g., USDC).

  4. To:

    • The recipient address for the transfer. This field allows users to specify the wallet address or ENS name where the tokens will be sent. Users should ensure that the recipient address is correctly entered to avoid misdirected transactions.

  5. Value:

    • Defines the amount of the token to transfer. For example, setting 100 would transfer 100 units of the selected token to the specified address. This field supports precise control over the transfer amount, making it suitable for workflows with specific transaction requirements.

By configuring these fields, you can automate token transfers with ease, ensuring efficient and accurate transactions within their workflows. The Transfer Action block is ideal for processes that require recurring transfers, such as payouts, asset rebalancing, or conditional transfers based on other workflow events.

PreviousSlackNextIONIC

Last updated 7 months ago