Running Agents
Agents are workflow orchestration glyphs that execute multi-step tasks.
How Agents Work
- You provide input parameters
- The agent sends data to a webhook endpoint
- External workflow (n8n, CrewAI, etc.) executes
- Results are returned to you
Agent Features
Webhooks
Agents communicate via HTTP webhooks:
- POST requests - Send data to external services
- Custom headers - Authentication and metadata
- Payload transformation - Format inputs for the endpoint
Async Execution
For long-running tasks:
- Polling - Agent checks for completion periodically
- Timeouts - Up to 180 seconds for complex workflows
- Retries - Automatic retry on transient failures
Multi-Step Workflows
Agents can orchestrate complex flows:
- Sequential task execution
- Parallel processing
- Conditional logic
- Data aggregation
Running an Agent
Step 1: Review Requirements
Check the agent’s input schema:
- Required fields (marked with *)
- Field types and formats
- Example values
Step 2: Fill Inputs
Complete the input form:
- Text inputs for queries/parameters
- Numbers for quantities/limits
- URLs for target resources
- File uploads if supported
Step 3: Execute
Click Run Agent:
- Inputs are sent to the webhook
- Progress updates appear in console
- Final results are displayed
Step 4: Monitor Progress
Watch the console for:
- Status updates
- Intermediate results
- Final output
Agent Output
Console View
Results displayed in terminal-style output:
- Timestamped log entries
- Status indicators (running, success, error)
- Final result payload
Structured Data
Agents often return JSON data:
{
"status": "success",
"result": {
"analysis": "...",
"recommendations": ["..."]
},
"metadata": {
"duration": 15000,
"steps_completed": 3
}
}Common Agent Use Cases
Trading Automation
- Execute trades based on signals
- Rebalance portfolios
- Monitor price movements
Data Pipelines
- Aggregate data from multiple sources
- Transform and clean data
- Store results in databases
Content Publishing
- Generate content with LLMs
- Format for different platforms
- Schedule and publish
Monitoring
- Watch blockchain events
- Alert on specific conditions
- Track wallet activities
Timeout and Retries
Timeouts
- Default: 60 seconds
- Maximum: 180 seconds
- Shown in glyph details
Retries
- Automatic retry on network errors
- Configurable retry count
- Exponential backoff
Error Handling
Common Errors
- Timeout: Workflow took too long
- Webhook Error: External service unavailable
- Invalid Input: Data format incorrect
What to Do
- Check your inputs are valid
- Try running again (transient errors)
- Contact the creator for persistent issues
Next Steps
Last updated on: