Skip to main content

Module 1.2: Setting Up Your OpenClaw Environment

Getting Started with OpenClaw

The best way to learn automation is to automate something. In this lesson, you will install OpenClaw, set up your first connection, and run a simple recipe — all in under 15 minutes.

Installation

OpenClaw runs anywhere Node.js runs. The quickest way to get started:

npx openclaw init my-automations
cd my-automations
npx openclaw start

This creates a new project with a local development server, a recipe editor, and a dashboard for monitoring your automations.

Your First Connection

Connections are how OpenClaw talks to external services. Let us start with something simple — connecting to a webhook endpoint.

npx openclaw connect add webhook-test \
  --type webhook \
  --url https://httpbin.org/post

This registers a test connection that sends data to httpbin (a free HTTP testing service). In production, you would connect to your actual services — Slack, GitHub, your CRM, databases, and more.

Your First Recipe

Recipes are YAML files that define your automation logic. Create a file called hello-world.recipe.yaml:

name: hello-world
trigger: manual
steps:
  - name: greet
    action: log
    message: "Hello from OpenClaw! The time is {{now}}"
  - name: notify
    action: webhook
    connection: webhook-test
    body:
      message: "First automation ran successfully"
      timestamp: "{{now}}"

Run it with:

npx openclaw run hello-world

You should see the log message in your terminal and a POST request sent to httpbin. Congratulations — you have just run your first automation.

Understanding the Project Structure

Your OpenClaw project has a clean, predictable structure:

  • recipes/ — Your automation definitions (YAML files)
  • connections/ — Service connection configs (credentials stored securely)
  • agents/ — AI agent definitions and prompts
  • .openclaw/ — Local state, logs, and configuration

The Local Dashboard

When you run npx openclaw start, a local dashboard is available at http://localhost:3100. From here you can:

  • View all your recipes and their run history
  • Monitor active automations in real time
  • Test recipes manually before scheduling them
  • Inspect logs and debug failures

Key Takeaways

  • OpenClaw installs with a single command and runs locally for development.
  • Connections link OpenClaw to external services securely.
  • Recipes are YAML files that define your automation steps.
  • The local dashboard gives you visibility into all your automations.

In Module 2, we will build real-world recipes that connect to services you actually use.