Multi-stepOperations
Give a small process a proper home.
Combine a designed HTML request page, a form, a database, and a team dashboard in one Fermium project folder.
A complete worked example
Give studio requests a front door and a working queue.
Colleagues currently ask for artwork through scattered messages. The design team needs a short request page and a private view of the work.
Fictional project and sample data. This preview does not submit, publish, or change access.
Staff portal; restricted team queue · illustrative result
Need something from the studio?
Start with the brief, attach the material, and give the team a useful deadline.
- 1 · Read the guide
- What to include and expected lead times
- 2 · Send a request
- Brief, due date, and supporting files
- 3 · Team workspace
- Private queue for triage and ownership
A small process with enough structure
The public-facing part explains how to request work. The team uses the response table to prioritize requests and record next steps; submitting a form does not grant access to the queue.
What the recipient can access
Guidance and the request form for the intended staff audience.
Kept out of this handoff
Other requests, team assignments, and internal prioritization.
How it runs
- Design the entry pointBuild an HTML page that explains the process and collects a well-structured request.
- Give the team a workspaceCreate the response database, saved views, and a status chart in the same project folder.
- Add the next step when neededConnect selected submission fields to n8n for background work and keep setup instructions with the project.
- You getA focused place to collect requests and manage the work, with optional webhook automation for more complex background steps.
A prompt to start with
Copy this into your AI tool after connecting it to Fermium. Replace the bracketed details and let it ask for the context it needs.
Create a small request portal in [project folder]: a designed HTML request page, a connected form, a requests database, a pending-work view, and a chart by status. Ask me about the request fields, audience, and team permissions first. Keep internal ownership and status out of the public form. Save partial responses as people work. Include a short setup guide beside the database. Offer a scoped n8n webhook only if we need a background workflow.
What this workflow needs
This foundation supports collection forms and an authenticated team database UI. Arbitrary browser database access, formulas, relational fields, and a full application runtime are future extensions.
Can I build any web application with this?
This is a practical starting point for intake and tracking workflows. Applications needing custom authentication, transactional inventory, or unrestricted browser CRUD need additional capabilities.