Key terms

A quick reference for the terms used throughout Attlaz. For a narrative introduction, see Core Concepts.

Term	Definition
Workspace	Your organisation on Attlaz — holds your team members and projects.
Project	A single integration or automation effort, containing one or more environments.
Environment	An isolated instance of a project, such as development, staging or production.
Flow	An automated workflow made up of a trigger, logic, actions and reports.
Flow run	A single execution of a flow, with a status of Pending, Running, Complete, Failed, Stopped or Canceled.
Trigger	What starts a flow — an API call, a webhook, a schedule, or an incoming email.
Runner	A process that executes flow runs.
Runner pool	A group of runners that process a flow's runs; each environment has a default pool.
External service	A third-party service such as Magento, Google or Slack.
Adapter	The Attlaz component that connects to an external service.
Adapter connection	Your configured instance of an adapter, holding the credentials for one account.
Provider token	The OAuth token behind a connection, refreshed automatically by Attlaz.
Code source	A repository whose code Attlaz deploys and runs as part of a flow.
Deployment	A build of a code source that runners execute.
Storage	Tiered data storage that flows can read from and write to.
Catalog	A named selection of products the product apps operate on.
Workspace member	A user who belongs to a workspace, with a role that governs their access.