Plexara
Endpoints and Forms
701 - An automation that answers a request
An endpoint is a lookup or feed another system calls: an automation with a handle(req) function, bound to an address of its own, that answers each request with JSON computed from platform data. What the handler is handed and what it may return, who binds it (an administrator), the limits a request runs under, what a caller is told when something goes wrong, and how a handler is drafted and tested like any other script. Grounded in the store finder on the demo tenant, which answers every active store in a state.
702 - A lookup a partner system calls
The three access modes an endpoint can have, and the one a partner uses: authenticated, admitting named personas or API keys. A supplier’s replenishment system calls a stock lookup with its own key, under a per-caller rate limit, and every request it makes is one audit row. What a refused caller is told and how refusals are counted by reason, cross-origin rules, signed single-use tokens for pre-authorized links, and the Endpoints page an administrator reads: traffic by status, refusals, p50 and p95, and the busiest callers.
703 - Your first form
Ask the agent for a supplier-onboarding form and it writes one: a form_spec that declares twelve fields, with category and pilot-store choices read from the warehouse each time the form opens, and a form_submit that refuses a malformed tax ID field by field. What the platform checks before the script sees a submission, the field types and their limits, the hosted page, and every accepted submission as a row in a table. The limits are stated where they arise: no conditional logic, no multiple pages, no payments, no respondent receipts, and no visual builder.
704 - Putting the form on your site, or in a report
A form has three places to live: its own address, inside a report or dashboard, and framed on a website an administrator allows. Embedding in an asset works in shared links; embedding on a site needs the site’s origin on the binding. Public forms are protected by named bot checks configured in the portal (proof of work, Turnstile, or hCaptcha), a hidden honeypot field, and a minimum fill time, and this lesson shows each refusing on the demo tenant.
705 - Sensitive fields
A field marked sensitive is encrypted before it is stored, so every copy of a submission, and every query of its table, holds ciphertext. Who can read it in clear (the form owner’s Submissions section and its CSV and Excel exports, and scripts running as a persona the form names), why every read is audited, how a value is sealed to its form and field, what recordings and failed requests keep instead of the value, and why a file field cannot be sensitive.
706 - From submission to action
Each accepted submission is an event in the form’s source, and an automation can run once for every one. The demo tenant’s intake automation checks each supplier application against the warehouse and posts a summary to an operations feed seconds after it is stored. Validation against live data that refuses field by field before anything is stored, what an event run reads, one run per event, what happens on a burst and on a failure, and where a write to another system belongs.
707 - Capstone: the supplier form end to end
The whole supplier program on the demo tenant in one place: the form and its bot check, the page that embeds it, the table its submissions land in, the automation that answers each one, and a report that joins the applications to warehouse stores and categories. With the run history, the Endpoints page figures, and the store finder and partner stock lookup beside it, the 700 series ends where the platform does: data in from people and systems, governed, stored, acted on, and reported.
600 · Automations
The agent writes the script, Plexara runs it on demand, on a schedule, once per event, or per request, and the outputs refresh themselves.
Next series800 · Working with People Outside the Company
Clients, suppliers and partners sign in, open what you share with them, and send files back, and see nothing else.