Workflow guide
Learn how TaskJuice workflows start, run, and connect triggers, app actions, system nodes, and forms.
How workflows are built
A TaskJuice workflow starts with one trigger and continues through connected action or system nodes. Each node receives context from previous steps and can add output for later steps.
Use this section when you are creating, reviewing, or operating workflows in the visual editor.
Core concepts
| Concept | What it means |
|---|---|
| Trigger | The event that starts a workflow run. |
| App action | A step that calls a supported app, such as Slack, Gmail, HubSpot, Salesforce, Shopify, or Google Sheets. |
| System node | Built-in workflow logic such as branching, looping, transforming data, calling HTTP APIs, or using AI. |
| Form node | A first-party Forms trigger or action that starts a workflow from a form submission or pauses a workflow for a response. |
| Published version | The validated workflow version that receives production events. Draft edits do not affect live runs until you publish again. |
Start here
- Workflow nodes - Choose the right trigger, app action, or system node.
- Form workflow nodes - Start workflows from forms or pause a workflow for a form response.
- Trigger nodes - Schedule, webhook, form, polling, stream, RSS, and app webhook triggers.
- System nodes - Built-in control flow, AI, HTTP, transform, and workflow-call nodes.
- App action nodes - App action coverage and configuration guidance.
Publishing expectations
Before publishing, TaskJuice validates required node configuration, required connections, graph structure, and referenced forms. Fix any validation issue in the editor, run a test, then publish the workflow when the test output matches the expected business process.
Was this helpful?