Look up any TaskJuice term

This page defines the terms you meet across TaskJuice, alphabetized for quick lookup. Each entry links to the page that explains the concept in full. Where a word means two different things in two different places (for example, a run is "paused" but a workflow is "Paused (safety)"), the entry says so.

A

Account The top of the hierarchy. One account is your agency. It holds your team, your branding, your plan, and one workspace per client. In the UI an account is often called your "agency". See Account roles and permissions.

Account admin (Admin) An account role. An Admin can build, invite teammates and clients, manage workspaces, and manage branding. An Admin cannot access billing, transfer ownership, or delete the account. See Account roles and permissions.

Account member (Member) An account role. A Member can build workflows and connections and view everything, but cannot invite, manage workspaces, or manage branding. See Account roles and permissions.

Account owner (Owner) The single owner role on an account. The Owner can do everything an Admin can, plus manage billing, transfer ownership, and delete the account. There is exactly one Owner per account, and ownership moves only by transfer, never by invite.

Action A node that performs a provider operation, such as sending a Slack message or creating a HubSpot contact. Actions are the work your workflow does after the trigger fires. See Triggers and actions.

Active version The one version of a workflow that receives live events. Activating a version automatically sets every other version of the same workflow to Inactive. Only an Active version dispatches. See Versioning.

AI node A system node that calls a model: AI Agent, AI Generate, AI Summarize, AI Classify, or AI Extract. AI nodes use the provider keys you bring to your account. See Triggers and actions.

Apply template Cloning a template into a workspace as a brand-new, independently editable workflow. You pick the target workspace, fill in any required variables, and TaskJuice creates a fresh draft workflow named after the template. See Template gallery.

Approval A human-in-the-loop checkpoint. A gated action parks the run as waiting and creates an approval task that someone reviews in the Approvals inbox. Each task has an expiry and a timeout policy. See Why a run paused.

B

Backup codes Ten single-use, eight-character recovery codes generated when you enable multi-factor authentication. Each works once if you lose access to your authenticator app. Regenerating them invalidates the old set immediately. See Protect your account.

Branch A control-flow node that routes execution down different paths based on conditions. A Branch needs at least 2 and at most 8 conditions, each built from a field, an operator (such as Equals, Contains, or Exists), and a value. See Control flow.

Branding The logos, icons, favicon, and color tokens that render across your agency app, the sign-in page, the client portal, and public forms. One configuration drives all of those surfaces, so clients never see the TaskJuice brand. See Branding.

Bring your own OAuth (BYOC) Registering your agency's own OAuth client for an app so the consent screen and refresh tokens carry your brand instead of TaskJuice's shared client. Apps with no override fall back to the shared client. See Branding.

C

Cancelled A terminal run status meaning an operator cancelled the run. Cancelling stops all pending and running steps and cannot be undone; you can replay the run later to re-run it from scratch. See Run and step statuses.

Client The workspace role for your agency's external customer. A Client has read-only access to one workspace: they can view execution history, trigger manual runs, and rotate their own connected-app credentials, but cannot edit workflows or change settings. Clients and staff are mutually exclusive on the same account.

Code node A system node that runs your own code as a step. Anything you write to the console is captured and shown in the Console section of that step's detail, up to 100 lines or 10 KB. See Control flow.

Compile Turning a workflow's graph into the executable plan that runs at scale. TaskJuice compiles a version when you publish or activate it. If validation passes the version becomes Active; if compilation itself fails, the version becomes Failed. See Versioning.

Completed The success state for a run or a step: every step finished without error. This is the only success word in the product surface; the run timeline never shows "succeeded". A completed run is terminal. See Run and step statuses.

Connection A stored, reusable credential for a third-party app. You create a connection once and select it on any node that needs it. The connect dialog calls a connection an "account" in its button text, but the concept is a connection. See Connections.

Connection request A request you send to a client asking them to connect one of their own apps. You queue requests per node, then send a single bundled email per recipient. The client authorizes through the provider's consent screen. See Connection request statuses and expiry.

Connection scope Whether a connection belongs to one workspace or to the whole account. A workspace-scoped connection (the default) lives in one client's workspace. An account-scoped connection is created once at the account level and granted to the workspaces that use it. See Connections.

Connection status The health of a connection. The four values are active, error (reconnection needed), pending (waiting for the first sync), and revoked. A connection in error is the one to reconnect. See Reconnect an integration.

Custom domain Your own hostname pointed at TaskJuice through a CNAME record, so the app, sign-in, and portal serve on your domain. See Custom domain.

D

Delay A system node that pauses the run for a set time. While a delay is pending, the run shows the waiting status and resumes when the timer fires. See Control flow.

Deprecated A terminal version status. A deprecated version cannot be activated or returned to any other status. See Versioning.

