What are Interfaces?
An Interface turns a workflow into a public form anyone can run. You pick which inputs to expose, give them friendly labels, and share a single URL. Visitors fill in the form, click Run, and watch live progress as your workflow executes.
Runners are billed, not authors
When someone runs your Interface, credits are deducted from their ORCFLO account, not yours. You share the workflow; they pay for the execution.When to use Interfaces
Interfaces are a good fit when you want someone other than yourself to run a workflow without giving them access to the editor. Common uses include:
- A colleague-facing tool — let a teammate run a workflow you built without onboarding them to the canvas.
- A customer-facing form — collect input from external users and give them a finished output.
- A one-click utility — package a useful automation as a sharable link for non-technical users.
- A demo of your work — show off a workflow without exposing the underlying steps or prompts.
Setting up an Interface
You configure Interfaces from inside a workflow. Open the workflow you want to share and follow these steps.
Open workflow settings
From the workflow editor, open Settings and select the Interface tab.
Pick a slug
The slug becomes the last part of the public URL — for example, orcflo.com/i/your-slug. Slugs must be unique across ORCFLO.
Write a title and description
Runners see these at the top of the form. Keep the title short and the description focused on what the runner will get back.
Choose which inputs to expose
Select fields from the workflow's declared inputs. Only fields you add to the Interface will appear on the public form. Inputs you don't expose stay internal and keep whatever default value they had.
Save and share
Save the Interface, then copy the public URL and send it to whoever needs to run the workflow.
Screenshot: Settings → Interface tab with title, slug, and fields configured
What runners see
When someone opens your Interface URL, they see a clean form with the title, description, and every field you exposed. The page works for everyone — signed-in or not — but a runner has to be signed in before they can press Run.
Fill in the form
Runners see your exposed fields with the labels and hints you set.
Sign in if needed
Anonymous visitors are redirected to sign in or create an account when they click Run. New accounts come with starter credits.
Watch live progress
After clicking Run, the page shows per-step progress in real time so the runner can see what the workflow is doing.
See the final output
When the workflow finishes, the final output is rendered on the same page.
Screenshot: Public Interface form at orcflo.com/i/<slug>
Screenshot: Live execution view with per-step progress and final output card
Field labels and hints
The names you use inside the workflow editor are often technical (source_url, target_audience). Interfaces let you override these with friendly, human-readable labels and short hints for each exposed field.
Treat the runner like a first-time user
They have no context for what the workflow does. A good label answers "what do I type here?" and a good hint answers "what happens if I leave it blank?"Billing
Credits for every Interface run are deducted from the runner's ORCFLO account. You — the workflow author — are never charged for someone else's run. This is true even if the runner has overage enabled and you don't.
Anyone visiting an Interface URL can read the form, but the Run button requires an authenticated session. Anonymous visitors are bounced to sign-in when they try to run; new accounts get a starter credit grant, so first-time runners can usually complete a workflow without paying.
Where to see runs
You can see executions of your workflow in Execution History, but the credits show up on the runner's account, not yours.Limits in this release
Interfaces are intentionally simple for the first release. The following features are on the roadmap but not yet available:
- Conditional fields — fields that only appear when another field has a specific value.
- Embedding — dropping an Interface into your own website with an iframe or script tag.
- Custom branding — icons, colors, and header images on the Interface page.
- "Keep refining" chat — a chat follow-up after the workflow completes to iterate on the result.
- Custom domains — hosting an Interface on your own domain instead of
orcflo.com/i/<slug>.
If any of these are blocking a use case you have in mind, let us know — it helps us prioritize.
Disabling an Interface
To stop accepting new runs, open the workflow's Settings → Interface tab and toggle Disable interface. The public URL will start showing a "not available" page, but past executions and their outputs are kept and remain visible in Execution History. You can re-enable the Interface at any time without losing your configuration.