Skip to content

Conversation

@SangeetaMishr
Copy link
Collaborator

@SangeetaMishr SangeetaMishr commented Jan 23, 2026

Removed the incorrect link, added a few more details on sticker format

Summary by CodeRabbit

  • Documentation
    • Updated "Last updated" timestamp to January 2026.
    • Clarified attachment guidance: separated sticker/audio note from follow-up link and reflowed bullet content.
    • Replaced inline reference links with a standalone documentation link for GIF/attachment details.
    • Specified sticker/image requirement as 512 × 512 px in .webp format.
    • Fixed list/bullet formatting for improved readability.

✏️ Tip: You can customize this high-level summary in your review settings.

Removed the incorrect link, added a few more details on sticker format
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 23, 2026

📝 Walkthrough

Walkthrough

Updated the "Send the contact a message.md" documentation: refreshed Last Updated to January 2026; restructured and reworded Important Notes bullets; replaced a cloud-api link with cloudapi; clarified sticker format as 512 × 512 px .webp.

Changes

Cohort / File(s) Summary
Documentation update
docs/4. Product Features/03. Flows/2. Flow Actions/02. Send the contact a message.md
Updated "Last Updated" timestamp to January 2026; reflowed and reworded Important Notes bullets (removed inline links and separated statements); changed reference path from cloud-api to cloudapi; specified sticker images as 512 × 512 px in .webp; minor formatting adjustments

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

Suggested labels

Screening

Suggested reviewers

  • Fawas003
  • tanuprasad530

Poem

🐰 I hopped through lines both new and old,

timestamps bright and bullets bold,
webp stickers set to size,
links aligned and tidy-wise,
docs refreshed with carroted pride.

