Fracttal ETL Hub Documentation
Welcome to the complete documentation of the Fracttal ETL Hub, an advanced data integration platform that enables efficient and scalable connection between multiple enterprise systems.
What is Fracttal ETL Hub?
Fracttal ETL Hub is an ETL (Extract, Transform, Load) solution based on JSON configurations that implements the JSON-RPC 2.0 protocol. The platform offers:
- 18+ native connection types to enterprise systems
- 40+ transformation operators based on JSON Logic
- Dynamic event system for complex workflows
- Orchestration with Apache Airflow 2.9.3
- Automatic validation of configurations
Atomic Design Methodology
Documentation organized following Atomic Design, adapted for ETL:
ATOMS - Basic Elements
-
APIs
Available connectors: Database, Fracttal API, HTTP/REST, SOAP, Google Sheets, Email
-
Operators
Basic operators: format_date, case, rename, substring, switch
-
Data Types
Core types: String, Number, Boolean, Array
MOLECULES - Functional Patterns
-
Source Patterns
Database Filter, API Pagination, File Reader - Optimized data extraction
Source Patterns (coming soon)
-
Transform Chains
Data Cleaning, Date Formatting, Text Processing - Data transformation
-
Target Outputs
Database Insert, API Send, File Export - Processed data loading
Outputs (coming soon)
ETL - Complete Flows
-
Business Cases
Order Synchronization, User Migration, Inventory Update
Business Cases (coming soon)
-
Integration Patterns
CRM to ERP, API to Database, File to API
Integrations (coming soon)
-
Workflows
Daily Reports, Real-time Sync, Batch Processing
Workflows (coming soon)
Quick Guide
1. Getting Started
2. Available Connections
Explore all supported connections organized by category:
- Database: SQL Server, MySQL, PostgreSQL, Oracle
- Cloud: AWS, Azure, Google Cloud
- Communication: Email, SMS, WhatsApp
- Management: JIRA, Trello
- APIs: HTTP/REST, SOAP, Fracttal API
- Files: Google Sheets, Google Docs
3. Transformations
API Reference
Quick Tips
- Use the search bar to find specific connections
- All configurations follow the JSON-RPC 2.0 schema
- The production environment is
production - UUIDs must be unique per configuration
Important
Remember to validate all configurations before deploying to production.