Example

An endpoint your app posts to

Give a system a URL of its own. What it sends lands in your inbox, filtered and stamped the way you configured, and it can do nothing else.

11 steps, driven by an agent. Every step is a step in an end-to-end test, run against a listening server on every pull request, so the graph moves the way the run moved it.

Why it is shaped this way

Anything that can make an HTTP request can put work into your inbox: your own app, a form, a helpdesk, an automation nobody wants to give a Flow account to. You publish an endpoint for it — one URL, one token, and the only thing either can do is write a capture. It cannot read your inbox, cannot see a task and cannot reach a project. What you configure on it is four separate things: which deliveries count, what every capture from it is stamped with, where the source’s own id lives so a retry does not double, and which line of the payload a person should read when the inbox is looked at. A delivery that does not match is not an error — the source did nothing wrong — so it is dropped and counted, and the counters are where a rule written against the wrong field stops being silent. The payload is stored exactly as it arrived, because what makes an inbox worth having is that nothing was decided or discarded on the way in. When the token leaks you rotate it and the URL stays; when the integration ends you revoke the endpoint, and everything it ever captured stays where it is.