Update 03. Send the contact an interactive message.md #441
Conversation
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
Updated the entire documentation along with level+read time+ last updated date. The section to be clubbed under a different documentation, hence not present here.
Contributor
WalkthroughAdds a comprehensive documentation page replacing a placeholder that explains how to send interactive messages (reply buttons, list messages, location requests), creation steps, flow editor usage, constraints, and multilingual translation workflow. No code or runtime behavior changes. (48 words) Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
Pre-merge checks and finishing touches❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
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 |
![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: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
docs/4. Product Features/03. Flows/2. Flow Actions/03. Send the contact an interactive message.md(1 hunks)
🧰 Additional context used
🪛 GitHub Actions: Build and Deploy to Netlify
docs/4. Product Features/03. Flows/2. Flow Actions/03. Send the contact an interactive message.md
[error] 1-2: MDX compilation failed. Cause: Expected a closing tag for
(2:3-2:7) before the end of blockQuote.
🪛 GitHub Actions: Test deployment
docs/4. Product Features/03. Flows/2. Flow Actions/03. Send the contact an interactive message.md
[error] 1-2: MDX compilation failed during 'yarn build' (docusaurus build). Cause: Expected a closing tag for
(2:3-2:7) before the end of blockQuote. Details: {"column":1,"message":"Expected a closing tag for <h3> (2:3-2:7) before the end of blockQuote","line":1,"name":"1:1-2:7"}
...4. Product Features/03. Flows/2. Flow Actions/03. Send the contact an interactive message.md
Outdated
Show resolved
Hide resolved
Re-wrote the existing documentation along with adding the last update date, level and read time. The dynamic fetching from sheets is to be clubbed with another documentation, hence removed it from this documentation.
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (1)
docs/4. Product Features/03. Flows/2. Flow Actions/03. Send the contact an interactive message.md (1)
1-2: Remove the leading blockquote markers around the heading/table.The
>prefix still wraps the heading/table in a blockquote, reproducing the MDX parse error flagged earlier. Drop the>characters so the page renders without the unterminated heading issue.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
docs/4. Product Features/03. Flows/2. Flow Actions/03. Send the contact an interactive message.md(1 hunks)
🧰 Additional context used
🪛 GitHub Actions: Build and Deploy to Netlify
docs/4. Product Features/03. Flows/2. Flow Actions/03. Send the contact an interactive message.md
[error] 12-13: MDX compilation failed. Expected a closing tag for
before the end of paragraph (12:229-12:233).
🪛 GitHub Actions: Test deployment
docs/4. Product Features/03. Flows/2. Flow Actions/03. Send the contact an interactive message.md
[error] 12-13: MDX compilation failed. Cause: Expected a closing tag for
(12:229-12:233) before the end of paragraph.
...4. Product Features/03. Flows/2. Flow Actions/03. Send the contact an interactive message.md
Outdated
Show resolved
Hide resolved
Re-wrote this documentation along with level, last update date and read time. the last part with dynamic fetching from g-sheets is to be clubbed with another existing documentation, hence removed it from here.
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
docs/4. Product Features/03. Flows/2. Flow Actions/03. Send the contact an interactive message.md(1 hunks)
🧰 Additional context used
🪛 GitHub Actions: Build and Deploy to Netlify
docs/4. Product Features/03. Flows/2. Flow Actions/03. Send the contact an interactive message.md
[error] 74-74: MDX compilation failed. Expected a closing tag for
🪛 GitHub Actions: Test deployment
docs/4. Product Features/03. Flows/2. Flow Actions/03. Send the contact an interactive message.md
[error] 74-74: MDX compilation failed during build. Cause: Expected a closing tag for
Comment on lines
71
to
104
| <ul> | ||
| <li>Type - User can select from either of Reply buttons, List message, Location request. </li> | ||
| <ul> | ||
| <li>Reply Buttons: | ||
| <img width="407" height="328" alt="Screenshot 2025-10-09 at 1 30 35 PM" src="https://github.com/user-attachments/assets/8f4baf63-7429-4df1-9498-92b520b15823" /></li> | ||
| <ol> | ||
| <li>Enter the Text of first button option.</li> | ||
| <li>Click on <code>+</code> button and add text of the next button (and <code>+</code> again for 3rd button)</li> | ||
| <li>Select the Attachment Type if you wish to include an attachment.</li> | ||
| <li>Enter the Attachment URL to specify the media you want to include. If <code>Allow dynamic media</code> is checked, the user can add an expression to dynamically fetch the media URL.</li> | ||
| </ol> | ||
| <li>List message: <br /> | ||
| <img width="455" height="417" alt="Screenshot 2025-10-09 at 1 36 30 PM" src="https://github.com/user-attachments/assets/ac1b4802-7dce-4d1b-861b-62b368009641" /></li> | ||
| <ol> | ||
| <li> Enter the List Header – this is the text that will appear on the list button (refer to the preview on the right for reference.</li> | ||
| <li>Enter the Title for List 1 (the preview below shows how list titles and items will be displayed to end users).</li> | ||
| <li>Enter the Title for the first item in List 1.</li> | ||
| <li>Enter List Item description.</li> | ||
| <li>Click on Add list item option to add another list item.</li> | ||
| <li>Click on Add list option to add another list. (Check preview on right to understand better)</li> | ||
| </ol> | ||
| <li>Location request: <br /> | ||
| <img width="263" height="298" alt="Screenshot 2025-10-09 at 1 40 30 PM" src="https://github.com/user-attachments/assets/91278ec8-60f4-4e77-92ef-3ae5581d8a34" /></li> | ||
| <ol> | ||
| <li>Add the message you want to send along with the 'Send Location' button</li> | ||
| <li>To learn more about how the location shared by the end user can be extracted into meaningful data insights, please refer to <a href="https://glific.github.io/docs/docs/Integrations/Google%20Maps%20API%20for%20reverse%20geo%20location">this</a> link.</li> | ||
| </ol> | ||
| </ul> | ||
| <li>Title – The title of the interactive message, used for easy search later. If the checkbox below is selected, the title will also appear at the top of the message for the end user.</li> | ||
| <li>Message - Includes the message content that the user wishes to send to the end user, along with the interaction chosen (button, list, location request)</li> | ||
| <li> Footer – Optional subtext to include at the bottom of the message.</li> | ||
| <li> Tag - Create/ Select a tag so that it is easy to categorize/ search in future. </li> | ||
| <li> Translate option (Please follow <a href="#section3a">this</a> link, to understand its functionality)</li> | ||
| </ul> |
Contributor
There was a problem hiding this comment.
Fix the nested list structure to unblock the MDX build
The pipeline error (“Expected a closing tag for <li>”) comes from the <ul> that sits outside any <li> and the <ol> blocks that live outside the list items they describe. MDX/HTML requires every nested list to be wrapped inside the parent <li>. Please restructure this section so the sublists stay inside their corresponding list items.
-<ul>
- <li>Type - User can select from either of Reply buttons, List message, Location request. </li>
- <ul>
- <li>Reply Buttons:
- <img width="407" height="328" alt="Screenshot 2025-10-09 at 1 30 35 PM" src="https://github.com/user-attachments/assets/8f4baf63-7429-4df1-9498-92b520b15823" /></li>
- <ol>
+<ul>
+ <li>
+ Type - User can select from either of Reply buttons, List message, Location request.
+ <ul>
+ <li>
+ Reply Buttons:
+ <img width="407" height="328" alt="Screenshot 2025-10-09 at 1 30 35 PM" src="https://github.com/user-attachments/assets/8f4baf63-7429-4df1-9498-92b520b15823" />
+ <ol>
<li>Enter the Text of first button option.</li>
<li>Click on <code>+</code> button and add text of the next button (and <code>+</code> again for 3rd button)</li>
<li>Select the Attachment Type if you wish to include an attachment.</li>
<li>Enter the Attachment URL to specify the media you want to include. If <code>Allow dynamic media</code> is checked, the user can add an expression to dynamically fetch the media URL.</li>
- </ol>
- <li>List message: <br />
- <img width="455" height="417" alt="Screenshot 2025-10-09 at 1 36 30 PM" src="https://github.com/user-attachments/assets/ac1b4802-7dce-4d1b-861b-62b368009641" /></li>
- <ol>
+ </ol>
+ </li>
+ <li>
+ List message: <br />
+ <img width="455" height="417" alt="Screenshot 2025-10-09 at 1 36 30 PM" src="https://github.com/user-attachments/assets/ac1b4802-7dce-4d1b-861b-62b368009641" />
+ <ol>
<li> Enter the List Header – this is the text that will appear on the list button (refer to the preview on the right for reference.</li>
<li>Enter the Title for List 1 (the preview below shows how list titles and items will be displayed to end users).</li>
<li>Enter the Title for the first item in List 1.</li>
<li>Enter List Item description.</li>
<li>Click on Add list item option to add another list item.</li>
<li>Click on Add list option to add another list. (Check preview on right to understand better)</li>
- </ol>
- <li>Location request: <br />
- <img width="263" height="298" alt="Screenshot 2025-10-09 at 1 40 30 PM" src="https://github.com/user-attachments/assets/91278ec8-60f4-4e77-92ef-3ae5581d8a34" /></li>
- <ol>
+ </ol>
+ </li>
+ <li>
+ Location request: <br />
+ <img width="263" height="298" alt="Screenshot 2025-10-09 at 1 40 30 PM" src="https://github.com/user-attachments/assets/91278ec8-60f4-4e77-92ef-3ae5581d8a34" />
+ <ol>
<li>Add the message you want to send along with the 'Send Location' button</li>
<li>To learn more about how the location shared by the end user can be extracted into meaningful data insights, please refer to <a href="https://glific.github.io/docs/docs/Integrations/Google%20Maps%20API%20for%20reverse%20geo%20location">this</a> link.</li>
- </ol>
- </ul>
+ </ol>
+ </li>
+ </ul>
+ </li>
<li>Title – The title of the interactive message, used for easy search later. If the checkbox below is selected, the title will also appear at the top of the message for the end user.</li>
<li>Message - Includes the message content that the user wishes to send to the end user, along with the interaction chosen (button, list, location request)</li>
<li> Footer – Optional subtext to include at the bottom of the message.</li>
<li> Tag - Create/ Select a tag so that it is easy to categorize/ search in future. </li>
<li> Translate option (Please follow <a href="#section3a">this</a> link, to understand its functionality)</li>
</ul>This will satisfy the MDX parser and let the Netlify build pass.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| <ul> | |
| <li>Type - User can select from either of Reply buttons, List message, Location request. </li> | |
| <ul> | |
| <li>Reply Buttons: | |
| <img width="407" height="328" alt="Screenshot 2025-10-09 at 1 30 35 PM" src="https://github.com/user-attachments/assets/8f4baf63-7429-4df1-9498-92b520b15823" /></li> | |
| <ol> | |
| <li>Enter the Text of first button option.</li> | |
| <li>Click on <code>+</code> button and add text of the next button (and <code>+</code> again for 3rd button)</li> | |
| <li>Select the Attachment Type if you wish to include an attachment.</li> | |
| <li>Enter the Attachment URL to specify the media you want to include. If <code>Allow dynamic media</code> is checked, the user can add an expression to dynamically fetch the media URL.</li> | |
| </ol> | |
| <li>List message: <br /> | |
| <img width="455" height="417" alt="Screenshot 2025-10-09 at 1 36 30 PM" src="https://github.com/user-attachments/assets/ac1b4802-7dce-4d1b-861b-62b368009641" /></li> | |
| <ol> | |
| <li> Enter the List Header – this is the text that will appear on the list button (refer to the preview on the right for reference.</li> | |
| <li>Enter the Title for List 1 (the preview below shows how list titles and items will be displayed to end users).</li> | |
| <li>Enter the Title for the first item in List 1.</li> | |
| <li>Enter List Item description.</li> | |
| <li>Click on Add list item option to add another list item.</li> | |
| <li>Click on Add list option to add another list. (Check preview on right to understand better)</li> | |
| </ol> | |
| <li>Location request: <br /> | |
| <img width="263" height="298" alt="Screenshot 2025-10-09 at 1 40 30 PM" src="https://github.com/user-attachments/assets/91278ec8-60f4-4e77-92ef-3ae5581d8a34" /></li> | |
| <ol> | |
| <li>Add the message you want to send along with the 'Send Location' button</li> | |
| <li>To learn more about how the location shared by the end user can be extracted into meaningful data insights, please refer to <a href="https://glific.github.io/docs/docs/Integrations/Google%20Maps%20API%20for%20reverse%20geo%20location">this</a> link.</li> | |
| </ol> | |
| </ul> | |
| <li>Title – The title of the interactive message, used for easy search later. If the checkbox below is selected, the title will also appear at the top of the message for the end user.</li> | |
| <li>Message - Includes the message content that the user wishes to send to the end user, along with the interaction chosen (button, list, location request)</li> | |
| <li> Footer – Optional subtext to include at the bottom of the message.</li> | |
| <li> Tag - Create/ Select a tag so that it is easy to categorize/ search in future. </li> | |
| <li> Translate option (Please follow <a href="#section3a">this</a> link, to understand its functionality)</li> | |
| </ul> | |
| <ul> | |
| <li> | |
| Type - User can select from either of Reply buttons, List message, Location request. | |
| <ul> | |
| <li> | |
| Reply Buttons: | |
| <img width="407" height="328" alt="Screenshot 2025-10-09 at 1 30 35 PM" src="https://github.com/user-attachments/assets/8f4baf63-7429-4df1-9498-92b520b15823" /> | |
| <ol> | |
| <li>Enter the Text of first button option.</li> | |
| <li>Click on <code>+</code> button and add text of the next button (and <code>+</code> again for 3rd button)</li> | |
| <li>Select the Attachment Type if you wish to include an attachment.</li> | |
| <li>Enter the Attachment URL to specify the media you want to include. If <code>Allow dynamic media</code> is checked, the user can add an expression to dynamically fetch the media URL.</li> | |
| </ol> | |
| </li> | |
| <li> | |
| List message: <br /> | |
| <img width="455" height="417" alt="Screenshot 2025-10-09 at 1 36 30 PM" src="https://github.com/user-attachments/assets/ac1b4802-7dce-4d1b-861b-62b368009641" /> | |
| <ol> | |
| <li>Enter the List Header – this is the text that will appear on the list button (refer to the preview on the right for reference).</li> | |
| <li>Enter the Title for List 1 (the preview below shows how list titles and items will be displayed to end users).</li> | |
| <li>Enter the Title for the first item in List 1.</li> | |
| <li>Enter List Item description.</li> | |
| <li>Click on Add list item option to add another list item.</li> | |
| <li>Click on Add list option to add another list. (Check preview on right to understand better)</li> | |
| </ol> | |
| </li> | |
| <li> | |
| Location request: <br /> | |
| <img width="263" height="298" alt="Screenshot 2025-10-09 at 1 40 30 PM" src="https://github.com/user-attachments/assets/91278ec8-60f4-4e77-92ef-3ae5581d8a34" /> | |
| <ol> | |
| <li>Add the message you want to send along with the 'Send Location' button</li> | |
| <li>To learn more about how the location shared by the end user can be extracted into meaningful data insights, please refer to <a href="https://glific.github.io/docs/docs/Integrations/Google%20Maps%20API%20for%20reverse%20geo%20location">this</a> link.</li> | |
| </ol> | |
| </li> | |
| </ul> | |
| </li> | |
| <li>Title – The title of the interactive message, used for easy search later. If the checkbox below is selected, the title will also appear at the top of the message for the end user.</li> | |
| <li>Message - Includes the message content that the user wishes to send to the end user, along with the interaction chosen (button, list, location request)</li> | |
| <li>Footer – Optional subtext to include at the bottom of the message.</li> | |
| <li>Tag - Create/ Select a tag so that it is easy to categorize/ search in future.</li> | |
| <li>Translate option (Please follow <a href="#section3a">this</a> link, to understand its functionality)</li> | |
| </ul> |
🧰 Tools
🪛 GitHub Actions: Build and Deploy to Netlify
[error] 74-74: MDX compilation failed. Expected a closing tag for
🪛 GitHub Actions: Test deployment
[error] 74-74: MDX compilation failed during build. Cause: Expected a closing tag for
🤖 Prompt for AI Agents
In docs/4. Product Features/03. Flows/2. Flow Actions/03. Send the contact an
interactive message.md around lines 71–104, the nesting is invalid because child
<ul>/<ol> blocks live outside their parent <li>, causing the MDX parser error;
fix by moving each nested list (the Reply Buttons, List message, and Location
request sublists and their <ol> steps) so they are placed directly inside the
corresponding parent <li>, ensure every <li> that opens contains its nested list
and any images/text, and verify all <li>, <ol>, and <ul> tags are properly
closed so the resulting HTML/MDX has properly nested list structure.
|
🚀 Deployed on https://deploy-preview-441--glific-docs.netlify.app |
SangeetaMishr
approved these changes
Oct 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 entire documentation along with level+read time+ last updated date. The section to be clubbed under a different documentation, hence not present here.
Summary by CodeRabbit