Skip to main content

Workflow nodes

Choose the right TaskJuice node for each step in a workflow.

Workflow nodes are the building blocks in the TaskJuice workflow editor. This reference covers the nodes that are currently user-facing and implemented end to end.

Node families

FamilyUse it forImplemented nodes
TriggersStarting a workflow from an eventForm Submission, schedules, webhooks, app webhooks, polling, RSS, streams, sub-workflow invocation, error handler
App actionsCalling a supported app APISeeded app actions across Forms, GitHub, Gmail, Google Calendar, Google Drive, Google Sheets, HubSpot, QuickBooks, Salesforce, Shopify, Slack, Strava, Stripe, Twilio, and Workday
System nodesBuilt-in workflow logicAI Generate, AI Extract, Branch, Delay, HTTP Request, Loop, Parallel, Call Workflow, Switch, Transform

Choosing a node

Use a trigger when the workflow should begin from a form submission, schedule, webhook, external app event, polling cycle, RSS item, stream event, sub-workflow invocation, or error event.

Use an app action when the next step writes to or reads from an integration such as Slack, Gmail, HubSpot, Salesforce, Shopify, or QuickBooks.

Use a system node when the workflow needs internal behavior: branching, looping, parallel execution, waiting, transformations, HTTP calls, AI text generation, AI extraction, or calling another workflow.

Configured Form Submission trigger

Current user-facing system nodes

The Add Node panel only exposes system nodes that have a configuration panel, compiler support, and runtime support.

NodeTypical use
AI GenerateGenerate text from a prompt and selected AI model.
AI ExtractExtract structured JSON from text using a schema.
BranchRoute to two or more paths using conditions.
DelayPause for a fixed duration before continuing.
HTTP RequestCall an arbitrary HTTP API with optional auth and retries.
LoopRepeat by count, array item, or condition.
ParallelRun multiple branches concurrently and merge their outputs.
Call WorkflowInvoke another published workflow.
SwitchRoute by matching one selector value against cases.
TransformApply ordered data transformations.

Catalog entries that are still incomplete, disabled, or future-facing are intentionally not documented as user-facing nodes.

Was this helpful?