Concepts

Ecosystem is built around connected concepts: a trigger starts a workflow, and each execution produces a trace; environments isolate deployments, dictionaries parameterize values, authentication methods secure access, and resources / Apps organize the business scope.

Workflows and triggers

• Trigger — the entry point of a workflow: defines when it starts, how data is received and which data is passed along. A workflow is always associated with a single trigger. → Introduction to triggers
• Workflow — a sequence of nodes that processes the data received from the trigger. → Introduction to workflows

Environments

Environments separate your deployments (development, staging, production). Each environment carries its own configurations and variables. → Introduction to environments

Traces

Every workflow execution generates a trace: status, per-node data, execution time and any errors. Traces are used for monitoring, debugging, performance analysis and replaying an execution. → Introduction to traces

Authentication methods

Authentication methods securely store the credentials used by your workflows (Basic Auth, OAuth 2, API keys, tokens, certificates). They are encrypted, masked in the interface and reusable across multiple workflows. → Introduction to authentication methods

Dictionaries

Dictionaries parameterize values according to the execution environment (dev, staging, production): a key-value container configured per environment, expressed in workflows as {{dictionaries.nomDuDico.cleDuDico}}:

{{dictionaries.api.baseUrl}}

For example, an api dictionary defining the base URL of your API, entered in the entries editor of the Dictionaries feature:

Sensitive values (API keys, tokens, passwords) can also be stored in a dictionary and masked in the interface; a dictionary variable can for example be used in a field of an authentication method. → Introduction to dictionaries

Resources and Apps

• Resources — external entities reusable in your workflows (API, third-party service, configured integration, custom endpoint): their configuration pre-fills the nodes that use them. → Introduction to resources
• Apps — attach triggers, nodes and resources to a business scope, for readability and mapping. → Apps

Roles and permissions

Access to the platform is controlled by roles assigned to users, with rights that differ per environment:

Role	Scope
Viewer	Reading, testing (Development and other environments)
Builder	Workflow building (Development and other environments)
Advanced Builder	Building + Production deployment + role management
Exploitation	Production ops (traces, dictionaries)
Company Owner	Full company administration

→ Roles and permissions

Next steps

• Getting started on Ecosystem — login and navigation
• Create a trigger
• Create a workflow

---

See also: Introduction to Ecosystem · Glossary · Best practices