Skip to main content

No-Code Editor

Create complex automations visually using the no-code editor. Drag and drop components to build workflows without writing code.

🎨 Editor Interface​

Main Layout​

  • Left Sidebar: Available components (Hooks, Actions, Conditions)
  • Central Area: Canvas where you build the automation
  • Right Sidebar: Properties and settings of the selected component
  • Top Bar: Automation name, status, and controls

Available Components​

🔗 Hooks (Triggers)​

  • Crypto Charge Paid: Confirmed crypto payment
  • PIX Charge Paid: Paid PIX
  • Ramp Completed: On/off-ramp completed
  • Scheduler: Periodic execution
  • DeFi Position Updated: DeFi position updated

⚡ Actions​

  • Crypto Transfer: Transfer crypto
  • Cross Swap: Cross-chain swap
  • On-chain Swap: On-chain swap
  • Ramp Off-ramp: Convert crypto to fiat
  • EVM Wallet Balance: Check balance
  • DeFi Operations: DeFi operations
  • Numeric Split: Split values

🔧 Conditions​

  • If/Then/Else: Conditional logic
  • Compare Values: Compare values
  • Check Balance: Check balance

🚀 How to Create an Automation​

Step 1: Add Hook​

  1. Drag a Hook from the left sidebar
  2. Drop it into the central canvas area
  3. Configure properties in the right sidebar

Step 2: Add Actions​

  1. Drag an Action from the sidebar
  2. Connect it to the Hook with a line
  3. Configure the Action parameters

Step 3: Configure Connections​

  1. Click on the Hook to select it
  2. Drag the connection line to the Action
  3. Configure dynamic values

Step 4: Test and Save​

  1. Test the automation with sample data
  2. Save when satisfied
  3. Activate to start executing

🔗 Connection System​

Dynamic Values​

Use the Field Selector to connect data between components:

{events.hooks.crypto_charge_paid.amount}
{events.actions.123.to_amount}
{events.triggers.scheduler_456.data.balance}

Field Types​

  • wallet: Wallets and addresses
  • token: Tokens and cryptocurrencies
  • amount: Numeric values
  • numeric: Numeric fields
  • beneficiary: Beneficiaries
  • any: Any field

Smart Filters​

The Field Selector shows only compatible fields:

  • ✅ Included: Fields of the correct type
  • ❌ Excluded: Incompatible fields
  • ⏰ Temporal: Only previous events

📋 Practical Examples​

1. Simple Auto-Transfer​

Hook: crypto.charge.paid
  ↓
Action: crypto.transfer.new
  - Source Wallet: {events.hooks.crypto_charge_paid.wallet_address}
  - Destination Wallet: Reserve wallet
  - Token: {events.hooks.crypto_charge_paid.token.id}
  - Amount: {events.hooks.crypto_charge_paid.amount}

2. Cross-Chain Swap​

Hook: crypto.charge.paid
  ↓
Action: cross.swap.new
  - Source Token: {events.hooks.crypto_charge_paid.token.id}
  - Destination Token: USDC
  - Amount: {events.hooks.crypto_charge_paid.amount}
  - Destination Address: USDC Wallet

3. Distribution with Numeric Split​

Hook: crypto.charge.paid
  ↓
Action: transform.numeric_split
  - Source Value: {events.hooks.crypto_charge_paid.amount}
  - Allocations:
    - 50% → Reserve
    - 30% → Investment
    - 20% → Expenses

4. Balance Monitoring​

Hook: scheduler (EvmWallet)
  ↓
Action: evm_wallet.get_token_balance
  - Wallet: Specific wallet
  - Token: USDC
  ↓
Condition: If balance < $1000
  ↓
Action: Send notification

🎯 Field Selector​

How to Use​

  1. Click on an input field
  2. Select "Use dynamic value"
  3. Choose the desired field from the list
  4. Confirm the selection

Interface​

  • Field Tree: Organized by event type
  • Search: Filter fields by name
  • Filters: By field type and compatibility
  • Preview: See value before selecting

Tips​

  • Bold Fields: Most relevant to the type
  • Icons: Indicate field type
  • Descriptions: Explain what each field contains

🔧 Advanced Configuration​

Conditions​

Add conditional logic to automations:

IF {events.hooks.crypto_charge_paid.amount} > 1000
  THEN crypto.transfer.new (VIP wallet)
ELSE
  crypto.transfer.new (normal wallet)

Multiple Actions​

Connect multiple actions to the same hook:

Hook: crypto.charge.paid
  ├── Action 1: crypto.transfer.new
  ├── Action 2: cross.swap.new
  └── Action 3: send.notification

Action Chains​

Connect actions in sequence:

Hook: crypto.charge.paid
  ↓
Action 1: evm_wallet.get_token_balance
  ↓
Action 2: cross.swap.new (using balance from Action 1)
  ↓
Action 3: crypto.transfer.new (using result from Action 2)

🛡️ Validation and Testing​

Automatic Validation​

  • Connections: Checks if fields are compatible
  • Types: Confirms correct data types
  • Required: Alerts about required fields
  • Limits: Checks security limits

Automation Test​

  1. Click on "Test Automation"
  2. Choose sample data
  3. Execute step by step
  4. Verify results

Simulation​

  • Dummy Data: Use sample data
  • Step-by-Step Execution: See each step
  • Detailed Logs: Track the process
  • Results: See what would happen

📊 Monitoring​

Automation Status​

  • 🟢 Active: Executing normally
  • 🟡 Paused: Temporarily disabled
  • 🔴 Error: Configuration problem
  • ⏸️ Disabled: Not executing

Execution Logs​

  • Timestamp: When it was executed
  • Trigger: What started the execution
  • Actions: Which actions were executed
  • Result: Success or failure
  • Details: Full logs

Metrics​

  • Executions per Day: How many times executed
  • Success Rate: Percentage of successes
  • Average Time: Duration of executions
  • Last Execution: When executed last time

🆘 Troubleshooting​

Automation does not execute​

  1. Check if it is active
  2. Confirm if hook was activated
  3. Check logs for errors
  4. Test manually

Field does not appear in selector​

  1. Check if field has automation_type
  2. Confirm if compatible with type
  3. Check if event happens before action
  4. Test with sample data

Connection error​

  1. Check if types are compatible
  2. Confirm if field exists
  3. Test with fixed values first
  4. Check error logs

Slow performance​

  1. Simplify complex automations
  2. Reduce number of actions
  3. Optimize conditions
  4. Monitor executions

💡 Tips and Best Practices​

Automation Design​

  • Start simple: Create basic automations first
  • Test frequently: Validate each step
  • Use descriptive names: Facilitate maintenance
  • Document: Add clear descriptions

Performance​

  • Avoid loops: Do not create circular dependencies
  • Optimize conditions: Use efficient filters
  • Monitor executions: Track performance
  • Clean automations: Remove unused automations

Security​

  • Test with small amounts: Validate before using high values
  • Configure limits: Set security limits
  • Monitor executions: Track regularly
  • Have backup: Keep previous versions

Next steps: Explore the Event Structure to better understand the available data.