Forms, workflows, and conversations
Connect visitor submissions and clicks to enabled workflows, write clear receipt messages, and add a Chatigram Line.
Collect an answer and take the next step #
A Form groups the inputs a visitor completes. Its submission can send selected fields to an enabled webhook workflow in the same organization. Use this for inquiries, appointment preferences, service requests, and other processes where a visitor supplies information.
A standalone Button can send a fieldless workflow request. Attach an action to the Form submission when the workflow needs answers from the form.
Connect a form #
- Create an enabled webhook workflow in the same organization. Define how it validates, stores, or routes incoming information.
- Add a Form in Studio and place labeled inputs inside it. Give each input a unique field name, such as
name,email, orrequest. - Select the Form and open Actions → When submitted → Run workflow.
- Choose the enabled webhook workflow and select the form fields to send. Send only information the process needs.
- Under Request feedback, set clear sending, accepted, and failed messages. Choose Add action.
- Review View workflow connection. Use Edit workflow connection and Save connection when changing a mapping. Then Save draft and publish the reviewed revision.
Use Workflow Activity to investigate the process after a controlled test submission. Private preview keeps external actions disabled, so it cannot prove that a request was delivered.
Sample inquiry form #
These are suggested labels and field names for a form you configure in Studio, not an importable workflow or a preconnected template.
| Visitor label | Field name | Guidance |
|---|---|---|
| Your name | name |
Ask only for the name you need to reply. |
| Email address | email |
Use the appropriate input mode and a visible label. |
| What would you like help with? | request |
Use TextArea with a short hint. |
| Preferred date | preferredDate |
Optional DateTime; explain that availability must be confirmed. |
Suggested feedback:
- Sending: “Sending your request…”
- Accepted: “Your request was received. Our team will review it and contact you.”
- Failed: “We couldn’t confirm receipt. Check your connection before trying again.”
An acceptance receipt confirms webhook receipt, not successful downstream work. Only promise a booking, payment, order, or other final outcome when your process separately verifies it. For repeated or interrupted submissions, design the workflow to recognize duplicates before performing consequential actions.
Buttons, selections, and dialogs #
Supported explicit clicks, submissions, and item selections can run a configured workflow. Typing, opening a Page, and arbitrary state changes do not automatically invoke a Pages webhook. For an order request, configure and review the bound order source rather than trusting visitor-supplied prices.
To show more detail without leaving the Page, add a Modal, then select a Button and choose Actions → Open a dialog. Choose the dialog and Add action. A Button inside can use Close a dialog. Review the interaction in Private preview and check keyboard access.
Add a conversation #
Add ChatigramLine and choose an organization Line by name and channel under Content. Live Chat uses the existing Chatigram conversation interface. Telegram and WhatsApp need a verified public destination; a Line without one shows its unavailable state.
A visitor’s chat message follows that Line’s own workflow configuration. It is separate from a Form’s webhook connection. Read Lines and channels and Live Chat when configuring the conversation experience.
When embedding, allow the host website for the Page and check the Line’s own origin permissions. Private preview suppresses Line launches.
Respect visitor expectations #
Explain why you collect information and who will respond. Avoid requesting sensitive information on a general public inquiry page. Client-side conditions and hidden widgets do not enforce permissions. Public guest uploads are unavailable; remove FileUpload before publishing and use an appropriate separate process if attachments are needed.