automation/

NeoFlow Service

Task neoflow service for the Neo Service Layer.

Overview

The NeoFlow service provides trigger-based task neoflow for smart contracts. Users can register triggers with conditions, and the TEE monitors these conditions continuously, executing callbacks when conditions are met.

Architecture

┌──────────────┐     ┌──────────────┐     ┌──────────────┐
│    User      │     │ NeoFlow      │     │ User Contract│
│              │     │ Service (TEE)│     │              │
└──────┬───────┘     └──────┬───────┘     └──────┬───────┘
       │                    │                    │
       │ Register Trigger   │                    │
       │───────────────────>│                    │
       │                    │                    │
       │                    │ Monitor Condition  │
       │                    │                    │
       │                    │ Condition Met!     │
       │                    │                    │
       │                    │ Execute Callback   │
       │                    │───────────────────>│

Trigger Types

NeoFlow supports two trigger sources:

• Supabase triggers (managed via /triggers): currently only cron triggers are executed, and they execute webhook actions.
• On-chain anchored tasks (optional): tasks registered in the platform AutomationAnchor contract can be executed when chain execution is enabled. Anchored tasks support cron and price trigger specs and are executed via txproxy.

API Endpoints

Request/Response Types

Create Trigger (Cron)

POST /triggers
{
    "name": "Daily Report",
    "trigger_type": "cron",
    "schedule": "0 9 * * *",
    "action": {
        "type": "webhook",
        "url": "https://hooks.miniapps.com/callback",
        "method": "POST"
    }
}

Trigger Response

{
    "id": "trigger-123",
    "name": "Daily Report",
    "trigger_type": "cron",
    "schedule": "0 9 * * *",
    "enabled": true,
    "last_execution": "2025-12-07T09:00:00Z",
    "next_execution": "2025-12-08T09:00:00Z",
    "created_at": "2025-12-01T00:00:00Z"
}

Cron Expression Format

Standard 5-field cron format:

┌───────────── minute (0 - 59)
│ ┌───────────── hour (0 - 23)
│ │ ┌───────────── day of month (1 - 31)
│ │ │ ┌───────────── month (1 - 12)
│ │ │ │ ┌───────────── day of week (0 - 6) (Sunday = 0)
│ │ │ │ │
* * * * *

Examples:

• 0 9 * * * - Every day at 9:00 AM
• */15 * * * * - Every 15 minutes
• 0 0 * * 1 - Every Monday at midnight
• 0 0 1 * * - First day of every month

Fee Structure

Data Layer

The NeoFlow service uses a service-specific Supabase repository for database operations.

Package Structure

services/automation/
├── marble/              # Enclave runtime + HTTP handlers + workers
├── supabase/            # Automation persistence (triggers + executions)
└── README.md

Neo N3 chain bindings live in infrastructure/chain (RPC, typed contract reads, event parsing). All on-chain writes are delegated to services/txproxy (allowlisted sign+broadcast).

Repository Interface

import neoflowsupabase "github.com/R3E-Network/service_layer/services/automation/supabase"

// Create repository
neoflowRepo := neoflowsupabase.NewRepository(baseRepo)

// Operations
err := neoflowRepo.CreateTrigger(ctx, &neoflowsupabase.Trigger{...})
triggers, err := neoflowRepo.GetTriggers(ctx, userID)
err := neoflowRepo.UpdateTrigger(ctx, trigger)
err := neoflowRepo.CreateExecution(ctx, &neoflowsupabase.Execution{...})
executions, err := neoflowRepo.GetExecutions(ctx, triggerID, limit)

Data Models

Testing

go test ./services/automation/... -v -cover

Current test coverage: 11.1%

Version

• Service ID: neoflow
• Version: 2.0.0