Docs / Getting started
Start here
You have a tenant of your own on a9script. This page is what you received, what to do in the first hour, and where the platform will stop you — so the first refusal you meet is one you have read about.
What you received
- The authoring address: https://a9script.lengauer.biz. Sign in there; everything you build lives there.
- Your endpoints’ address: https://hooks.a9script.lengauer.biz. A webhook you configure is reached under this host, and so is an API or MCP endpoint you expose.
- An invitation mail. Its link works once, for 48 hours. If it has expired, ask the operator for a new one; nobody can hand you a password.
- A tenant with two environments,
sandboxandproduction. They are sealed off from each other; the only way from one to the other is a promotion you perform. - Your role: tenant admin of your tenant. You invite colleagues, open write probes for the sandbox, allow egress ranges, and clear health marks.
- Session limits. A browser session ends after 30 minutes idle or 12 hours absolute; the login screen says which limit signed you out.
First sign-in
Your invitation link sets a password, and the platform then asks for a second factor: an authenticator, and recovery codes shown once, each good for one use. Nothing is switched on until a code from the authenticator proves it holds the secret, so a mis-scanned code locks nobody out — and if both the authenticator and the codes are lost, an administrator clears the factor and you enrol again with the password alone. People and access is the page that walks all of it.
Three ways to build
Start with the first; the other two use what it teaches.
- Your first automation — in the browser, step by step with pictures: a webhook from a shop, a lookup in a CRM, a script of six lines. You need to know what a REST call is; nothing else.
- Build with Claude Code — connect Claude Code in the Claude desktop app to your sandbox and describe the next automation in your own words. It writes, tests and fixes; you review in the browser.
- Working from a terminal — the same work as commands and a folder of files, for CI and scripted changes.
Before the first one, What this platform is explains in a few minutes what is configuration and what is code — the one idea everything else rests on.
Limits you meet first
| Limit | Default |
|---|---|
| Repeats of a transient failure, per call | 3 (at most 10) |
| Statuses never repeated | 400, 401, 404, 422 |
| One wait, at most | 24 hours |
| A debug run’s trace is kept | 7 days |
| A stepped run waits for your move | 1 hour |
| Run rows are kept | 90 days |
The complete table is Limits and safety.
What to watch out for
- Set a mail account to record while building; a redirect sends every recipient’s mail to one inbox; only deliver reaches the real addresses.
- Outbound calls to private addresses are denied unless a tenant admin allows the ranges, so a system inside your own network is not reachable from the beta.
- A credential never travels to production: promote, then enter it there.
- Debug runs, stepped runs and probes are sandbox-only; production refuses them before anything runs.
- A top-level
returnis the run’s result; without one, the final value of a top-leveloutputvariable is. - A health mark stays red or amber until somebody acknowledges it.
- A model’s answer is input; validate it like any other.
Who to write to
office@lengauer.biz — say which tenant, which environment and, for a run, its id. We answer within two working days.