01. Getting Started¶

From signing in to actually running your first workflow. Follow along in order and it takes about 10 minutes.

Go to app.eeumsae.com and press Continue with Google. During the beta, Google sign-in is the only supported method. There is no separate sign-up step — your account is created on first sign-in.

2. Pick a workspace¶

After signing in you see your list of workspaces. A workspace is the container for your automations, connections, variables and data. If this is your first time, one default workspace is already there. Click into it and you land on the main screen with the sidebar.

If you have several workspaces, switch between them with the switcher at the top of the sidebar. Connections, variables and datasets are managed per workspace, so if you connected Slack in workspace A, you have to connect it again in workspace B.

3. Create your first workflow¶

In the sidebar go to Workflows → press the Create button at the top right.

Field	Description
Name	A human-readable name. For example: `First automation test`
slug	The identifier used in URLs and webhook addresses. It is generated from the name and you can edit it.

Once created you land on the workflow detail screen. It has three tabs.

Tab	What it does
Overview	Check the webhook address, view execution history
Visual Editor	A diagram editor where you drag nodes and connect them with lines
YAML	Write the workflow definition directly as text

The two editing tabs are two views of the same workflow. What you build in the visual editor shows up in the YAML tab, and the other way around.

4. Build it in YAML (the fastest route)¶

Open the YAML tab and paste the whole thing below. This example needs no external connections at all.

id: my-first-workflow
name: First automation test

nodes:
  - id: trigger
    name: Webhook trigger
    type: ENTRYPOINT
    trigger:
      kind: WEBHOOK
      input-schema:
        type: object
        required: [name]
        properties:
          name: { type: string }

  - id: greet
    name: Build a greeting
    type: CALL
    integration: transform_jmespath
    input:
      expression: "{message: join('', ['Hello, ', name, '!'])}"
      data:
        name: "${nodes.trigger.response.body.name}"

edges:
  - from: trigger
    to: greet

Once pasted, press Save (or Ctrl+S).

id must be unique within the workspace. If the value is already taken the save is rejected, so pick another name.

Line by line, here is what it means.

The trigger node: starts from a webhook, and the request body must contain a name field.
The greet node: transforms data using the transform_jmespath integration. It takes the name the previous node received and builds a greeting sentence.
edges: means "run greet after trigger".

5. Actually run it¶

Go to the Overview tab. For a workflow that uses a webhook trigger, the call address appears in the Webhook trigger card.

https://api.eeumsae.com/webhooks/{workspaceId}/{workflowSlug}

POST to this address and it runs. You can check it from a terminal like this.

curl -X POST "https://api.eeumsae.com/webhooks/<workspaceId>/my-first-workflow" \
  -H "Content-Type: application/json" \
  -d '{"name": "Ada"}'

Refresh the execution history on the Overview tab and you will see the run you just made. Click it to see what went into and came out of each node. If the greet node output contains {"message": "Hello, Ada!"}, it worked.

What next?¶

Now that your first workflow has run, it is time to move on to an automation you would actually use.

"I want it to run at a fixed time every day" → the scheduler part of 03. Setting Up Triggers

"I want the result in Slack" → connect Slack in 07. Managing Connections, then slack_post_message in 04. Integration Catalog

"I want to call my own service's API" → http_request in 04. Integration Catalog

"I want AI to summarize something" → llm_chat in 04. Integration Catalog

"I just want to describe it in words" → 11. Turning It into an AI Assistant

"I want to see finished examples first" → 12. Recipes