🚥 Pre-merge checks | ✅ 2 | ❌ 1
❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Title check ❓ Inconclusive The title is generic and vague—'Update 02. Send the contact a message.md' describes the file being modified rather than the substantive changes made (removing incorrect link, adding sticker format details). Revise the title to be more specific about the actual changes, such as 'Fix documentation links and add sticker format specifications' or 'Update message documentation with corrected links and sticker details'.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@docs/4`. Product Features/03. Flows/2. Flow Actions/02. Send the contact a
message.md:
- Around line 69-70: Fix the malformed list item and wrong URL in the two list
entries: close the first <li> that starts with "WhatsApp business API doesn't
support .gif files to be sent as attachments." by adding the missing </li>,
correct the link in the second list item that currently points to
"https://developers.facebook.com/docs/whatsapp/cloudapi/reference/media" to
"https://developers.facebook.com/docs/whatsapp/cloud-api/reference/media", and
add a space after the period so "follows.To" becomes "follows. To" to resolve
the MDX compilation error.

Comment on lines 69 to 70
<li>WhatsApp business API doesn't support .gif files to be sent as attachments.
<li>Size limits for attachments are as follows.To read more about this, please refer to this <a href="https://developers.facebook.com/docs/whatsapp/cloudapi/reference/media">link</a></li>
Copy link
Contributor

@coderabbitai coderabbitai bot Jan 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

Facebook WhatsApp Cloud API media reference documentation URL

💡 Result:

Official Meta docs (WhatsApp Cloud API → Media reference):

https://developers.facebook.com/docs/whatsapp/cloud-api/reference/media/

(See sections like #upload-media, #retrieve-media-url, #download-media, #delete-media.) (stackoverflow.com)

Meta Postman reference (same endpoints, often easier to follow):

https://www.postman.com/meta/whatsapp-business-platform/request/fpj02x0/retrieve-media-url
https://www.postman.com/meta/whatsapp-business-platform/request/ked0afm/download-media

(postman.com)

Citations:


Fix critical HTML syntax error and incorrect API documentation URL.

Line 69 is missing a closing </li> tag, which causes the MDX compilation to fail and blocks deployment.

Additionally, line 70 contains an incorrect URL path. The Facebook WhatsApp Cloud API documentation uses cloud-api (with hyphen), not cloudapi. The link should be https://developers.facebook.com/docs/whatsapp/cloud-api/reference/media.

Minor issues:

  • Line 70 spacing: follows.To should be follows. To
🐛 Proposed fix
-    <li>WhatsApp business API doesn't support .gif files to be sent as attachments. 
-    <li>Size limits for attachments are as follows.To read more about this, please refer to this <a href="https://developers.facebook.com/docs/whatsapp/cloudapi/reference/media">link</a></li>
+    <li>WhatsApp business API doesn't support .gif files to be sent as attachments.</li>
+    <li>Size limits for attachments are as follows. To read more about this, please refer to this <a href="https://developers.facebook.com/docs/whatsapp/cloud-api/reference/media">link</a></li>
📝 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
<li>WhatsApp business API doesn't support .gif files to be sent as attachments.
<li>Size limits for attachments are as follows.To read more about this, please refer to this <a href="https://developers.facebook.com/docs/whatsapp/cloudapi/reference/media">link</a></li>
<li>WhatsApp business API doesn't support .gif files to be sent as attachments.</li>
<li>Size limits for attachments are as follows. To read more about this, please refer to this <a href="https://developers.facebook.com/docs/whatsapp/cloud-api/reference/media">link</a></li>
🧰 Tools
🪛 GitHub Actions: Build and Deploy to Netlify

[error] 68-70: MDX compilation failed: Expected a closing tag for (69:5-69:9) before the end of paragraph. (MDX: end-tag-mismatch)

🪛 GitHub Actions: Test deployment

[error] 68-70: MDX compilation failed. Expected a closing tag for (69:5-69:9) before the end of paragraph. Cause: End-tag-mismatch (mdast-util-mdx-jsx).

🤖 Prompt for AI Agents
In `@docs/4`. Product Features/03. Flows/2. Flow Actions/02. Send the contact a
message.md around lines 69 - 70, Fix the malformed list item and wrong URL in
the two list entries: close the first <li> that starts with "WhatsApp business
API doesn't support .gif files to be sent as attachments." by adding the missing
</li>, correct the link in the second list item that currently points to
"https://developers.facebook.com/docs/whatsapp/cloudapi/reference/media" to
"https://developers.facebook.com/docs/whatsapp/cloud-api/reference/media", and
add a space after the period so "follows.To" becomes "follows. To" to resolve
the MDX compilation error.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@CodeRabbit can you check fix or not ?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check the current state of lines 68-72 in the file
sed -n '68,72p' "docs/4. Product Features/03. Flows/2. Flow Actions/02. Send the contact a message.md"

Length of output: 498


@SangeetaMishr, the fix has not been applied yet. The file still has the critical issues:

Line 69 - Still has malformed HTML:

<li>WhatsApp business API doesn't support .gif files to be sent as attachments.<li>

Should be:

<li>WhatsApp business API doesn't support .gif files to be sent as attachments.</li>

⚠️ The closing tag <li> needs to be changed to </li>

Line 70 - Still missing space:

<li>Size limits for attachments are as follows.To read more...

Should be:

<li>Size limits for attachments are as follows. To read more...

⚠️ Add a space after the period: follows. To

These issues will continue to cause MDX compilation errors and block deployment until fixed. Please apply the suggested changes from the previous comment.

Copy link
Contributor

@tanuprasad530 tanuprasad530 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The url is line 70 is broken. This is the correct url - https://developers.facebook.com/docs/whatsapp/cloud-api/reference/media
kindly make the changes. The current one referenced exclude the - inside cloud-api

@github-actions
Copy link

@github-actions github-actions bot temporarily deployed to pull request January 23, 2026 08:11 Inactive
@SangeetaMishr
Copy link
Collaborator Author

@tanuprasad530 The issues has been fixed, you can review and merge by tuesday.

@tanuprasad530 tanuprasad530 merged commit e45b7c8 into main Jan 23, 2026
7 checks passed
@tanuprasad530 tanuprasad530 deleted the sne branch January 23, 2026 08:17
@SangeetaMishr SangeetaMishr mentioned this pull request Jan 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants