Your first automationLesson 2 of 8

Create a project

A project is the home of an automation: its scripts and flows, the connections and variables they use, their schedules and endpoints, and the history of every run. In this lesson you create daily-report, the project the whole track is built in — and keeping the exercise in its own project makes it easy to remove later.

4 min readBefore this: What Waiso isOpen in Waiso
What you will learn
  • Create a project with + New project
  • Understand how the name becomes the project’s address
  • Find the project pages the next lessons use

What a project holds

Everything you build lives inside a project, and nothing crosses between projects unless you move it: a script in one project cannot import a script in another, a project variable is read only by its own project, and a person given access to one project sees none of the others.

ProjectsWorkers 3Users
Pick a project or create a new oneNew project
D6 scripts
docs-demonewShop demo: scripts, flows and triggers
R14 scripts
reportingDaily sales reports and the finance export
E4 scripts
events-labEvent triggers playground (MQTT + e-mail)
New project
The Projects page: one card per project, the New project action at the top.
Inside a projectPage
Scripts, flows and foldersCode
Every run, from any triggerRuns
Timetables that start runsSchedules
URLs other systems callAPI
Databases, S3, e-mail, AI providersIntegrations
Settings and secrets your code readsVariables

Create daily-report

  1. Press New project

    On Projects, press + New project. Type daily-report as the Project name; the Description (optional) can stay empty. Press Create project. An icon and a colour are picked for you — change them later with Edit project.

  2. Open it

    Click the new card. A project opens on Runs — empty for now — with the project’s pages in the left column. Code is where the next lesson starts.

  3. Check that a worker can serve it

    Open Workers. On the cloud at least one worker is online and runs every language. If a run later stays Queued, this page is where you look first.

A name is an address

The project’s name is turned into its address: daily-report lives at /projects/daily-report, and a name like Daily Report becomes daily-report too. That is why two projects cannot share a name that reads the same once spaces and capitals are folded — the form says A project with that name already exists.

Inside the project, names work the same way one level down. A script called daily-report in the folder reports opens at /projects/daily-report/edit/reports/daily-report, and two items in the same folder cannot share a name. Folders are made with + New → Directory on the Code page, and a script’s folder path is also the default path of its API endpoint — so a tidy tree gives tidy URLs.

Renaming

Renaming a project changes its address in the app, so bookmarks to the old one stop working. The URLs other systems call are not affected: an API endpoint is addressed by the project’s permanent id, not by its name (see Your first API).

Limits

  • Each plan includes a number of projects. At the cap the form says so before you type, and offers Upgrade plan.
  • Who may open a project is set per person and per area; see Team access.
2 / 8