noclick

Describe an agent. Watch it get built. Let it run. Workflow automation with AI agents at the core — a visual canvas, ~160 integrations, and coding agents that can actually use your tools.

Website · Docs · Self-hosting · Discord · Contributing

Quick start

Try NoClick with npx — requiresNode.js 18+ and Docker:

npx noclick

Or with one line of shell, no Node required:

curl -fsSL https://noclick.com/install.sh | sh

Or by hand — the same thing, visibly:

git clone https://github.com/noclickapp/noclick.git && cd noclick
./scripts/noclick-setup.sh
docker compose up -d

Each installer path fetches the source, generates this instance's secrets —including the credential-encryption key, which is kept across re-runs — andstarts the stack with Docker Compose. Re-running updates in place. Releases aretags; pin the exact source the installer builds with NOCLICK_REF=v0.2.0. Theinstaller deliberately builds that checkout locally. If you operate the Composestack directly, NOCLICK_VERSION=0.2.0 docker compose up -d instead pins thereleased backend image; the frontend is still built for your public URLs. Everyinstaller option is documented at the top of install.sh.

Then open the editor at http://localhost:3000.

What is NoClick?

NoClick lets you build automations on a visual canvas and run them on triggers —webhooks, schedules, inbound email, or chat messages from Slack, WhatsApp andfriends. What makes it different is the agent layer: an AI agent node can drivereal coding harnesses (Claude Code, Codex, opencode, hermes, OpenClaw) and callyour connected integrations as tools, so an agent can read a Linear issue, workin a git repo, and post the result back to Slack.

This repository is the platform: the workflow engine, every integration node,the React editor, the realtime collaboration layer, the AI workflow builder,and an MCP server. It's the same code that runs noclick.com.

What you can build

• Automations on a canvas — chain ~160 integrations (Slack, Gmail, Notion,Linear, HubSpot, Stripe, Postgres, Google Sheets, …) with branching,iteration, filters, and code nodes.
• Triggers — webhooks, cron schedules, inbound email, and app events fromSlack/Discord/HubSpot; channel-style agents that reply where they're spokento, with as many triggers per workflow as you need.
• AI agents with real tools — wire integration nodes into an agent's toolhandle and it can call those operations directly. Agent nodes run eitherin-process (any OpenAI/Anthropic/OpenRouter-compatible model) or as a codingharness using your own installed CLI.
• Interfaces — publish a form, dashboard, or chat over any workflow.
• Build with AI — describe what you want and the builder assembles theworkflow on the canvas. It's also exposed over MCP, so you can point ClaudeCode (or any MCP client) at your instance and have it build for you.

How it works

1. Describe it. Type what you want into the builder — or point any MCPclient at your instance and let your coding agent do the describing.
2. The builder assembles it. Nodes appear on the canvas wired to realoperations, asking only for what it genuinely needs: credentials, and thechoices only you can make.
3. It runs on triggers. A message arrives, a webhook fires, a scheduleticks — the workflow executes, agents call their tools, and results landwhere you told them to. Every run records its tool calls, timings, and theagent's response, so you can see exactly what happened.

Self-hosting

The installer above is the fast path. For a real deployment — your own Postgres,object storage, OAuth apps for integrations, model providers, and theenvironment variables each side needs — read theself-hosting guide.

The deploy buttons above ask for nothing: each provider creates a Postgresdatabase next to the reviewed release image, and the instance does the rest onfirst boot — it runs its own auth layer, prepares the database, and generatesits own keys. Railway uses railway.template.json,Render render.yaml, DigitalOcean.do/deploy.template.yaml, and Flyfly.toml. See thehosted deployment guide forwhat each one provisions and where its secrets live.

Releases are what you run: main moves with every upstream merge, tags aredeliberate cuts, and each tag publishes images to GHCR so the compose stackpulls rather than builds. Pin with NOCLICK_VERSION.

Developing from source

Prerequisites: Docker, the Supabase CLI,Python 3.12 (3.13 isn't supported yet — some pinned wheels don't build on it),Node.js 20 or newer, and pnpm 10.34.4 (or npm for running package scripts).

pip install -r requirements.txt
make local

That boots everything on your machine — a local Supabase (Postgres, auth,storage), the backend, and the frontend — and prints a URL. Sign up with anyemail; local auth confirms instantly. No cloud account, no API keys required toget to a running canvas.

# Backend
cd backend && python server.py       # or: uvicorn server:web_app
pytest                               # test suite

# Frontend
cd frontend && npm run dev
npm run typecheck && npm run build && npm test

# Database migrations
cd infra && supabase migration up --local

Architecture

Node config UIs are generated from the backend's Pydantic models, so adding anintegration is mostly writing one Python module — the editor picks it up.

NoClick Cloud

noclick.com is the hosted platform. It runs this engineplus managed infrastructure: retained agent runtimes so turns resume instantly,scaled webhook and cron delivery, additional hosted builder capabilities, andmanaged storage and email. Self-hosted and cloud share the same workflowformat, so workflows move between them unchanged.

Contributing

Issues and pull requests are welcome. Adding an integration node is the easiestplace to start: copy the closest existing node in backend/nodes/, register itin backend/nodes/core/registry.py, and the config UI generates itself.

CONTRIBUTING.md covers the architecture you need to knowand the conventions this codebase enforces. AGENTS.md / CLAUDE.md carry thesame guidance for coding agents, so pointing Claude Code or Codex at a checkoutgets you working changes rather than plausible-looking ones.

Come say hello in Discord — it's thefastest way to get a question answered.

License

Sustainable Use License 1.0 — use and modify it for your owninternal business purposes, or for non-commercial and personal use. You may passit on only free of charge and non-commercially. It is source-available ratherthan open source: there is no time-based conversion to a permissive licence, andcommercial redistribution — including offering it as a hosted service — needs aseparate agreement. LICENSE.md is the authority; this paragraphis a summary and not a term of it.