Unified Input/Output System

Enable seamless data exchange between events across Python, Node.js, and Bash scripts with standardized functions and API integration.

Overview

Core Capabilities

The Unified Input/Output System provides a consistent way to pass data between events and workflows, regardless of the programming language. This enables powerful data processing pipelines and external system integration.

Cross-Language Support

Works consistently across Python, Node.js, and Bash scripts

API Integration

Accept input data via REST API endpoints for external integrations

Workflow Chaining

Automatic data flow between connected workflow nodes

Using cronium.input()

The cronium object is automatically injected into every script. No imports, requires, or sourcing needed - just start using cronium.input() and cronium.output() immediately.

Accessing Input Data

# cronium is automatically available - no imports needed!

# Access input data directly
input_data = cronium.input()
print(f"Received: {input_data}")

# Access specific fields
user_id = input_data.get('user_id', 'unknown')
action = input_data.get('action', 'default')

# Assign to new variable
new_input = cronium.input()

Automatic Injection

• Python: cronium object available globally
• Node.js: cronium object available globally
• Bash: cronium_input() and cronium_output() functions available
• Automatic JSON parsing and error handling
• Returns empty object if no input provided

Using cronium.output()

Set output data using the simple cronium.output() function. This data can be accessed by subsequent workflow nodes or retrieved via API. The cronium object is automatically available in all scripts.

Setting Output Data

# cronium is automatically available - no imports needed!

# Create output data
output_data = {
    "success": True,
    "message": "Processing completed",
    "results": {
        "processed_items": 42,
        "total_time": "2.5s"
    },
    "next_action": "send_notification"
}

# Set output for next workflow node
cronium.output(output_data)

Standard Logging

Use standard logging methods in each language. The cronium object is automatically available if you need to access input data within your logging.

Logging Examples

# Use standard Python print for logging
print("Starting data processing...")
print(f"Processing {len(items)} items")
print("Data processing completed successfully")

# Access input if needed (cronium automatically available)
input_data = cronium.input()
if input_data.get('verbose'):
    print(f"Input received: {input_data}")

Using cronium.event()

Access event metadata using the cronium.event() function. This returns information about the current event such as its ID, name, type, server details, and execution statistics.

Accessing Event Metadata

# cronium is automatically available - no imports needed!

# Access event metadata
event_data = cronium.event()
print(f"Event ID: {event_data.get('id')}")
print(f"Event Name: {event_data.get('name')}")
print(f"Event Type: {event_data.get('type')}")

# Use event info in processing
if event_data.get('type') == 'PYTHON':
    print("Running Python script")
    
# Check server information
server = event_data.get('server')
if server:
    print(f"Running on server: {server.get('name')}")

Available Event Data

• id: Unique event identifier
• name: Event display name
• description: Event description
• type: Script type (PYTHON, NODEJS, BASH)
• runLocation: Execution location (LOCAL, REMOTE)
• server: Server details (if running remotely)
• successCount/failureCount: Execution statistics
• createdAt/updatedAt: Timestamps

API Integration

Passing Input via API

Execute events with custom input data using the REST API endpoint

HTTP Request Format

POST /api/events/{event_id}/execute
Content-Type: application/json
Authorization: Bearer YOUR_API_TOKEN

{
  "input": {
    "user_id": 123,
    "action": "process_data",
    "data": {
      "items": ["item1", "item2", "item3"],
      "priority": "high"
    },
    "metadata": {
      "request_id": "req_12345",
      "timestamp": "2025-06-06T22:00:00Z"
    }
  }
}

Example API Calls

API Integration Examples

import requests

# Execute event with input data
response = requests.post(
    'https://your-cronium-instance.com/api/events/42/execute',
    headers={
        'Authorization': 'Bearer YOUR_API_TOKEN',
        'Content-Type': 'application/json'
    },
    json={
        "input": {
            "user_id": 123,
            "action": "process_data",
            "data": {"items": ["item1", "item2"]}
        }
    }
)

result = response.json()
print(f"Execution result: {result}")

Quick Reference

Quick Start Examples

# cronium is automatically available - no imports needed!

# Access input
user_data = cronium.input()
print(f"Processing for user: {user_data.get('name', 'unknown')}")

# Access event metadata
event_data = cronium.event()
print(f"Running event: {event_data.get('name')} (ID: {event_data.get('id')})")

# Set output
cronium.output({"result": "success", "processed": True})

Best Practices

Data Structure Guidelines

Use JSON-compatible data types (objects, arrays, strings, numbers, booleans)
Include meaningful field names and consistent structure
Add metadata like timestamps and request IDs for traceability
Validate input data before processing

Error Handling

Always check if input data exists before accessing fields
Provide default values for optional fields
Include error information in output when processing fails
Use try-catch blocks to handle exceptions gracefully

Performance Considerations

Keep input/output data reasonably sized (< 1MB recommended)
Avoid deeply nested objects when possible
Use efficient data processing algorithms
Clean up temporary data when no longer needed

Troubleshooting

Common Issues

Runtime helper not found

The cronium object is automatically available in containerized execution. No imports needed.

cronium.input is empty

Check if input is being passed via API or if workflow connections are properly configured.

JSON output errors

Validate JSON structure before calling cronium.output(). Use JSON validators or linters.

Debugging Tips