Draft For a workflow, the lifecycle status before you publish. For a version, the editable starting status. Editing the graph of an Active version creates a fresh Draft version rather than changing the running one, so your edits never disturb live runs. See Versioning.

E

Eval failed A version status meaning a publish-time evaluation suite did not pass. The version drops back so you can fix it and publish again. Evaluation only happens when a blocking eval suite is configured. See Versioning.

Evaluating A transient version status while publish-time evaluation suites run. If the version has no blocking suites it skips straight to Active; if it has them, the response is held while they run. See Versioning.

Expression A small JSONata snippet you write in a node field to pull data from earlier in the run, for example $trigger.email or $steps.action1.data.id. Type $ in any expression field to open the reference picker. See Expressions.

F

Failed For a run or step, a terminal status meaning a step errored and the run stopped. For a version, the status after a compilation failure. Open the first failed step to read its error, then fix and replay. See Run and step statuses.

Founding discount A 50% discount applied to your plan's base price. It applies to the base plan only; overage usage still bills at standard rates. See Manage your subscription.

G

Graph The shape of a workflow: one trigger plus the connected downstream nodes and the edges between them. The graph lives on the version, not on the workflow container. See Workflows.

H

HTTP node A system node that makes a custom HTTP request, for any API not covered by a dedicated app action. See Control flow.

I

Inactive A version status meaning the version is compiled and ready but is not receiving live events. You can reactivate an inactive version without recompiling. See Versioning.

Invitation The record of inviting someone. A teammate invitation grants an account role (Admin or Member); a client invitation grants the Client role on one workspace. Invitations expire after 7 days. See Account roles and permissions.

L

Loop A control-flow node that repeats a body. The three types are Fixed Count, Condition-based, and Array Iteration. Array loops bind $currentItem and $currentIndex inside the body and can run sequentially or in parallel. Every loop requires a maximum-iterations cap between 1 and 1000. See Control flow.

M

Magic link The branded, login-free URL a client without a portal account receives by email to authorize a connection request. Magic-link requests expire 7 days after dispatch; portal requests expire after 4 hours. See Connection request statuses and expiry.

MFA (multi-factor authentication) Time-based codes from an authenticator app, plus backup codes, that protect your sign-in. An account owner or admin can require MFA for all staff with a grace period of up to 30 days. See Protect your account.

N

Node Any box on the canvas. A node is one of three roles: the single trigger, an app action, or a system node (such as Branch, Loop, or Transform). See Triggers and actions.

O

Overage Usage above your plan's included envelope. Overage is post-paid: the priced dimensions (compute time, file storage, state storage, outbound bandwidth, and form submissions) appear on your next invoice. Workflow runs are counted and shown but not priced directly. See Usage and overage.

P

Parallel A control-flow node that runs two or more branches at once. Completion modes are all, race, settled, and independent; the default waits for every branch. See Control flow.

Paused A run status meaning an operator stopped a running or pending run. You resume it with the Resume button on the run detail page. This is not the same as a workflow that is Paused (safety). See Run and step statuses.

Paused (safety) A workflow-level status set by the safety breaker when something looks misconfigured, such as a runaway loop or a reached spend cap. This is not the same as a paused run. You resume a throughput-tripped workflow from its safety banner after fixing the issue; a spend-cap pause resumes on its own once you raise the cap or the billing period rolls over. See Why a run paused.

Pending A transient run status meaning the run was accepted but no steps have started yet. If a run stays pending, confirm the workflow is published and its version is Active. See Run and step statuses.

Plan Your TaskJuice subscription tier: Starter, Growth, or Scale. The plan sets your workspace limit (1, 5, or 25), execution-data retention (7, 30, or 90 days), and other inclusions. There is no free tier. See Usage and overage.

Published A workflow status meaning it has an Active version and is dispatching live events. A workflow flips to Published automatically when one of its versions becomes Active, and back to Draft when the last Active version is deactivated. See Versioning.

Publish The action that makes a version live: TaskJuice runs the plan check, compiles the graph, validates it, and (when no validation rule blocks it) activates the version. A draft, inactive, failed, or eval-failed version can be published. See Publish your workflow.

R

Reauthorization Reconnecting a connection whose OAuth token can no longer be refreshed. The connection turns to error, a banner appears, and dependent runs pause until you re-run the OAuth flow. A single expired token does not trigger this; only a permanent refresh failure does. See Reconnect an integration.

Reference picker The popover that lists every value you can pull into a node field, grouped by scope ($input, $trigger, $steps, $meta). It is populated from the pinned test output of upstream nodes, so test a node first to see its real fields. See Map data between steps.

Replay Creating a brand-new run from a finished one. You can replay a completed, failed, or cancelled run as-is, with a new prompt, or with a new model. Replays are capped at 20 per minute per workspace and a chain depth of 5. See Replay and re-run.

