Global Configurator Overview
Global Configurator is the central configuration library for the Qinfinite platform. It stores everything your automations need to connect to external systems, look up shared values, and access common files and certificates — all in one secure, searchable place.
Instead of repeating the same setup across dozens of workflows, you configure it once in Global Configurator and reuse it everywhere. When something changes — a password, an API token, a data file — you update it in one place and every automation that references it picks up the change automatically.
The Basic Idea
What It Manages
Global Configurator organises six types of shared resources:
| Resource | What It Stores | Why It Matters |
|---|---|---|
| Connections | Credentials and settings for 100+ system types — databases, cloud services, email, messaging, enterprise apps, AI platforms, and more | Automations can reach any external system without embedding passwords in workflows |
| Global Variables | Shared key-value pairs reusable across all automations. Supports text, numbers, dates, booleans, lists, and maps | Change a token or threshold once and every workflow that uses it updates immediately |
| Datasets | Reusable structured data in JSON, CSV, XML, Properties, or Text format, with full version history | Teams can maintain lookup tables, configuration bundles, or test data centrally |
| Files | Shared files uploaded once and versioned. Stored in AWS S3 or MinIO with checksum validation | Templates, reference files, and attachments are always available to any automation |
| Certificates | X.509 certificates with automatic metadata extraction, expiry tracking, and revocation checking | No more surprise outages from an expired certificate — the platform warns you first |
| API Management | Postman-style API suites with request collections, cURL import/export, OAuth2 management, and execution history | Teams can test and document API integrations directly inside the platform |
How It Fits with Automation Hub
Global Configurator and Automation Hub are designed to work together. Automation Hub is where you build and run workflows. Global Configurator is where you store the configuration those workflows depend on.
When a workflow step needs to query a database, it references the saved connection by name. When it needs an API token, it references a global variable. This clean separation means your workflow logic stays readable and your credentials stay protected.
Why It Matters
| Without Global Configurator | With Global Configurator |
|---|---|
| The same database credentials are copy-pasted into ten different workflows | One connection record is shared by all ten workflows |
| Updating an API token means editing every workflow that uses it | Update the global variable once and all workflows pick it up |
| Moving from QA to production requires manually recreating every setting | Export from QA, import to production — done in minutes |
| Nobody knows which workflows will break if a shared setting changes | References track exactly where each asset is used |
| Certificate expiry causes unexpected outages | Daily and scheduled checks alert you before expiry becomes a problem |
| Team members duplicate work and make inconsistent choices | Everyone draws from the same, well-named shared library |
Common Examples
| Scenario | How Global Configurator Helps |
|---|---|
| Multiple automations need to query the same production database | Create one database connection with the host, port, credentials, and SSL settings. Every workflow references it by name |
| An API token rotates monthly and is used in 20 workflows | Store the token as an encrypted global variable. Update it once each month — all 20 workflows get the new value automatically |
| A workflow needs to look up country codes or product categories | Create a dataset with a JSON or CSV file. Activate the version you want, and reference it in any workflow as a stable data source |
| A team shares a reporting template across several automations | Upload the template as a versioned file. Automations always fetch the current active version |
| An SSL certificate for an integration partner is approaching expiry | Global Configurator tracks the expiry date and alerts the team with enough lead time to renew |
Security
Security is built into Global Configurator at every level.
Encryption at rest Password and secret fields are automatically detected from connection and variable templates. They are encrypted using HashiCorp Vault's Transit secrets engine before being stored in the database. Plain-text passwords never touch the database.
Role-based access control
Permissions follow a GlobalConfigurator:Resource:Action format, giving administrators fine-grained control over who can view, create, edit, delete, or test each type of resource. A developer can use connections without being able to delete them.
Full audit trail Every record tracks who created it and who last changed it, with timestamps. If something breaks after a configuration change, you can see exactly what changed and who made the change.
Import and export controls All six resource types support controlled export and import, supporting safe environment promotion from Dev to QA to Staging to Production. Name conflicts are handled automatically — no accidental overwrites.
Sensitive values encrypted by Vault cannot be read in plain text by anyone who does not have the appropriate Vault access. This is intentional. If you need to rotate a credential, edit the connection or variable and save the new value — do not try to recover the old one.
Section Guide
Use the links below to learn about each area of Global Configurator:
- Connections — credentials and settings for 100+ external system types
- Global Variables — shared key-value pairs, including encrypted secrets
- Datasets — versioned structured data reusable across workflows
- Files — uploaded and versioned shared files
- Certificates — X.509 certificate tracking, expiry alerts, and revocation checks
- API Management — Postman-style API suites, cURL import/export, and execution history
- Import and Export — moving configuration safely between environments