Use standard logging (print, console.log, echo) to output debug information
Check execution logs for runtime errors and output
Print cronium.input to verify data structure
Test scripts individually before adding to workflows
Use proper error handling with try-catch blocks

Unified Input/Output System

Enable seamless data exchange between events across Python, Node.js, and Bash scripts with standardized functions and API integration.

Overview

Core Capabilities

Cross-Language Support

Works consistently across Python, Node.js, and Bash scripts

API Integration

Accept input data via REST API endpoints for external integrations

Workflow Chaining

Automatic data flow between connected workflow nodes

Using cronium.input()

The cronium object is automatically injected into every script. No imports, requires, or sourcing needed - just start using cronium.input() and cronium.output() immediately.

Accessing Input Data

# cronium is automatically available - no imports needed!

# Access input data directly
input_data = cronium.input()
print(f"Received: {input_data}")

# Access specific fields
user_id = input_data.get('user_id', 'unknown')
action = input_data.get('action', 'default')

# Assign to new variable
new_input = cronium.input()

Automatic Injection

• Python: cronium object available globally
• Node.js: cronium object available globally
• Bash: cronium_input() and cronium_output() functions available
• Automatic JSON parsing and error handling
• Returns empty object if no input provided

Using cronium.output()

Setting Output Data

# cronium is automatically available - no imports needed!

# Create output data
output_data = {
    "success": True,
    "message": "Processing completed",
    "results": {
        "processed_items": 42,
        "total_time": "2.5s"
    },
    "next_action": "send_notification"
}

# Set output for next workflow node
cronium.output(output_data)

Standard Logging

Use standard logging methods in each language. The cronium object is automatically available if you need to access input data within your logging.

Logging Examples

# Use standard Python print for logging
print("Starting data processing...")
print(f"Processing {len(items)} items")
print("Data processing completed successfully")

# Access input if needed (cronium automatically available)
input_data = cronium.input()
if input_data.get('verbose'):
    print(f"Input received: {input_data}")

Using cronium.event()

Access event metadata using the cronium.event() function. This returns information about the current event such as its ID, name, type, server details, and execution statistics.

Accessing Event Metadata

# cronium is automatically available - no imports needed!

# Access event metadata
event_data = cronium.event()
print(f"Event ID: {event_data.get('id')}")
print(f"Event Name: {event_data.get('name')}")
print(f"Event Type: {event_data.get('type')}")

# Use event info in processing
if event_data.get('type') == 'PYTHON':
    print("Running Python script")
    
# Check server information
server = event_data.get('server')
if server:
    print(f"Running on server: {server.get('name')}")

Available Event Data

• id: Unique event identifier
• name: Event display name
• description: Event description
• type: Script type (PYTHON, NODEJS, BASH)
• runLocation: Execution location (LOCAL, REMOTE)
• server: Server details (if running remotely)
• successCount/failureCount: Execution statistics
• createdAt/updatedAt: Timestamps

API Integration

Passing Input via API

Execute events with custom input data using the REST API endpoint

HTTP Request Format

POST /api/events/{event_id}/execute
Content-Type: application/json
Authorization: Bearer YOUR_API_TOKEN

{
  "input": {
    "user_id": 123,
    "action": "process_data",
    "data": {
      "items": ["item1", "item2", "item3"],
      "priority": "high"
    },
    "metadata": {
      "request_id": "req_12345",
      "timestamp": "2025-06-06T22:00:00Z"
    }
  }
}

Example API Calls

API Integration Examples

import requests

# Execute event with input data
response = requests.post(
    'https://your-cronium-instance.com/api/events/42/execute',
    headers={
        'Authorization': 'Bearer YOUR_API_TOKEN',
        'Content-Type': 'application/json'
    },
    json={
        "input": {
            "user_id": 123,
            "action": "process_data",
            "data": {"items": ["item1", "item2"]}
        }
    }
)

result = response.json()
print(f"Execution result: {result}")

Quick Reference

Quick Start Examples

# cronium is automatically available - no imports needed!

# Access input
user_data = cronium.input()
print(f"Processing for user: {user_data.get('name', 'unknown')}")

# Access event metadata
event_data = cronium.event()
print(f"Running event: {event_data.get('name')} (ID: {event_data.get('id')})")

# Set output
cronium.output({"result": "success", "processed": True})

Best Practices

Data Structure Guidelines

Use JSON-compatible data types (objects, arrays, strings, numbers, booleans)
Include meaningful field names and consistent structure
Add metadata like timestamps and request IDs for traceability
Validate input data before processing

Error Handling

Always check if input data exists before accessing fields
Provide default values for optional fields
Include error information in output when processing fails
Use try-catch blocks to handle exceptions gracefully

Performance Considerations

Keep input/output data reasonably sized (< 1MB recommended)
Avoid deeply nested objects when possible
Use efficient data processing algorithms
Clean up temporary data when no longer needed

Troubleshooting

Common Issues

Runtime helper not found

The cronium object is automatically available in containerized execution. No imports needed.

cronium.input is empty

Check if input is being passed via API or if workflow connections are properly configured.

JSON output errors

Validate JSON structure before calling cronium.output(). Use JSON validators or linters.

Debugging Tips

Use standard logging (print, console.log, echo) to output debug information
Check execution logs for runtime errors and output
Print cronium.input to verify data structure
Test scripts individually before adding to workflows
Use proper error handling with try-catch blocks