Revise WhatsApp Forms documentation and update details#578
Open
mahajantejas wants to merge 2 commits intomainfrom
Open
Revise WhatsApp Forms documentation and update details#578mahajantejas wants to merge 2 commits intomainfrom
mahajantejas wants to merge 2 commits intomainfrom
Conversation
Updated the last updated date and modified the steps for creating WhatsApp forms, including new instructions for data storage and form submission based on the forms phase 2 implementation
Contributor
📝 WalkthroughWalkthroughThis pull request updates the WhatsApp Forms documentation: streamlines the creation flow to emphasize the Form Builder, removes iframe-based publishing steps and Meta Playground references, expands Form Builder details (field types, naming, Option Ids, multilingual notes), adds checklist and lifecycle guidance, and updates the timestamp to February 2026. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
🚀 Deployed on https://deploy-preview-578--glific-docs.netlify.app |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/4`. Product Features/WhatsApp Forms.md:
- Line 46: The document uses the lowercase proper noun "google" in phrases like
"google sheet" and "google service account" (e.g., the text "add a `google
sheet` with write access to the google service account"); update these
occurrences to use the correct capitalization "Google" (e.g., "Google Sheet",
"Google service account") consistently throughout the file, including the
instances referenced at lines 46, 96, and 128.
- Around line 55-58: The doc uses two different lifecycle terms—“Submit to Meta”
(button/step label) and “published” (descriptive state); pick one term and make
it consistent across the guide and FAQs (replace occurrences of “published” with
“Submit to Meta” or vice versa), update the Form Features section lines
referencing the final step (e.g., the “Submit to Meta” button text) and the
FAQ/other sections (previously lines ~223-226 and ~239-245) so they use the
chosen term consistently, and keep the immutability note (“once the form is
submitted to meta, it cannot be changed further”) aligned to the chosen
terminology.
- Around line 42-48: The ordered step lists in WhatsApp Forms.md have skipped
numbers (e.g., 1,2,3,4,6) which breaks continuity; update each "Steps:" ordered
list so numbering is sequential and continuous (e.g., change the block that
currently reads 1,2,3,4,6 to 1,2,3,4,5) and repeat the same fix for the other
occurrences referenced (the lists around lines 61-65 and 154-156); ensure every
"Steps:" section and its items are renumbered to a consecutive sequence without
gaps so users can follow instructions linearly.
- Line 121: The emphasis contains trailing spaces ("**Implications of the id
**"); remove the extra space inside the bold markers so the text reads
"**Implications of the id**" to satisfy markdownlint MD037 and render correctly;
update the heading in the WhatsApp Forms document where the string "Implications
of the id **" appears.
Comment on lines
42
to
+48
| Steps: | ||
| 1. Go to `Quick Tools` → `WhatsApp Forms` in Glific. | ||
| 2. Click `Create Form` | ||
| 3. Go to WhatsApp Flows Playground to get a friendly interface to create your form | ||
| 4. Choose field types and design your form (text input, radio, multi-select, etc.) | ||
| 5. Click on `copy flow JSON` after completing the form design | ||
| 6. Paste the Flow JSON into the `form JSON` input field | ||
| 7. Give your form an appropriate `title`, `description` and `category` | ||
| 8. Click on `Save` | ||
| 9. This creates a draft of the form | ||
| 10. On the `WhatsApp Forms` Listing page, click on the publish icon to publish the form. | ||
| 2. Click `Create` Form | ||
| 3. Provide a form `title` and `category` | ||
| 4. For data storage, add a `google sheet` with write access to the google service account to automatically capture the responses to the form. This step is optional. A google sheet can be added before the form is `submitted to Meta` | ||
| 6. Click on Save and go to the form builder interface | ||
| <img width="568" height="386" alt="Screenshot 2026-02-24 at 3 51 24 PM" src="https://github.com/user-attachments/assets/15e81cc8-0da5-43a0-95fd-298177bb567a" /> |
Contributor
There was a problem hiding this comment.
Fix broken step numbering.
There are skipped numbers in multiple step lists (e.g., 4→6, 2→4, 1→3), which makes the instructions hard to follow. Please renumber for continuity.
Also applies to: 61-65, 154-156
🧰 Tools
🪛 LanguageTool
[uncategorized] ~46-~46: “Google” is a proper noun and needs to be capitalized.
Context: ...google sheet with write access to the google service account to automatically captur...
(A_GOOGLE)
[uncategorized] ~46-~46: “Google” is a proper noun and needs to be capitalized.
Context: ...s to the form. This step is optional. A google sheet can be added before the form is `...
(A_GOOGLE)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/4`. Product Features/WhatsApp Forms.md around lines 42 - 48, The ordered
step lists in WhatsApp Forms.md have skipped numbers (e.g., 1,2,3,4,6) which
breaks continuity; update each "Steps:" ordered list so numbering is sequential
and continuous (e.g., change the block that currently reads 1,2,3,4,6 to
1,2,3,4,5) and repeat the same fix for the other occurrences referenced (the
lists around lines 61-65 and 154-156); ensure every "Steps:" section and its
items are renumbered to a consecutive sequence without gaps so users can follow
instructions linearly.
| 10. On the `WhatsApp Forms` Listing page, click on the publish icon to publish the form. | ||
| 2. Click `Create` Form | ||
| 3. Provide a form `title` and `category` | ||
| 4. For data storage, add a `google sheet` with write access to the google service account to automatically capture the responses to the form. This step is optional. A google sheet can be added before the form is `submitted to Meta` |
Contributor
There was a problem hiding this comment.
Capitalize “Google” consistently.
Multiple instances use “google” in running text. Please capitalize the proper noun.
Also applies to: 96-96, 128-128
🧰 Tools
🪛 LanguageTool
[uncategorized] ~46-~46: “Google” is a proper noun and needs to be capitalized.
Context: ...google sheet with write access to the google service account to automatically captur...
(A_GOOGLE)
[uncategorized] ~46-~46: “Google” is a proper noun and needs to be capitalized.
Context: ...s to the form. This step is optional. A google sheet can be added before the form is `...
(A_GOOGLE)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/4`. Product Features/WhatsApp Forms.md at line 46, The document uses the
lowercase proper noun "google" in phrases like "google sheet" and "google
service account" (e.g., the text "add a `google sheet` with write access to the
google service account"); update these occurrences to use the correct
capitalization "Google" (e.g., "Google Sheet", "Google service account")
consistently throughout the file, including the instances referenced at lines
46, 96, and 128.
Comment on lines
+55
to
+58
| 1. Form Json - this allows you to toggle to the from json view, and edit things in the form json as it gets developed by adding screens and components from | ||
| 2. Save Draft - while the changes being made are auto-saved, this button is provided as a back-up. | ||
| 3. Submit to Meta - this is the final step of form creation. Click on `Submit to meta` once the form is ready to be used by over WhatsApp. Please note: once the form is submitted to meta, it cannot be changed further. To make changes, a new form will need to be created and modified. | ||
|
|
Contributor
There was a problem hiding this comment.
Align lifecycle terminology (“Submit to Meta” vs “published”).
The doc states forms must be “submitted to Meta” and then later says they must be “published.” These appear to describe the same lifecycle step; inconsistent terminology will confuse users. Please standardize on one term across the guide and FAQs.
Also applies to: 223-226, 239-245
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/4`. Product Features/WhatsApp Forms.md around lines 55 - 58, The doc
uses two different lifecycle terms—“Submit to Meta” (button/step label) and
“published” (descriptive state); pick one term and make it consistent across the
guide and FAQs (replace occurrences of “published” with “Submit to Meta” or vice
versa), update the Form Features section lines referencing the final step (e.g.,
the “Submit to Meta” button text) and the FAQ/other sections (previously lines
~223-226 and ~239-245) so they use the chosen term consistently, and keep the
immutability note (“once the form is submitted to meta, it cannot be changed
further”) aligned to the chosen terminology.
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
♻️ Duplicate comments (3)
docs/4. Product Features/WhatsApp Forms.md (3)
46-46:⚠️ Potential issue | 🟡 MinorCapitalize “Google” consistently.
Line 46, Line 96, and Line 128 use “google” in running text. Please standardize to “Google” (e.g., “Google Sheet”, “Google service account”).
Also applies to: 96-96, 128-128
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/4`. Product Features/WhatsApp Forms.md at line 46, The document uses lowercase “google” in several places; update each occurrence to use the proper capitalization: change "google sheet" to "Google Sheet", "google service account" to "Google service account", and any other instances of "google" in running text (e.g., the phrase "submitted to Meta" context) so all mentions are consistently capitalized (check the occurrences matching the diff strings "google sheet", "google service account", and surrounding text on the flagged lines).
57-57:⚠️ Potential issue | 🟠 MajorStandardize lifecycle terminology across the guide.
Line 57/131/138 use “submitted to Meta,” while Line 224–226 and Line 241/245 use “published.” Please pick one canonical lifecycle term and apply it consistently across steps, checklist, notes, and FAQs.
Also applies to: 131-131, 138-138, 223-226, 241-245
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/4`. Product Features/WhatsApp Forms.md at line 57, Choose a single canonical lifecycle term (e.g., "published" or "submitted to Meta") and replace all inconsistent occurrences—specifically the phrases "Submit to Meta", "`Submit to meta`", "submitted to Meta", and "published"—so the guide uses that one term consistently in steps, checklists, notes, FAQs and any button text; ensure casing is consistent (Meta vs meta) and update the sentence in the step that currently reads "Submit to Meta - this is the final step..." plus the checklist and FAQ entries that reference "published" to use the chosen canonical phrase.
42-47:⚠️ Potential issue | 🟡 MinorFix skipped numbering in ordered lists.
Line 47, Line 65, Line 156, and Line 243 continue lists with missing numbers. Please renumber these lists sequentially for readability and consistency.
Suggested renumbering
-6. Click on Save and go to the form builder interface +5. Click on Save and go to the form builder interface ... -4. Please note, the preview mode is not fully representative ... +3. Please note, the preview mode is not fully representative ... ... -3. Take a note of all the these form field names +2. Take a note of all these form field names ... -3. What is the published state +2. What is the published stateAlso applies to: 61-65, 154-156, 239-247
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/4`. Product Features/WhatsApp Forms.md around lines 42 - 47, The ordered lists under the "Steps:" blocks in WhatsApp Forms.md have skipped/misaligned numbers (e.g., the sequence showing "1. Go to `Quick Tools` → `WhatsApp Forms`, 2. Click `Create` Form, 3. Provide a form `title` and `category`, 4. For data storage..., 6. Click on Save..." and similar elsewhere); update each ordered list so numbers are sequential (1,2,3,4,5...) throughout the document, fixing the lists that start with the "Steps:" heading and other list blocks that include items referencing `google sheet`, `submitted to Meta`, and the form builder instructions so all list items follow correct numeric order.
🧹 Nitpick comments (1)
docs/4. Product Features/WhatsApp Forms.md (1)
50-57: Do a quick editorial cleanup pass for clarity.Several new sections have grammar/wording slips that make instructions harder to scan (e.g., Line 55, Line 57, Line 79, Line 87, Line 109, Line 123, Line 130). A brief proofread pass will materially improve readability.
Also applies to: 79-79, 87-87, 109-123, 127-131, 135-138
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/4`. Product Features/WhatsApp Forms.md around lines 50 - 57, Perform a brief editorial cleanup of the "Navigating the form builder interface." section and the other flagged blocks by fixing grammar, punctuation, capitalization, and clarity; specifically: reword the intro to be a complete sentence, normalize action names ("Form JSON" not "Form Json", "Submit to Meta" capitalization consistent), correct typos ("from json view" → "form JSON view", "over WhatsApp" → "on WhatsApp"), and simplify the Submit description to state immutability after submission and the need to create a new form for changes; apply the same proofreading rules to the other flagged sections (the blocks around lines noted in the review) to fix sentence fragments, tense/number agreement, and inconsistent styling so instructions are concise and scannable.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In `@docs/4`. Product Features/WhatsApp Forms.md:
- Line 46: The document uses lowercase “google” in several places; update each
occurrence to use the proper capitalization: change "google sheet" to "Google
Sheet", "google service account" to "Google service account", and any other
instances of "google" in running text (e.g., the phrase "submitted to Meta"
context) so all mentions are consistently capitalized (check the occurrences
matching the diff strings "google sheet", "google service account", and
surrounding text on the flagged lines).
- Line 57: Choose a single canonical lifecycle term (e.g., "published" or
"submitted to Meta") and replace all inconsistent occurrences—specifically the
phrases "Submit to Meta", "`Submit to meta`", "submitted to Meta", and
"published"—so the guide uses that one term consistently in steps, checklists,
notes, FAQs and any button text; ensure casing is consistent (Meta vs meta) and
update the sentence in the step that currently reads "Submit to Meta - this is
the final step..." plus the checklist and FAQ entries that reference "published"
to use the chosen canonical phrase.
- Around line 42-47: The ordered lists under the "Steps:" blocks in WhatsApp
Forms.md have skipped/misaligned numbers (e.g., the sequence showing "1. Go to
`Quick Tools` → `WhatsApp Forms`, 2. Click `Create` Form, 3. Provide a form
`title` and `category`, 4. For data storage..., 6. Click on Save..." and similar
elsewhere); update each ordered list so numbers are sequential (1,2,3,4,5...)
throughout the document, fixing the lists that start with the "Steps:" heading
and other list blocks that include items referencing `google sheet`, `submitted
to Meta`, and the form builder instructions so all list items follow correct
numeric order.
---
Nitpick comments:
In `@docs/4`. Product Features/WhatsApp Forms.md:
- Around line 50-57: Perform a brief editorial cleanup of the "Navigating the
form builder interface." section and the other flagged blocks by fixing grammar,
punctuation, capitalization, and clarity; specifically: reword the intro to be a
complete sentence, normalize action names ("Form JSON" not "Form Json", "Submit
to Meta" capitalization consistent), correct typos ("from json view" → "form
JSON view", "over WhatsApp" → "on WhatsApp"), and simplify the Submit
description to state immutability after submission and the need to create a new
form for changes; apply the same proofreading rules to the other flagged
sections (the blocks around lines noted in the review) to fix sentence
fragments, tense/number agreement, and inconsistent styling so instructions are
concise and scannable.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated the last updated date and modified the steps for creating WhatsApp forms, including new instructions for data storage and form submission based on the forms phase 2 implementation
Summary by CodeRabbit