Run One execution of a published workflow version, started when its trigger fires or by a manual start. A run is pinned to the version it started on, so swapping the live version never disturbs runs already in flight. The seven run statuses are pending, running, waiting, paused, completed, failed, and cancelled. See The run model.

Running A run or step status meaning steps are executing now. While a run is running you can pause or cancel it. See Run and step statuses.

S

Spend cap A required, account-scoped monthly safety limit. Workflows pause when projected month-end spend reaches the cap, then resume at the start of the next billing cycle. The default is five times your plan's base monthly price, and the cap cannot be set below your plan base. See Usage and overage.

Step (node run) The execution of one node inside a run. A step carries its own input, output, console output (for code steps), and, on failure, a structured error. Step statuses match the run statuses and add skipped, which marks a node on a control-flow path that was not taken. See Run and step statuses.

Stripe Connect (client billing) The separate billing track where your agency bills its own clients, distinct from paying TaskJuice for your own plan. See Manage your subscription.

Subprocessor A third party that processes data on TaskJuice's behalf. The current list and the change-notice commitment are published on the legal subprocessor list. See Subprocessors.

Subscription status The state of your TaskJuice subscription, such as Trialing, Active, Past Due, or Canceled. A new account gets a 14-day trial; a failed payment keeps full access through a 14-day grace window before access is paused. See Manage your subscription.

Switch A control-flow node that evaluates one selector expression and routes to the case whose value matches. Match modes are Strict (default), Loose, Regex, and Contains. See Control flow.

System node A built-in node not tied to any app: Branch, Switch, Loop, Parallel, Transform, HTTP, Code, Delay, Call Workflow, and the AI nodes (AI Agent, AI Generate, AI Summarize, AI Classify, AI Extract). See Triggers and actions.

T

Template A reusable snapshot of a published workflow that you can clone into client workspaces. Templates carry numbered revisions and optional variables that get filled in when you apply them. No starter templates ship by default; you build templates from your own published workflows. See Save a workflow as a template.

Test a node Running one node for real against pinned or typed input from inside its configuration panel. This is not a simulation: it executes the step and pins its output, which is what fills the reference picker for downstream nodes. See Publish your workflow.

Transform A system node for reshaping data. Its operations include Set, Copy, Rename, Merge, Concatenate, Calculate, and conversions such as To Number and To Date. It is the closest thing to a dedicated data-mapping tool. See Map data between steps.

Trigger The single entry node of a workflow: the event that starts a run. Trigger kinds include Webhook, App Webhook, Polling, Schedule, Stream, Message Queue, Email, RSS, Sub-workflow, Error, Manual, and Form. A workflow has exactly one trigger. See Triggers and actions.

Trigger payload The data the trigger hands to the run, available as $trigger. Batch-shaped triggers (webhook, RSS, polling) collapse to one run per cycle or POST, wrapping multiple items as { items: [...] }. To process each item, add a Loop node; reference the first item as $trigger.items[0]. See The run model.

U

Usage meter A per-dimension counter on the usage dashboard: Workflow runs, Compute time, File storage, State storage, Form submissions, and Outbound bandwidth. Each meter shows current versus included and a projection for the period. See Usage and overage.

V

Version A numbered, editable snapshot of a workflow's graph with its own lifecycle. The eight version statuses are Draft, Compiling, Evaluating, Eval failed, Active, Inactive, Failed, and Deprecated. The workflow is the container; each version holds the canvas you edit. See Versioning.

W

Waiting A run or step status meaning execution is parked on something: a delay timer, an approval, a form submission, a sub-workflow barrier, or a pending client connection request. A waiting run resumes when the wait resolves. See Why a run paused.

Workflow The durable design object: a name, a description, a status, and a pointer to its currently Active version. The workflow is the container; its graph lives on the version. See Workflows.

Workspace One client engagement under your account. Each workspace is isolated: its workflows, connections, and data are scoped to it and cascade-delete with it. Your plan sets how many workspaces you can create. See Account roles and permissions.

Expression aliases

These are the references you write inside node fields. Full syntax lives on the Expressions reference.

When a term has two meanings

A few words mean different things depending on where you see them. Reading them as one thing is the most common mix-up:

• Paused describes a run an operator stopped, which you resume with the Resume button. Paused (safety) describes a whole workflow the safety breaker stopped, which resumes differently. See Why a run paused.
• Status is three separate lists: the workflow's published lifecycle, a run's progress, and a step's progress. See Run and step statuses.
• A connection's status (active / error / pending / revoked) is the health of a stored credential, while a connection request's status (pending / fulfilled / expired / revoked / cancelled) tracks the lifecycle of the ask you sent a client.

Related

• Workflows and The run model for the two objects most of these terms hang off.
• Run and step statuses for every status value and its next action.
• How credentials are stored for what happens to a connection's secret.