Skip to content

FAQ

No. You describe your process in plain language and assess.one builds the workflow. Everything — steps, forms, decisions, dashboards — is generated and editable without code.

Yes. You can generate and preview a workflow before creating an account. When you sign up, the workflow you were working on is saved to your workspace so you can publish and run it.

Write a clear, complete description of your process — who does what, any conditions, what to collect, and the outcomes. See Writing effective prompts.

Can I change a workflow after creating it?

Section titled “Can I change a workflow after creating it?”

Yes. Refine it by describing the change in plain language. For a fundamentally different process, start a new workflow instead.

Usually by submitting its intake form (you can share the link), or by starting it manually. Workflows can also run on a schedule or be triggered by a webhook. See Forms & triggers.

Can my workflow send real emails and texts?

Section titled “Can my workflow send real emails and texts?”

Yes — connect an email/SMS integration (AWS or Twilio) with your own account. Building and previewing don’t require it; sending for real does.

Yes — connect Stripe. Workflows can create payment links (with a fixed or customer-entered amount) and send them to customers. There’s a test mode for trialling safely.

To people by role (e.g. Support, Manager, Finance). This keeps workflows working as team members change. See Tasks & approvals.

Dashboards can only show data that’s saved on the record. Values that live only inside a run (like a task answer) need to be written to the record first. assess.one handles this when building your workflow — see Dashboards & views.

Yes. Each workspace’s data is isolated, and integration credentials are stored encrypted. See Plans & billing.

Reach out to the assess.one team from your workspace, and we’ll help.