Greentic.ai is currently at v0.2.0. A basic store with some free flows, plugins and tools is available. You can also create your own flows, plugins, tools,... Flows can use tools that connect to APIs with no authentication or API keys. oAuth will be supported in v0.3.0. You will have to run Greentic.ai from your local computer. Deploying onto the Cloud is coming in v0.4.0. The vision for v1.0.0 foresees a world where you just ask via WhatsApp, Teams, Slack, Telegram,... for a digital worker to be generated and automatically Greentic.ai will create it for you based on a simple ChatGPT-like request. Also learn how Greentic.ai is able to generate revenues for partners.
📋 Table of Contents
- Introduction
- What is a Digital Worker?
- Key Concepts
- Getting Started
- Quick Flow Example (YAML)
- Controlling Flows, Channels & Tools
- Coming Soon
- Need Custom Agentic Automation?
- Contributing
- License
📝 Introduction
Greentic.AI is an open-source platform designed to let you build, deploy, and manage digital workers at lightning speed.
- Fastest runtime with zero cold-starts for WebAssembly tools.
- Extendable architecture: plug in your own channels, tools, agents and processes, all defined in an easy to understand text-based flow.
- Secure by design: tools are sandboxed inside Wasm allowing securely running untrusted third-party MCP tools.
- Observability via OpenTelemetry integrations
🤖 What is a Digital Worker?
A Digital Worker is a flow that acts autonomously and intelligently to handle a complete task, from end to end.
It:
- Listens for messages (via Channels like Telegram or Slack)
- Extracts meaning or decisions (via Agents, powered by LLMs)
- Calls APIs or executes functions (via Tools written in Wasm)
- Handles control logic (via Processes like retries, conditionals, loops)
Flows link these components into one cohesive automation. Your digital workers are secure, modular, and language-agnostic.
🔑 Key Concepts
Tools (MCP in Wasm)
- MCP (Model-Context Protocol) modules compile to WebAssembly.
- Each tool can define its own actions, inputs, outputs, and run logic securely.
- Tools live in
tools/and are called by the flows.
👉 Learn how to build MCP Tools
Channels
- Channels allow flows to send/receive messages to/from the outside world.
- Examples: Telegram, Slack, Email, HTTP Webhooks.
👉 How to build Channel Plugins
Processes
- Processes are a collection of builtIn processes and soon extendable via Wasm.
- Debug: allows you to easily understand the output of the previous flow nodes.
- Script: create a script in Rhai to programme logic.
- Template: a Handlebars-based template processor for rending string output.
- QA: A dynamic, multi-question form-like process with optional validation, LLM user assistance and routing.
- Defined declaratively in YAML.
Agents
- Agents are LLM-powered nodes capable of autonomous decision-making.
- The first type of agent is oLlama. More types coming soon.
- Coming Soon: Agents understand context, use memory, trigger tools, and follow goals.
🦀 Prerequisites: Install Rust
To build and run this project, you need to have Rust installed.
If you don’t have Rust yet, the easiest way is via rustup:
|
## 🚀 Getting Started
The first time around initialise everything:
- creates the greentic configuration directories
- registration so your user gets a GREENTIC_TOKEN
- and you can pull flows, channels, tools,... from
- the greenticstore.com.
Pull your first flow, i.e. Telegram Weather Bot:
Extra instructions after you pull the flow:
- you will need to configure one time a Telegram bot and obtain a TELEGRAM_TOKEN. You can add it via 'greentic secret add TELEGRAM_TOKEN <your_token>
- You also need to sign up to the WeatherApi and generate an API key.
- You can add it via 'greentic secret add WEATHERAPI_KEY <your_key>
- you will now be able to get the weather forecast via your Telegram bot.
- The Telegram Weather Bot optionally uses AI to help the user, e.g.
- if you type: "Get me the weather in London for tomorrow" instead of 'London'
- when asked: 👉 What location would you like a forecast for?
- For this to work you also need to install ollama
- and do 'ollama pull gemma:instruct'
Start greentic with:
You should now have a fully working Telegram Weather Bot.
If you want to create your own flows:
When you are ready to start a flow you can call:
🛠 Quick Flow Example (YAML)
id: weather_bot
title: Get your weather prediction
description: >
This flow shows how you can combine either a fixed question and answer process
with an AI fallback if the user is not answering the questions correctly.
channels:
- telegram
nodes:
# 1) Messages come in via Telegram
telegram_in:
channel: telegram
in: true
# 2) QA node: ask for the city and fallback to the OllamaAgent if more than 3 words are used
extract_city:
qa:
welcome_template: "Hi there! Let's get your weather forecast."
questions:
- id: q_location
prompt: "👉 What location would you like a forecast for?"
answer_type: text
state_key: q
max_words: 3
fallback_agent:
type: ollama
model: gemma:instruct
task: |
The user wants the weather forecast. Find out for which city or location they want the weather and
assign this to a state value named `q`. If they mention the days, assign the number to a state value named `days`,
otherwise use `3` for `days`.
If you are unsure about the place (`q`), ask the user to clarify where they want the weather forecast for.
routing:
- to: forecast_weather
# 3) “forecast_weather”: the Weather API tool, using the JSON from parse_request.
forecast_weather:
tool:
name: weather_api
action: forecast_weather
parameters:
q: "{{extract_city.payload.city}}"
days: 3
# 4) “weather_template”: format the weather API’s JSON into a friendly sentence.
weather_out_template:
template: |
Here’s your forecast for {{ location.name }}:
• High: {{ forecast.forecastday.[0].day.maxtemp_c }}°C
• Low: {{ forecast.forecastday.[0].day.mintemp_c }}°C
• Condition: {{ forecast.forecastday.[0].day.condition.text }}
• Rain Today? {{#if (eq (forecast.forecastday.[0].day.daily_will_it_rain) 1)}}Yes{{else}}No{{/if}}
# 5) “telegram_out”: send the forecast back to Telegram.
telegram_out:
channel: telegram
out: true
connections:
telegram_in:
- extract_city
extract_city:
- forecast_weather
forecast_weather:
- weather_out_template
weather_out_template:
- telegram_out
⚙️ Controlling Flows, Channels & Tools
# Validate a flow before deploying. Afterwards you can start/stop the flow
🔭 Coming Soon
- v0.3.0 oAuth MCP Tools - connect to any SaaS
- v0.4.0 Serverless Cloud deployment of flows - greentic deploy
Roadmap:
- More Agentic: memory persistence, vector databases, A2A,...
- AI Flow Designer
- Flow, Tools, Channels & Processes marketplace
📬 Need Custom Agentic Automation?
Have a specific use-case or need expert help?
Please fill out our form: Agentic Automation Inquiry
🤝 Contributing
We are actively looking for contributors and welcome contributions of all kinds!
- Bug reports 🐞
- Feature requests 🎉
- Code & documentation PRs 📝
- Fork the repo
- Create a feature branch
- Open a PR against
main
See CONTRIBUTING.md for full guidelines.
📄 License
Distributed under the MIT License. See LICENSE for details.
Thank you for checking out Greentic.AI—let’s build the future of automation together! 🚀