Setup pulse
rsp_9C41 · asked after a first publish
- How was setup?
- 4 / 5
- What was rough?
- Creating the token — the docs step 404s.
- Asked
- 38 seconds after publish succeeded
We're opening Fillo forms to agents. When something breaks, the agent can report it on the spot. When it's a good moment to ask for feedback, it can ask.
Setting Fillo up with a coding agent instead? See agent setup.
Nobody stops mid-task to find your form, and nobody answers the quarterly email. The signal peaks in the moment — then it's gone.
The agent hit the problem and knows exactly what went wrong. It asks your customer first, then files the report — error, versions, workaround included. It lands in your responses like any other.
You pick the moments worth asking about — right after setup, after a first export, the day someone cancels. The agent is already in the conversation, so it just asks. One question, answered in seconds, not a survey email nobody opens.
rsp_9C41 · asked after a first publish
Every published Fillo form already accepts validated responses over the public API. We're building the part where agents find yours — and you stay in control.
One line in your docs or llms.txt shows agents where your forms live.
What each form is for, how to submit — and when to ask.
Agent submissions are marked, so you know which responses came this way.
The request is a published Fillo form. Have your agent submit it — the same round trip your customers' agents will make.
Read https://fillo.so/agent-forms.md and request agent-forms early access for me. Ask me for any answers you're missing, show me the completed form, and submit only after I approve. Then give me the response id.
Curious what your agent reads? agent-forms.md.