Skip to content

eeumsae User Guide

So your flow never breaks.

eeumsae runs your business automations without you standing up a server or a cron job. Call an API on a schedule or a webhook, pull out just the fields you need, summarize them with AI, and send the result to Slack — turn it on once and it keeps running.

eeumsae is currently in beta. This guide describes the screens and features as of the beta.


The 5-minute version

A single automation in eeumsae is called a workflow. A workflow is one picture: nodes connected by edges.

[⏰ Every day 9 AM]  →  [⚡ Fetch orders API]  →  [⟐ Keep only what matters]  →  [✦ AI summary]  →  [💬 Post to Slack]
    start (trigger)         external call              data transform              AI call          send message
  • Every workflow starts from exactly one ENTRYPOINT node. There are two ways to start it — a webhook (when someone calls it) or a schedule (at a fixed time).
  • Everything in between is a CALL node. You decide what it does by choosing an integration.
  • To pass values between nodes you write expressions like ${nodes.previousNode.response.body.field}.

There are three ways to build one. Pick whichever you like — you can mix them freely.

Way Where Who it suits
Visual editor Workflow detail → Visual Editor tab People who want to click things together
Write YAML directly Workflow detail → YAML tab People who like version control and copy-paste
Ask an AI assistant Connect Claude, ChatGPT, etc. over MCP "Summarize sales every day at 9 and send it to Slack"

Contents

Start here

Page What's in it
01. Getting Started From signing in to actually running your first workflow
02. Core Concepts What workflows, nodes, edges and executions are

Building workflows

Page What's in it
03. Setting Up Triggers Receiving webhooks / running on a schedule
04. Integration Catalog Everything a CALL node can do, and its inputs
05. Connecting Data with Expressions ${...} syntax — reading previous node values, \| raw
06. Flow Control Branching · joining · looping

Workspace management

Page What's in it
07. Managing Connections OAuth connections to Slack, GitHub and other services
08. Variables and Secrets Using API keys without writing them into YAML
09. Datasets Table-shaped storage your workflows read and write

Running it

Page What's in it
10. Executions and Monitoring Reading execution history, retries and timeouts, failure alerts
11. Turning It into an AI Assistant (MCP) Connecting Claude or ChatGPT to eeumsae and building by talking

Reference

Page What's in it
12. Recipes Finished examples you can copy and paste
13. Troubleshooting Common errors and their causes, plus FAQ

The screen at a glance

Once you sign in there is a sidebar on the left. Here is what each menu does.

Menu What it does More
Dashboard Workflow count, total executions, success rate, recent executions Page 10
Workflows Create, edit and inspect the execution history of your automations Page 01
Connections Connect external services like Slack and GitHub Page 07
Variables Store API keys and settings (secret / plain) Page 08
Datasets Table-shaped data storage Page 09
Templates Node template catalog
Recipes Ready-made workflow templates
API Keys Issue keys for external and AI assistant (MCP) access Page 11
Notifications Where to get notified when an execution fails Page 10

About this guide

  • Labels are written exactly as they appear on screen.
  • The example YAML is written so that it works when pasted as-is. You do still have to replace values like channel IDs and API keys with your own.
  • Features may change during the beta. If the docs and the screen disagree, tell us at [email protected].