What you are building in WOODY.IO?

What you are building: a self-governing data integration process

In WOODY.IO, you build a self-governing data integration process: a repeatable process that takes data from a source, applies structure and rules, and writes it into a destination system in a controlled way (Import > Validate > Approve if required > Persist).

The building blocks of a basic self-governing data integration process

1. Application
   An Application is where your processes live. It contains your configuration (connections, metamodels, templates, roles) and the imports executed by users. Only instance admins (“Super Admins”) can create new Applications. 
2. Connection 
   A Connection defines how WOODY.IO connects to a system used as a source and/or destination (e.g., MS SQL, ADLS, Snowflake, Databricks, DataLake, AW). Saving a connection also verifies it by attempting to connect.
3. Metamodel
   A Metamodel defines one process: the destination connection, the structure (entities/fields), and the behavior (rules/transformations/lookups) that will be applied during imports. Publishing creates a version so running imports are not broken by later changes.
4. Entities and Fields
   An Entity defines how the data should look when persisted.
   • Entity: the target dataset structure (like a table or dataset).
   • Field: the columns and properties (e.g., required, key, identity, lookup usage).
5. Import Template
   An Import Template defines how the data will be imported:
   • Import Type (file upload, SQL-based import, ADLS, Snowflake, Databricks, Live Edit, etc.)
   • Transaction Type (Merge/Insert/Update/Replace/Delete) 
6. Import
   An Import is one run of the process using an Import Template. The Import moves through stages such as Load > Validation > Approval (if enabled) > Persist.

Your process building always starts on the Management page.

If you have any further questions, please feel free to Contact Us.