Run your first workflow

Before you start

This walkthrough takes you from a new account to a workflow that processes a real run. You build the simplest workflow that goes live cleanly: a webhook trigger and one Transform node that reshapes the incoming data. Transform needs no external app connection, so nothing blocks you on the way to your first run.

You need two things:

• An email address, or a Google account to sign in with.
• A payment method. TaskJuice has no free tier. You pick a plan during setup and activate through Stripe checkout.

If you already have an account and a workspace, skip to Build the workflow.

Create your account

TaskJuice organizes everything as Account, then Workspace, then User. When you sign up you create an account and TaskJuice creates your first workspace for you. There is no separate "create a team" step.

1. Sign up at /login

   Go to /login. Enter your email and choose Continue with Email, or choose Continue with Google. If the email is new, you set a password (use at least 8 characters) and agree to the Terms of Service and Privacy Policy, then select Create Account. There is no confirm-your-email step, so your account is usable right away.

2. Complete the setup wizard

   A brand-new account lands on the setup wizard at /onboarding/agency. It has five steps: choose a plan (Starter, Growth, or Scale), name your account and pick its URL, optionally add a logo and brand colors, then confirm. You can skip the logo and color steps.

3. Activate through checkout

   On the final step, select Continue to checkout and complete payment. When you return, you land on your dashboard. Your first workspace already exists, named after your account. This is where workflows, connections, and runs live.

For a field-by-field breakdown of the wizard, see create your account.

Build the workflow

A workflow is one trigger plus the nodes that run after it. You build it on a visual canvas, and every workflow starts with a trigger. You do not need to connect any external app for this first run, because the Transform node works entirely on the data you pass in.

1. Open the workflow builder

   From the dashboard, open the Get started checklist and choose Build your first workflow, or go to Workflows and create a new one. The builder opens on a blank canvas.

2. Add the webhook trigger

   Select Add node (the plus button on the canvas). Because the workflow has no trigger yet, the panel only offers triggers and shows "Start by choosing a trigger to begin your workflow." Open the System tab, find Webhook, and add it. This trigger fires when an HTTP POST arrives at the workflow's endpoint, and it needs no connection.

3. Add a Transform node

   Select Add node again. Now that a trigger exists, the panel shows the Triggers, Apps, and System tabs. Open System and add a Transform node. Transform reshapes data without any external app, which keeps this first run unblocked.

4. Connect the two nodes

   Drag from the trigger's output handle to the Transform node's input handle so an edge connects them. Every non-trigger node needs an incoming edge, or publishing fails.

5. Configure the Transform node

   Open the Transform node and add one operation. A Set operation that writes a fixed value, or a Copy that reads from the trigger, is enough to prove the workflow runs. You reference the trigger payload as $trigger, for example $trigger.email. You do not need real data yet.

6. Save

   Select Save. The Save button is disabled until you have unsaved changes, so if it is greyed out, your work is already saved.

To go deeper on building, see the builder tutorial.

Publish the workflow

Publishing compiles your workflow and makes the version live. A version receives events only when its status is Active.

1. Publish the draft

   Select Publish (the rocket button). It appears only on draft versions. TaskJuice compiles the workflow, and when there is nothing left to validate, it activates immediately. You see the toast Workflow published successfully.

2. Confirm the version is Active

   After publishing, the Publish button is replaced by an activation switch and a Run button. The Run button is disabled unless the version status is Active. If Run is enabled, your workflow is live.

Start a live run

You can fire a run by sending an HTTP POST to the workflow's webhook endpoint, but the fastest way to confirm everything works is to start a run from the builder.

1. Open the Run dialog

   Select Run. The Run Workflow dialog opens with a Trigger Payload (optional) field. Leave it as {}, or paste a JSON object that matches what your Transform reads:

   { "email": "ada@example.com", "plan": "growth" }

   Copy code
2. Start the run

   Select Run. You see the toast Workflow run started.

3. Watch it complete

   Open the Runs list for the workflow. Your run appears and moves from Running to Completed. Open the run to see the step-by-step timeline: the trigger payload, then your Transform node's input and output.

Verify it worked

You have a working first run when all of the following are true:

• The workflow version status reads Active.
• Starting a run showed the toast Workflow run started.
• The run reached status Completed in the Runs list.
• The Transform step shows the output you configured.

To read a run in detail, see the run model.

Next steps

• Connect a real app inline while building with connect an account.
• Start from a prebuilt workflow with start from a template.
• Understand the moving parts in core concepts.