Connecting Data Sources

Connecting data sources is the foundation of a stable and scalable analytics architecture. By centralizing all database, API, and file connections within the Builder’s Sources area, organizations ensure transparency, reliability, and controlled schema management. With built-in connection testing, schema cache synchronization, and secure authentication options, Noreja enables seamless integration of operational systems into a consistent process intelligence environment—ensuring that every analysis starts with trusted, up-to-date data.

Overview

Managing your data sources effectively is the cornerstone of a reliable analytics workflow. In this guide, we’ll walk through accessing the Sources screen, understanding the information at a glance, keeping your schemas in sync, and adding new connections—all wrapped in a smooth, narrative flow that highlights why each step matters.

Accessing Your Sources

When you first arrive in the Builder, look to the main menu on the left and select Builder, then click Sources. Instantly, you’ll see every data source you’ve ever registered—no more hunting through hidden settings or terminal commands. This single page is your control center for connecting, testing, and maintaining all of the systems that power your insights.

What You See—and Why It Matters

At the heart of the Sources screen is a clear, tabular view of all your connections. Each row tells a story:

Name
A free-form label, chosen by you, that sits front and center. Whether it’s prod_orders_db or stripe_payments_api, a thoughtful name turns an otherwise cryptic list into a friendly roster you recognize at a glance.

Connection Type
Under the hood, this reveals the technology in use—PostgreSQL, MySQL, REST API, and so on. Immediately you know which protocols and drivers are at work, so you can troubleshoot the right layer.

Created & Last Modified
Two timestamps bookmark the life of each source: when it joined your universe and when you last tuned it. These dates help you track configuration drift and audit changes over time.

Status
A quick-glance indicator of whether the last connection test passed. Green means “go ahead”—everything’s talking to each other. Red means “hold on”—there’s an issue to address.

Actions
Four handy buttons let you edit configurations, rerun tests, delete sources, or—crucially—renew the schema cache. Each action is just one click away, no menus to navigate.

Keeping Schemas in Sync

Behind the scenes, the Builder caches schema metadata (tables, columns, data types) for speed. But databases are living things: you add tables, rename columns, tweak data types. When the physical schema changes, the cache can fall out of date, leading to missing tables in your queries or SQL errors in downstream models.

That’s where Renew Cache comes in. Click it, and the Builder:

Reads your source’s current schema.
Updates its internal cache.
Makes every new or altered table and column available to your flows.

Editing, Testing, Deleting

From the same Actions menu:

Edit lets you tweak hostnames, ports, or credentials in situ—without starting from scratch.

Test immediately verifies connectivity; a failed test surfaces network issues or bad credentials before they wreak havoc.

Delete removes the source and its metadata forever, so double-check that no Entities still depend on it before you click.

Adding a New Source

Ready to onboard another system? A single ⁺ Add Source button sits just below the table, beckoning you to click. You’ll be guided through a simple, step-by-step form:

Name your source—make it memorable.

Choose a Connection Type—relational database, REST API, CSV file, or one of our other supported options.

Supply the Host (IP or URL) and Port (default ports are prefilled for convenience).

Select your Authentication Mode: username/password, OAuth, API key, or another supported method.

Toggle Use SSL if you need an encrypted channel.

Enter your Credentials (and database name for relational sources).

Hit Create—the Builder will immediately run a test and let you know if everything is configured correctly.

If the test fails, you’ll receive clear, actionable error messages. Correct typos, verify network rules, adjust permissions, and retry.

Best Practices to Keep You Smoothly Sailing

Naming Conventions: Prefix with environment (dev_, stg_, prod_) and suffix with region (_eu_central, _us_west) to keep things orderly.

Least-Privilege Credentials: Grant only the access you need. Rotate passwords and keys regularly.

SSL Everywhere: Encrypt data in transit, especially across public networks. Troubleshoot cert errors by checking your CA chain.

By following these steps and tips, your data sources will stay healthy, up to date, and ready to feed the next great analysis or machine-learning pipeline. Happy building!