Update 02. Gupshup Setup.md

[SangeetaMishr]

added images and removed broken links

Summary by CodeRabbit

• Documentation
  • Updated pre-onboarding guide with clearer, step-by-step instructions and embedded screenshots for enabling message events via webhooks and updating the display picture.
  • Replaced external link-based guidance with in-document walkthroughs, improving clarity and reducing context switching.
  • Reorganized steps to create a more intuitive navigation flow, including new images and captions.
  • Removed redundant sections to streamline the narrative while preserving the original objectives of webhook enablement and profile updates.

[coderabbitai]

Walkthrough

Updates the Gupshup onboarding documentation to replace link-based instructions with inline, step-by-step guidance and embedded screenshots for enabling message event webhooks and updating the display picture. Removes separate detailed sections, consolidating them into the numbered flow with new images and references.

Changes

Cohort / File(s)	Summary of changes
Docs: Gupshup setup steps and images docs/2. Pre Onboarding/02. Gupshup Setup.md	Rewrote steps 26–27 to inline instructions for enabling all message events via Webhooks and updating the display picture; embedded new screenshots; removed standalone sections for read receipts and display picture; added updated references/links and revised captions.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• Update and rename 02. Setup an organisation on GupShup.md to 02. Gups… #433 — Also edits the same file with overlapping adjustments to read-receipt/display-picture steps and images.
• Update 02. Facebook Verification Process for WhatsApp Business API.md #320 — Alters Gupshup setup presentation, shifting between external linking and inline walkthroughs, similar topical scope.

Suggested reviewers

• Fawas003
• mahajantejas

Poem

I hopped through docs with screenshot flair,
Rewrote the steps with careful care.
Webhooks on, display set right—
Click, confirm, a tidy sight.
Thump-thump goes my review drum—
Pre-onboarding made less glum. 🐇✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title Check	❓ Inconclusive	The title merely notes an update to a file by name without describing what was changed, such as added images or fixed links, and thus fails to convey the main changes in the PR.	Consider revising the title to summarize the key modifications, for example “Add images and fix broken links in Gupshup setup guide,” so reviewers immediately understand the nature of the changes.

✅ 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 changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch Gupshup_Setup.md

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[github-actions]

🚀 Deployed on https://deploy-preview-454--glific-docs.netlify.app

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6a9a830 and 364b9d7.

📒 Files selected for processing (1)

• docs/2. Pre Onboarding/02. Gupshup Setup.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

docs/2. Pre Onboarding/02. Gupshup Setup.md

[grammar] ~185-~185: There might be a mistake here.
Context: ...iew arrow` beside the app name(as shown in 1st screenshot), go to Webhooks and Ena...

(QB_NEW_EN)

🪛 markdownlint-cli2 (0.18.1)

docs/2. Pre Onboarding/02. Gupshup Setup.md

195-195: Spaces inside link text

(MD039, no-space-in-links)

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Clarify Step 26 wording and spacing.

The sentence is hard to parse ("app name(as...") and repeats phrases. Please rephrase with proper spacing for clarity.

-26.  On the app name click on the `overview arrow` beside the app name(as shown in the below second screenshot), go to Webhooks and Enable all the message events (as shown in the below second screenshot).
+26. Click the overview arrow beside your app name (as shown in the first screenshot), open **Webhooks**, and enable all message events (as shown in the second screenshot below).

📝 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

	26. On the app name click on the `overview arrow` beside the app name(as shown in 1st screenshot), go to Webhooks and Enable all the message events (as shown in the below second screenshot).
	27. Upload a display picture so it can be visible to your end users.Please refere [Update my profile picture of BOT](https://glific.github.io/docs/docs/FAQ/Update%20my%20profile%20picture%20of%20BOT/)
	<img width="1050" alt="image" src="https://github.com/user-attachments/assets/cb70dbb3-12e8-4ad8-9b9b-e09dee793ab8" />
	<img width="692" height="463" alt="image" src="https://github.com/user-attachments/assets/d5dd0207-d48f-42dd-ade6-7593f4f514cf" />
	26. Click the overview arrow beside your app name (as shown in the first screenshot), open **Webhooks**, and enable all message events (as shown in the second screenshot below).
	<img width="1050" alt="image" src="https://github.com/user-attachments/assets/cb70dbb3-12e8-4ad8-9b9b-e09dee793ab8" />
	<img width="692" height="463" alt="image" src="https://github.com/user-attachments/assets/d5dd0207-d48f-42dd-ade6-7593f4f514cf" />

🧰 Tools

🪛 LanguageTool

[grammar] ~185-~185: There might be a mistake here.
Context: ...iew arrow` beside the app name(as shown in 1st screenshot), go to Webhooks and Ena...

(QB_NEW_EN)

🤖 Prompt for AI Agents

In docs/2. Pre Onboarding/02. Gupshup Setup.md around lines 185 to 192, Step
26's sentence is cramped and repetitive ("app name(as..." and duplicated "as
shown"); rephrase it into one or two clear sentences with proper spacing and
punctuation, e.g. state that the user should click the overview arrow beside the
app name, navigate to Webhooks, and enable all message events; remove the
duplicate "as shown" and ensure screenshots are referenced once with a short
caption.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Remove the extra space inside the link text.

markdownlint (MD039) flags the trailing space before the closing bracket.

-27. Please refer to [add display picture ](https://docs.gupshup.io/docs/profile)
+27. Please refer to [add display picture](https://docs.gupshup.io/docs/profile)

📝 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

	27. Please refer to [add display picture ](https://docs.gupshup.io/docs/profile)
	27. Please refer to [add display picture](https://docs.gupshup.io/docs/profile)

🧰 Tools

🪛 markdownlint-cli2 (0.18.1)

195-195: Spaces inside link text

(MD039, no-space-in-links)

🤖 Prompt for AI Agents

In docs/2. Pre Onboarding/02. Gupshup Setup.md around line 195, the markdown
link text contains an extra trailing space before the closing bracket ("add
display picture "); remove that trailing space so the link text reads "add
display picture" to satisfy markdownlint MD039; update the line to use the
corrected link text while keeping the same URL.