Documentation Index
Fetch the complete documentation index at: https://docs.pinkfish.ai/llms.txt
Use this file to discover all available pages before exploring further.
Why use this?
Pinkfish can generate interactive HTML pages — but a single workflow can only produce output, it can’t also listen for incoming requests. To build a web page that submits data (like a form), you need two workflows: one that creates the frontend and one that acts as the backend.The Key Concept
In Pinkfish, a workflow produces a result. It can’t also be a server that receives requests. So you split the work:| Workflow | Role | What it does |
|---|---|---|
| Workflow 1 | Frontend | Generates HTML and saves it to file storage |
| Workflow 2 | Backend | Receives form submissions via an API trigger and saves data to the datastore |
Step-by-Step
Step 1: Create the Frontend Workflow
Build a workflow that generates your HTML page and saves it to file storage. Your workflow might have steps that gather data, format content, or do other preparation — but the final step creates the HTML and saves it to a file storage collection. Once saved, you get a URL where anyone can visit the page. Example prompt for the HTML step:Step 2: Create the Backend Workflow
Create a second workflow that will receive and process form submissions. A good technique: paste your HTML into the prompt and ask Pinkfish to build a backend for it. Example prompt:Step 3: Publish the Backend and Create an API Trigger
- Publish your backend workflow
- Create an API trigger on the published workflow — this gives you an endpoint URL that your HTML page can submit data to
- Copy the API trigger URL
Step 4: Connect the Frontend to the Backend
Go back to your frontend workflow and update the HTML to submit to your backend endpoint. Example prompt:Step 5: Test It
- Visit your file storage URL to see the page
- Fill out the form and submit
- Check your datastore collection to verify the data was saved
The Complete Picture
Tips
- Build the frontend first, then use the generated HTML to inform the backend workflow
- The backend can do more than save data — it can look up existing records, send emails, trigger other workflows, or return data for the page to display
- Multiple endpoints: If your page needs to both read and write data, create separate backend workflows for each (e.g. one to fetch existing data, one to save new data)
- Signed links with query params: If you need to pass context to the page (like a customer ID), see Personalized Web Forms with Signed Links for how to embed parameters in the URL

