create_form
ChatGPTCreate a new draft form in Reuily from a structured design you write. Reuily validates it, auto-corrects small mistakes, applies a theme and saves it unpublished. It does not publish or share anything. Afterwards give the user the edit_url. Images: a question can show an image (imageUrl), choice options can have images (options[].imageUrl), a page can have a cover or background image (branding) and the form can show a logo on every page (logo). Use only image URLs the user gave you or that you found online, never invented ones. Look: themeSelection.presetId picks a gallery theme; colors recolours parts of it. PAGE CATALOG text: Short text response | email: Email input with validation | phone: Phone number input | country: Country picker | textarea: Long text response | date: Date picker | time: Time picker | number: Numeric input | select: Single choice dropdown | radio: Pick one option from a list | checkbox: Select multiple options from a list | yes_no: A simple binary yes or no choice | rating: Star rating input with customizable colors, sizes, and styles | file: File upload field | url: URL input field | signature: Digital signature pad | statement: Show a message before people continue | contact-info: separate input fields: First Name (text), Last Name (text), Email (email), Phone (phone), Company (text) | address: separate input fields: Address (text), Address line 2 (text), City/Town (text), State/Region/Province (text), Zip/Post code (text), Country (country) | welcome: The first page people see, with your branding and a start button | thank-you: The final page users see after submission, with an optional website button | legal: Legal consent, terms, or disclaimer page with agree action | nps: Measures customer loyalty on a 0–10 scale | opinion_scale: Collects feedback on a customizable rating scale | ranking: Drag and drop to order by preference | matrix: Rate multiple items at once | scheduler: Book a meeting | multi-question: separate input fields: Full Name (text), Feedback or Questions (textarea) DESIGN RULES - Prefer one question per page; group only with contact-info, address, or multi-question. - Start with a welcome page in the business's voice (pageTitle, a one-line pageDescription, cta buttonText) unless the request says not to. Add legal only when requested. - Always end with a thank-you in the business's voice: short pageTitle, pageDescription on what happens next, promising only what the request states; never judge the person or their answers (no lead, fit, qualify or submission). - radio for one choice, checkbox for many, select for long lists, yes_no for binary, scheduler for booking. - Single-field pageTitle and label are the question itself; never generic labels. - Choice/ranking need options, matrix rows and columns, scheduler provider/URL. - Put display copy in placeholder for statement, section_header, and cta. - Statement pages are text only: one statement field, never a cta. - Website links live only on the thank-you page, after answers are saved. If a link is requested, give its cta buttonText and set linkHref to the exact user-supplied URL or "https://example.com" if none; never invent any other link. - Require only what the request or normal use requires. Emit special email/phone rules or colors only when asked. COMPLETENESS CHECK BEFORE CALLING - Include every requested question, field and option; quick means concise, not incomplete. - Every if/when needs its trigger, dependent page, and flowRouting. Trace every answer to a rejoin or end; different intermediate branches may submit to the common thank-you. - Requested contact data must be matching inputs, not description text. - Grouped templates: use listed input labels; headings/copy belong in pageTitle/pageDescription. - Never collapse a grouped template into one input named after the group: a contact-info page holds separate inputs, e.g. fields=[{"label":"First Name","field_type":"text"},{"label":"Email","field_type":"email"}]; "Contact information" is a page title, not a label. A message goes on its own textarea page. FORM KIND - fo…
create_form_from_template
ChatGPTCopy a template from list_templates into the workspace as a new unpublished draft.
get_form
ChatGPTRead one Reuily form: status, links, a question outline, and its full content in the same form shape that create_form and update_draft_form accept.
get_form_results
ChatGPTGet aggregate results for a form: views, starts, responses, completion rate, and counts per option for closed questions (choice, rating, NPS, scale, yes/no, ranking, matrix). Also includes quiz scores for quizzes, where responses came from (campaign tags, referrals, websites) and where people leave the form, when the workspace has them. For a period (days, or start_date and end_date) it adds a day-by-day trend, weekly over two months.
list_forms
ChatGPTList forms in the connected Reuily workspace, newest first, with status, response counts and links. Use it to find a form ID before reading or changing a form.
list_responses
ChatGPTRead individual responses to a form, newest first, as question/answer pairs, with each response's quiz score or lead level (hot, warm, no_fit; none when no answer was a good sign or a deal-breaker) and the link details it came with (campaign, referral, website). Filter by answers, lead level, quiz result or score, source, date or text, oldest or newest first. Use it to quote, review or summarize specific submissions. For totals and answer distributions use get_form_results instead.
list_templates
ChatGPTSearch Reuily's library of ready-made form templates by topic or use case.
publish_form
ChatGPTPublish a form so anyone with its public link can open it and submit responses. Only call this when the user explicitly asks to publish or go live.
set_form_link
ChatGPTGive a form a custom, readable link ending on its organization's own domain, e.g. forms.your-company.com/spring-survey. Forms without a custom domain keep their standard link. The text is turned into a URL-safe slug and must be unused in the organization. If the form is already shared, its previous custom link stops working. Only the form's creator can do this, and only on plans with custom links; otherwise explain that.
unpublish_form
ChatGPTStop a published form from accepting new responses. Existing responses are kept and the form can be published again later.
update_draft_form
ChatGPTReplace all pages and questions of an unpublished draft that has no responses, for example after the user asks for changes to a form you just created. Read the form with get_form first, edit its form object, and send the complete result. Follows the same rules as create_form. Leave out themeSelection and colors to keep the current look (get_form's style shows it), and logo to keep the current logo. Published forms or forms with responses are refused so answers are never orphaned; point the user to the builder instead.
update_form_settings
ChatGPTChange when a form accepts responses and whether it runs as a kiosk. Send only the settings to change; get_form shows the current ones. Kiosk mode is for one shared screen used by person after person (a tablet at a booth, front desk or event check in): after each response the form starts over at its first page. Turn it on only when the user describes that setup or asks for it. Closing the form or setting a limit stops new responses, so confirm with the user first.