Knowledge Base

Your First Workflow

Duration: ~15 min · Level: Beginner

Prerequisites: Nodlyn Studio installed (on-prem or cloud). No coding required.

In this tutorial you build a minimal workflow: a Webhook trigger receives JSON, a Log node records it, and you test with Dry Run before activating.

Step 1 — Create a workflow

  1. Open Studio and click New workflow (or use the template library and pick a blank canvas).
  2. Name it My First Workflow in the toolbar.

Step 2 — Add a Webhook trigger

  1. From the left palette, open Triggers and drag Webhook onto the canvas.
  2. Select the node. In the Inspector (right panel), set:
    • Path/hello (or leave the default).
    • MethodPOST.
  3. Note the full webhook URL shown in the Inspector — you will use it after activation.

Step 3 — Add a Log node

  1. Drag Log from Utilities and connect the Webhook output to Log input.
  2. In the Inspector, set Message to something like Received: {{body}} so the incoming payload appears in run history.

Step 4 — Dry Run

  1. Click Dry Run in the toolbar.
  2. Studio simulates the path without calling external systems. Confirm the Log node shows in the trace.

See Dry Run for details on safe testing.

Step 5 — Validate and activate

  1. Click Validate — fix any warnings (missing connections, required fields).
  2. Move through Approve if your org requires it, then Activate.

Only Active workflows accept live webhook calls. Read Workflow Lifecycle for the full state machine.

Step 6 — Send a test request

With the workflow Active, POST JSON to your webhook URL:

curl -X POST "https://your-instance/webhook/hello" \
  -H "Content-Type: application/json" \
  -d '{"name": "Nodlyn"}'

Open the Jobs panel → History and confirm a completed run with your log message.

What you learned

  • Palette → canvas → Inspector workflow.
  • Trigger data flows to downstream nodes via placeholders like {{body}}.
  • Dry Run vs live activation.

Next tutorials

Nodlyn Assistant
Ask me anything about Nodlyn
Hi! 👋 I'm the Nodlyn assistant. Ask me about the product, workflow components, connectors, agent runtime, agent capabilities, deployment, and more. If I don't know an answer, I'll point you to our contact form.