Skip to main content

Glossary

Reference definitions for the terms used in this documentation.

Core concepts​

  • Trigger — entry point of a workflow: defines when it starts, how data is received and which data is passed along. Each workflow is associated with a single trigger. → Introduction to triggers
  • Trigger node — automatic entry point of the workflow: added when the workflow is created, it cannot be deleted and is the first node executed. It represents the trigger associated with the workflow and the data it receives. → Trigger node
  • Workflow — sequence of nodes that processes the data received from the trigger. → Introduction to workflows
  • Node — a basic operation of a workflow (HTTP request, condition, loop, code, email send, etc.). Nodes are connected to each other in the editor.
  • Business metadata — free annotation attached to a node (reference, integration context, such as an email, an identifier, an iteration value), with no effect on execution and visible in the traces according to the tracing mode. → Workflow editor
  • Trace — record of a workflow execution: status, data per node, duration and errors. Used for monitoring, debugging and replay. → Introduction to traces
  • Environment — isolated deployment space (development, staging, production) carrying its own configurations and variables. → Introduction to environments
  • Organization — workspace that users access; triggers, workflows and configurations are attached to it.

Configuration elements​

  • Dictionary — key-value container of variables whose value varies according to the environment, expressed in workflows as {{dictionaries.nomDuDico.cleDuDico}}. Sensitive values can be masked there and referenced in node fields like authentication methods. → Introduction to dictionaries
  • Authentication method — secure storage (encrypted and masked) of the credentials used by workflows: Basic Auth, OAuth 2, tokens, API keys, certificates. → Introduction to authentication methods
  • Resource — external entity reusable in workflows (API, third-party service, configured integration, custom endpoint) whose configuration pre-fills the nodes. → Introduction to resources
  • App — attachment of triggers, nodes and resources to a business scope, for readability and mapping. → Apps
  • Project / Folder — organizational levels of the workflow tree.

Lifecycle​

  • Version — frozen state of a workflow; the Main version is always modifiable and cannot be deployed to production. → Version management
  • Deployment — making a trigger or a workflow available in an environment.
  • Trigger status — Inactive (created but triggers nothing) or Active (can be deployed and trigger workflows).
  • Workflow status — Draft (being edited), Main version (modifiable development line) or Deployed.
  • Slug / Path — unique identifier of a trigger in public URLs, unique within the organization.

Security​

  • MFA / OTP — two-factor authentication: a one-time password (OTP) generated by a TOTP-compatible application (e.g. Google Authenticator).
  • Role — set of permissions granted to a user; roles determine what a user can create, modify, deploy or administer. → Roles and permissions

See also: Concepts · Introduction to Ecosystem