Public forms & webhooks

Most workflows need information from outside your workspace. assess.one gives every workflow two ways to receive it — public forms and inbound webhooks — and both are set up for you automatically when the AI builds the workflow. You never configure them by hand; you describe what you need, and you refine it in plain language.

Public forms

When you describe a process that collects information (“a contact form”, “a job application”, “an intake with the customer’s details”), the AI creates the form as part of the workflow, with the fields it needs and the right field types.

• Every form gets a shareable public link. Send it to customers or staff — they don’t need an account to submit it. You’ll find the link on the workflow’s detail page, ready to copy or open.
• A submission starts the workflow. Each submitted form creates (or updates) a record and kicks off the run.
• A workflow can have more than one form (for example, an intake form and a separate follow-up form).

Caution

A public form link is exactly that — public. Anyone with the link can submit the form, so treat it like any shareable URL. assess.one applies rate limiting to protect against abuse, but don’t publish links you intend to keep private.

Inbound webhooks

If your workflow should start when another system sends data in — rather than from a form — the AI sets up a webhook trigger instead. The workflow gets its own webhook endpoint (a URL) that other systems can call.

• The endpoint is stable. Its address never changes, even when you edit or refine the workflow later — so once another system is pointed at it, that integration keeps working.
• Calls are authenticated with webhook keys. From the workflow’s detail page you generate a key, which is shown once (copy it somewhere safe) and can be revoked at any time. The calling system sends the key with each request.
• Incoming data starts a run, creating a record just like a form submission does.

Note

Webhook keys are secrets. Store them securely, use a separate key per integration where you can, and revoke a key immediately if it’s ever exposed.

Changing forms and webhooks

You don’t edit forms or webhooks in a settings screen — you refine the workflow in plain language, and assess.one updates them for you. For example:

• “Add a phone number field to the intake form.”
• “Also collect the invoice amount and a file upload.”
• “Start this workflow from a webhook instead of a form.”

Refinement regenerates the workflow’s forms and steps to match. The webhook endpoint stays stable through all of this, so refining a workflow won’t break a system that’s already calling it.

Next

• Forms & triggers →
• Refining a workflow →
• Workflows & records →