What to ask your AI assistant
Tabs
Once your assistant is connected, you work with PlatoForms by asking for what you want in plain language — no field ids, no API calls. This page collects the things you can ask, what you get back, and the few things worth knowing before you rely on it. If you haven’t connected yet, start with Connect your AI assistant (MCP).
The prompts below are examples, not commands — phrase them however you like. The one habit that helps is naming the form you mean, because your assistant looks it up by name.
Find a form and see what it collects
- “List my published PlatoForms forms.”
- “Find my form called Customer Intake.”
- “What information does the Customer Intake form collect, and which fields are required?”
You get each form’s name, folder, publish state, and submission count, and for any single form the full field list — every field’s label, type, whether it’s required, its options, and its validation rules. Ask for the draft if you want the unpublished version instead of the live one.
If you have a lot of forms, ask by name rather than for the whole list — your assistant reads at most 200 forms at a time.
Check what has come in
- “Show me submissions to the Order form from last week.”
- “Find the submission where the email field is sarah@example.com.”
- “Show me all the answers in the latest submission to my intake form.”
Your assistant can filter by date range, search submissions by keyword, or look up a submission by an exact field value, then read the full set of answers with their field labels. Field lookups match the whole value exactly, so search for sarah@example.com rather than sarah.
Get a PDF, CSV, or attachment
- “Give me a PDF download link for that submission that expires in 2 hours.”
- “Send me a CSV of that submission.”
- “I need the attachments from yesterday’s submission as a zip.”
PlatoForms creates a time-limited download link for the generated PDF, a CSV of the answers, a zip of the uploaded files, a single attachment, or the signing certificate. You can ask for the link to last 30 minutes, 2 hours, or 7 days; leave it out and the form’s own expiry setting applies.
These links are public until they expire — anyone who has the link can open the file without signing in. Share them the way you would share the file itself.
Send someone a link with fields already filled in
- “Create a single-use link to the intake form with Sarah’s email already filled in, expiring next Friday.”
- “Create 5 tracked links to the registration form for our partner sites.”
You get the link URLs back to share yourself. Prefilled fields are read-only for the recipient unless you ask for them to stay editable, and you can make a link work only once, set an expiry date, or create up to 10 separately tracked links in one go. Every link your assistant creates is named and appears in your invitation list, so your team can see where it came from.
Your assistant never emails on your behalf — it hands you the links and you send them.
Submit an entry to a form
- “Submit a test entry to my Feedback form with rating 5 and the comment ‘MCP test’.”
Your assistant reads the form’s fields first so it knows what each one expects, submits, and tells you exactly what was recorded.
A submission through your assistant is a real submission: it counts toward your plan and can trigger the notification emails, webhooks, and workflows configured on that form. Be explicit when you only want a test. If a request seems to hang, ask your assistant to check the submission list before trying again, so you don’t end up with a duplicate.
Start a new form from a description
- “Create a client intake form for a physiotherapy clinic: contact details, insurance provider, injury history, and a consent signature.”
- “Create a coffee shop customer incident report our staff can fill in, including injury details.”
Your assistant creates the form in your account and gives you a link to open it. The design happens in PlatoForms, not in the chat: when you open that link, the form generator asks a couple of clarifying questions, lets you choose between a classic form and a conversational one, and shows you the proposed field list to edit and confirm before the form is built.
Because the form is designed after you open the link, your assistant can’t tell you which fields it ended up with — the final list is the one you confirm in the builder. If an assistant lists the fields before you’ve opened it, treat that as a guess, not the finished form.
Start a new PDF document
- “Create a one-page service invoice PDF with our company header, an itemized table with quantity and price, and a total line.”
- “List my PDF documents.”
Same idea: you get a link, and opening it starts the document editor’s AI on your description. From there you keep refining the document by chatting with the AI inside the editor, where you can see what it’s changing.
Chain a few steps together
Assistants are at their best when a request spans several steps:
“Find the form with the most submissions, show me the latest submission’s answers, and give me a PDF download link that expires in 2 hours.”
“Submit a test entry to my Customer Feedback form with rating 5, then create a prefilled link for Sarah with her email already filled in.”
What your assistant can’t do
Your assistant works through a fixed set of actions. It cannot do these, and it shouldn’t offer to:
- Change an existing form or document. There is no way to edit fields, labels, layout, theme, or settings from a chat. Make those changes in the builder — or ask for a new form and start from a better description.
- Wire things together. It can’t connect a form to a PDF document, make submissions fill a document automatically, turn a PDF document into a fillable form, or set up workflows, integrations, notifications, or where submissions are sent. Some of these are real PlatoForms features — they live in the app, not in the assistant.
- Publish, share, delete, rename, move, or duplicate forms and documents.
- Send email. It creates links; you decide who gets them.
- Reach anything the connected account can’t. Your assistant sees exactly what that account sees, under the same team permissions and plan limits as the PlatoForms app.
Limits worth knowing
Beyond your plan’s API quota, assistant access is capped at 60 actions per minute and 20 creations per day, counting new forms, new PDF documents, and prefilled links together. Every action also draws on your plan’s API volume — if your assistant reports error 462, that quota is exhausted. Long lists come back trimmed (up to 50 submissions at a time) so a single question can’t pull thousands of records into a chat.
The full list of actions
| Action | What it does |
|---|---|
| Who am I | Confirms which PlatoForms account and team the assistant is connected to |
| List forms | Lists your forms with folder, publish state, and submission count |
| Search forms | Finds a form by name or id |
| Get form fields | Reads a form’s full field schema, live or draft |
| List submissions | Lists a form’s submissions, filtered by date or keyword |
| Find submission by field | Finds submissions where a field exactly matches a value |
| Get submission | Reads every answer in one submission |
| Get download link | Creates a time-limited link to a PDF, CSV, attachment, zip, or signing certificate |
| Submit form | Submits an entry to a published form |
| Create prefilled link | Creates tracked form links with fields already filled in |
| Create form | Creates a new web form from a description and returns a builder link |
| Create PDF document | Creates a new PDF document from a description and returns an editor link |
| List PDF documents | Lists your PDF documents |