Skip to content

Document onboarding process for new Glific chatbot #579

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
SangeetaMishr wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Document onboarding process for new Glific chatbot #579

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e93516c
Document onboarding process for new Glific chatbot
SangeetaMishr Feb 25, 2026
c34dfbc
Update last updated date to February 2026
SangeetaMishr Feb 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
187 changes: 187 additions & 0 deletions docs/2. Pre Onboarding/Adding a New Chatbot in Glific.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,187 @@
<h3>
<table>
<tr>
<td><b>10 minutes read</b></td>
<td style={{ paddingLeft: '40px' }}><b>Level: Beginner </b></td>
<td style={{ paddingLeft: '40px' }}><b>Last Updated: February 2026</b></td>
</tr>
</table>
</h3>


## Starting with another chatbot in Glific
Copy link
Contributor

@coderabbitai coderabbitai bot Feb 25, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Trailing space in heading.

The heading has a trailing space after "Glific ". While typically harmless in rendering, it violates clean Markdown hygiene.

✏️ Proposed fix 
-## Starting with another chatbot in Glific 
+## Starting with another chatbot in Glific
🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@docs/2`. Pre Onboarding/Adding a New Chatbot in Glific.md at line 12, The
heading "## Starting with another chatbot in Glific " contains a trailing space;
open the file and remove the extra space so the heading reads "## Starting with
another chatbot in Glific" (locate that exact heading text in docs/2. Pre
Onboarding/Adding a New Chatbot in Glific.md and trim the trailing whitespace).


If your NGO already has one or more chatbots on Glific and wants to start another, follow the below steps:

### Step 1: Decide on the Use Case & Get a Phone Number

- Identify the purpose of the new chatbot (e.g., survey, support, awareness campaign).

- Get a phone number for this bot.

- **Important:** Do not install WhatsApp on this number.If using an existing number, uninstall WhatsApp from it before connecting to the bot.
Copy link
Contributor

@coderabbitai coderabbitai bot Feb 25, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Missing space after period.

✏️ Proposed fix 
-- **Important:** Do not install WhatsApp on this number.If using an existing number, uninstall WhatsApp from it before connecting to the bot.
+- **Important:** Do not install WhatsApp on this number. If using an existing number, uninstall WhatsApp from it before connecting to the bot.
📝 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
- **Important:** Do not install WhatsApp on this number.If using an existing number, uninstall WhatsApp from it before connecting to the bot.
- **Important:** Do not install WhatsApp on this number. If using an existing number, uninstall WhatsApp from it before connecting to the bot.
🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@docs/2`. Pre Onboarding/Adding a New Chatbot in Glific.md at line 22, Fix the
punctuation in the sentence "**Important:** Do not install WhatsApp on this
number.If using an existing number, uninstall WhatsApp from it before connecting
to the bot." by inserting a space after the period so it reads "...number. If
using an existing number..." — update the line in the "Adding a New Chatbot in
Glific.md" content where that exact sentence appears.


### Step 2: Filling the Glific onboarding form:
Copy link
Contributor

@coderabbitai coderabbitai bot Feb 25, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Trailing colon and inconsistent heading style.

The heading ### Step 2: Filling the Glific onboarding form: has a trailing colon not present in Steps 1 and 3, and uses a gerund form ("Filling") inconsistent with the other step headings.

✏️ Proposed fix 
-### Step 2: Filling the Glific onboarding form:
+### Step 2: Fill the Glific Onboarding Form
📝 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
### Step 2: Filling the Glific onboarding form:
### Step 2: Fill the Glific Onboarding Form
🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@docs/2`. Pre Onboarding/Adding a New Chatbot in Glific.md at line 24, The
heading "### Step 2: Filling the Glific onboarding form:" is inconsistent with
Steps 1 and 3 and has an unnecessary trailing colon; update this heading to
match the style of the others (use an imperative verb and remove the trailing
colon), e.g. change "### Step 2: Filling the Glific onboarding form:" to "###
Step 2: Fill the Glific onboarding form" so it aligns with the phrasing and
punctuation used in Step 1 and Step 3.


- You will receive the Onboarding Form link from the Glific Team. You can refer to this documentation for guidance on how to complete the form.
Copy link
Contributor

@coderabbitai coderabbitai bot Feb 25, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

"this documentation" is missing its hyperlink.

The phrase "refer to this documentation" has no URL attached, leaving the user with no path to the referenced content.

✏️ Proposed fix 
-- You will receive the Onboarding Form link from the Glific Team. You can refer to this documentation for guidance on how to complete the form.
++ You will receive the Onboarding Form link from the Glific Team. You can refer to [this documentation](<INSERT_LINK_HERE>) for guidance on how to complete the form.
📝 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
- You will receive the Onboarding Form link from the Glific Team. You can refer to this documentation for guidance on how to complete the form.
- You will receive the Onboarding Form link from the Glific Team. You can refer to [this documentation](<INSERT_LINK_HERE>) for guidance on how to complete the form.
🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@docs/2`. Pre Onboarding/Adding a New Chatbot in Glific.md at line 26, The
sentence containing "You will receive the Onboarding Form link from the Glific
Team. You can refer to this documentation for guidance on how to complete the
form." is missing a hyperlink on the phrase "this documentation"; update the
Markdown in "Adding a New Chatbot in Glific.md" to replace "this documentation"
with a proper Markdown link pointing to the intended onboarding guidance URL
(e.g., [this documentation](URL)), ensuring the anchor text remains "this
documentation" and the URL is the correct target for the onboarding form
guidance.


### Step 3: Gupshup App Setup (Required)

- Each chatbot needs a separate Gupshup app. As Facebook account is already verified, so no need to redo that.Make sure to Login to your verified Facebook acocunt while doing the GUpshuyp app live process.
Copy link
Contributor

@coderabbitai coderabbitai bot Feb 25, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Multiple typos and grammar issues on this line (also flagged by static analysis).

  • acocunt → account
  • GUpshuyp → Gupshup
  • Login (noun) → log in (verb)
  • Missing space after the period before Make
  • "As Facebook account is already verified, so no need to redo that." is grammatically awkward
✏️ Proposed fix 
-- Each chatbot needs a separate Gupshup app. As Facebook account is already verified, so no need to redo that.Make sure to Login to your verified Facebook acocunt while doing the GUpshuyp app live process.
+- Each chatbot needs a separate Gupshup app. Since your Facebook account is already verified, there is no need to redo that. Make sure to log in to your verified Facebook account while doing the Gupshup app live process.
🧰 Tools
🪛 LanguageTool

[grammar] ~30-~30: Ensure spelling is correct
Context: ...sure to Login to your verified Facebook acocunt while doing the GUpshuyp app live proce...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@docs/2`. Pre Onboarding/Adding a New Chatbot in Glific.md at line 30, Fix the
typos and grammar in the sentence that starts "Each chatbot needs a separate
Gupshup app. As Facebook account..." by replacing "acocunt" with "account",
"GUpshuyp" with "Gupshup", changing the noun "Login" to the verb phrase "log
in", adding the missing space after the period, and rephrasing the awkward
clause to read: "Each chatbot needs a separate Gupshup app. As the Facebook
account is already verified, there is no need to redo that. Make sure to log in
to your verified Facebook account while performing the Gupshup app live
process."


- Log in to [Gupshup.ai](http://Gupshup.ai)
Copy link
Contributor

@coderabbitai coderabbitai bot Feb 25, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🌐 Web query:

Gupshup official login portal WhatsApp Business self-serve

💡 Result:

Gupshup’s official self-serve WhatsApp Business (API) console is accessed via the WhatsApp dashboard:

https://www.gupshup.io/whatsapp/dashboard

Log in there with your Gupshup credentials to manage apps / WhatsApp settings (Self-Serve). [1]

If you’re starting from the main site, use Gupshup’s Login on:

https://www.gupshup.io/

…and then proceed to the WhatsApp dashboard/self-serve flow. [2]

Sources: [1] [2]

🌐 Web query:

Gupshup.io vs Gupshup.ai domain official

💡 Result:

Both domains appear to be officially operated by Gupshup:

  • gupshup.io is Gupshup’s long-standing corporate domain (listed as the company website in reference sources) and is still used in official materials (e.g., “visit: www.gupshup.io” and @gupshup.io media contact emails). [1][2]
  • gupshup.ai is also official and is currently the primary website experience: visiting gupshup.io redirects to gupshup.ai, and the gupshup.ai site links to official docs hosted on docs.gupshup.io (same root domain control). [3][4]

If your goal is to avoid lookalikes/phishing: the safest sign is the direct redirect from gupshup.io → gupshup.ai and cross-linking to docs.gupshup.io. [3][4]

Fix insecure protocol and clarify Gupshup domain.

The link uses http:// instead of https://. Additionally, the correct Gupshup self-serve WhatsApp Business portal is at https://www.gupshup.io/, not gupshup.ai (both are official Gupshup domains, but gupshup.io is the corporate domain for the self-serve console).

✏️ Proposed fix 
-- Log in to [Gupshup.ai](http://Gupshup.ai)
+- Log in to [Gupshup](https://www.gupshup.io/)
📝 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
- Log in to [Gupshup.ai](http://Gupshup.ai)
- Log in to [Gupshup](https://www.gupshup.io/)
🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@docs/2`. Pre Onboarding/Adding a New Chatbot in Glific.md at line 32, Update
the insecure and incorrect Gupshup link: replace the text "Log in to Gupshup.ai"
and its URL using the insecure http scheme with the secure corporate self-serve
console URL "https://www.gupshup.io/" (use https and the gupshup.io domain) so
the instructional line points to the correct, secure Gupshup console.


- Enter an app name (No space or special characters allowed).

This is something internal and not visible to your end users & also **it cannot be changed once setup is completed**. So you can go for something like `GlificChatbot` or `TamilNaduChatbot` etc…

![image](https://user-images.githubusercontent.com/130072273/233287354-f1aafdef-064f-4862-bf28-f392d8c7949b.png)


- Once the App name is entered. It will show as **Created successfully**. Click on `Go to Dashboard`.
Comment on lines +34 to +41
Copy link
Contributor

@coderabbitai coderabbitai bot Feb 25, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Unindented continuation paragraph breaks the bullet list.

The prose on line 36 is not inside a list item, so it terminates the preceding list and starts a new one at line 41. Indent it (or prefix with -) to keep it logically attached to the app name entry step.

✏️ Proposed fix 
 - Enter an app name (No space or special characters allowed).
 
-This is something internal and not visible to your end users & also **it cannot be changed once setup is completed**. So you can go for something like `GlificChatbot` or `TamilNaduChatbot` etc…
+  This is something internal and not visible to your end users & also **it cannot be changed once setup is completed**. So you can go for something like `GlificChatbot` or `TamilNaduChatbot` etc…
🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@docs/2`. Pre Onboarding/Adding a New Chatbot in Glific.md around lines 34 -
41, The continuation prose following the bullet "Enter an app name (No space or
special characters allowed)." is not indented and breaks the list; fix it by
indenting that paragraph (or prefixing it with "- ") so the sentence starting
"This is something internal and not visible to your end users & also **it cannot
be changed once setup is completed**." remains part of the same list item; apply
the same indentation to the example app names line and the screenshot caption so
they stay under the "Enter an app name" bullet.


![image](https://user-images.githubusercontent.com/130072273/233287630-bb1481fb-c34c-493d-8fc2-e1a2d5837000.png)


- Click on the `overview arrow` beside the app name(as shown in the screenshot)

<img width="1050" alt="image" src="https://github.com/user-attachments/assets/cb70dbb3-12e8-4ad8-9b9b-e09dee793ab8" />

- Click on `Settings` >> `Add Partner ID` as `49` and confirm.

<img width="626" alt="image" src="https://github.com/user-attachments/assets/cc8d9f17-0b97-467b-a6d5-417b62eb1d81" />



- Go to dashboarad and then click on the `Go live` button beside your app.
Copy link
Contributor

@coderabbitai coderabbitai bot Feb 25, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Typo: "dashboarad" → "dashboard".

✏️ Proposed fix 
-- Go to dashboarad and then click on the `Go live` button beside your app.
+- Go to dashboard and then click on the `Go live` button beside your app.
📝 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
- Go to dashboarad and then click on the `Go live` button beside your app.
- Go to dashboard and then click on the `Go live` button beside your app.
🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@docs/2`. Pre Onboarding/Adding a New Chatbot in Glific.md at line 56, Fix the
typo in the sentence "Go to dashboarad and then click on the `Go live` button
beside your app." by replacing "dashboarad" with "dashboard" so the line reads
"Go to dashboard and then click on the `Go live` button beside your app." Update
the Markdown content in the Adding a New Chatbot in Glific section accordingly.


![image](https://user-images.githubusercontent.com/130072273/233288175-775d6bbe-0367-4123-8a5e-a91e7ecb2fc7.png)

- Select the type of phone number you wish to configure for your WhatsApp Business Account.

<img width="768" alt="image" src="https://github.com/user-attachments/assets/ab3614a9-a68c-4cdf-8fc4-24ecc33ccb80" />


- Review the `data storage region`, the respective country's WhatsApp free, and select `Proceed`.
Copy link
Contributor

@coderabbitai coderabbitai bot Feb 25, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Unclear phrasing: "WhatsApp free" likely should be "WhatsApp fees".

✏️ Proposed fix 
-- Review the `data storage region`, the respective country's WhatsApp free, and select `Proceed`.
+- Review the `data storage region`, the respective country's WhatsApp fees, and select `Proceed`.
📝 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
- Review the `data storage region`, the respective country's WhatsApp free, and select `Proceed`.
- Review the `data storage region`, the respective country's WhatsApp fees, and select `Proceed`.
🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@docs/2`. Pre Onboarding/Adding a New Chatbot in Glific.md at line 65, Replace
the unclear phrase "WhatsApp free" in the sentence "Review the `data storage
region`, the respective country's WhatsApp free, and select `Proceed`." with
"WhatsApp fees" and adjust punctuation to read naturally (e.g., "Review the
`data storage region`, the respective country's WhatsApp fees, and select
`Proceed`.") so the meaning is clear and grammatically correct.


<img width="894" alt="image" src="https://github.com/user-attachments/assets/e3b77607-a051-4bbc-a010-b2561361a15b" />


- Enter the details of a contact person from your organization (It should be someone who would be managing chatbot work for the organization) & click `Next`button.
Copy link
Contributor

@coderabbitai coderabbitai bot Feb 25, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Missing space between `Next` and "button".

✏️ Proposed fix 
-- Enter the details of a contact person from your organization (It should be someone who would be managing chatbot work for the organization) & click `Next`button.
+- Enter the details of a contact person from your organization (It should be someone who would be managing chatbot work for the organization) and click the `Next` button.
📝 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
- Enter the details of a contact person from your organization (It should be someone who would be managing chatbot work for the organization) & click `Next`button.
- Enter the details of a contact person from your organization (It should be someone who would be managing chatbot work for the organization) and click the `Next` button.
🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@docs/2`. Pre Onboarding/Adding a New Chatbot in Glific.md at line 70, Fix the
typographical spacing in the documentation line that reads "`Next`button" by
inserting a space so it becomes "`Next` button"; locate the exact string
"`Next`button" in the document "Adding a New Chatbot in Glific.md" and update it
to "`Next` button" to ensure proper spacing and readability.


<img width="771" alt="image" src="https://github.com/user-attachments/assets/b2e98ffe-53e0-4eb3-a0dd-d548ec1a5ed9" />

- Click on `Confirm` button.

![image](https://user-images.githubusercontent.com/130072273/233290836-8858c4e3-a4ac-40ad-9f45-aa2dfd8cd349.png)


- Click on `Continue with Facebook` in the next page. It will redirect to Facebook login page.

<img width="772" alt="image" src="https://github.com/user-attachments/assets/06e05787-b9b6-419e-9b64-93d546217fd8" />

- This step will open a pop-up window leading to Facebook.com. Do not close the pop-up window or navigate to a different page.

- Please ensure that your browser is configured to allow pop-ups to load.

- Log into Facebook if you haven't already or click Continue as [your name] if you're already signed in. After logging in, you will be shown an overview of the process of connecting
your number to WhatsApp.

<img width="766" alt="image" src="https://github.com/user-attachments/assets/449ae355-ebd2-4da3-bebb-a4b133600149" />

- Select `Get Started`.

<img width="769" alt="image" src="https://github.com/user-attachments/assets/9516829b-21b5-40f2-92ac-8e391836157b" />

- Fill in your business information and select `Next`.

<img width="773" alt="image" src="https://github.com/user-attachments/assets/12827667-e3d2-4df9-8da0-ed919ca01666" />

- Next, you will be able to select a WhatsApp Business Account (WABA) and WhatsApp Business Profile or create a new one.

<img width="769" alt="image" src="https://github.com/user-attachments/assets/3fcaf45e-905b-4c88-9774-ad0ec0e5c5b6" />

- Now, provide details for your business information.

<img width="767" alt="image" src="https://github.com/user-attachments/assets/c5d759ab-91cc-452a-bdac-80ced08c0449" />

- Create or select your WhatsApp Business account. Then, select Next.

<img width="770" alt="image" src="https://github.com/user-attachments/assets/b30028e1-58ea-4da6-86c6-3c70832424d0" />

- Provide a WhatsApp Business display name and select the category. Then, select Next.

<img width="764" alt="image" src="https://github.com/user-attachments/assets/7853377b-b892-4338-9332-a02290a3f2c0" />

- Next, you will receive a verification code on your registered phone number. Enter the verification code and select Next.

<img width="768" alt="image" src="https://github.com/user-attachments/assets/4dcbe3f6-cd53-421b-b2d9-71f0fbc2cf03" />

- Review the permissions requested and select Continue.

<img width="768" alt="image" src="https://github.com/user-attachments/assets/8ea04b5b-f874-4e06-9832-7325269556ca" />

- You're all set to go. Select Finish.

<img width="767" alt="image" src="https://github.com/user-attachments/assets/23a1b538-7329-4ab3-a898-fa2b5bc8c1e3" />

- Confirm the WABA ID and phone number.

<img width="769" alt="image" src="https://github.com/user-attachments/assets/16533c4c-a074-405f-88aa-debfc169270f" />

- Congratulation! You are now ready to send messages. Select Go to dashboard and your Gupshup App will be `Live`.
Copy link
Contributor

@coderabbitai coderabbitai bot Feb 25, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Grammar: "Congratulation!" → "Congratulations!"

✏️ Proposed fix 
-- Congratulation! You are now ready to send messages. Select Go to dashboard and your Gupshup App will be `Live`.
+- Congratulations! You are now ready to send messages. Select Go to dashboard and your Gupshup App will be `Live`.
📝 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
- Congratulation! You are now ready to send messages. Select Go to dashboard and your Gupshup App will be `Live`.
- Congratulations! You are now ready to send messages. Select Go to dashboard and your Gupshup App will be `Live`.
🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@docs/2`. Pre Onboarding/Adding a New Chatbot in Glific.md at line 132, Change
the incorrect singular "Congratulation!" to the plural "Congratulations!" in the
sentence "Congratulation! You are now ready to send messages. Select Go to
dashboard and your Gupshup App will be `Live`." so the line reads
"Congratulations! You are now ready to send messages. Select Go to dashboard and
your Gupshup App will be `Live`."


<img width="770" alt="image" src="https://github.com/user-attachments/assets/0b81b393-0016-47e7-9f12-bda6eafcf686" />


- 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).

<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" />



- Please refer to [add display picture ](https://docs.gupshup.io/docs/profile)
Copy link
Contributor

@coderabbitai coderabbitai bot Feb 25, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Remove trailing space inside link text (MD039).

[add display picture ] has a trailing space before the closing bracket, flagged by markdownlint.

✏️ Proposed fix 
--  Please refer to [add display picture ](https://docs.gupshup.io/docs/profile)
+-  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
- Please refer to [add display picture ](https://docs.gupshup.io/docs/profile)
- Please refer to [add display picture](https://docs.gupshup.io/docs/profile)
🧰 Tools
🪛 markdownlint-cli2 (0.21.0)

[warning] 147-147: Spaces inside link text

(MD039, no-space-in-links)

🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@docs/2`. Pre Onboarding/Adding a New Chatbot in Glific.md at line 147, The
markdown link text "[add display picture ]" contains a trailing space before the
closing bracket causing MD039; remove the trailing space so the link text reads
"[add display picture]" (keep the target URL unchanged) to resolve the lint
error.



### Connecting Gupshup to Glific:
Copy link
Contributor

@coderabbitai coderabbitai bot Feb 25, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

"Connecting Gupshup to Glific" is not numbered as Step 4.

Steps 1–3 use the ### Step N: … pattern, but this section breaks the convention with a plain heading. Number it for consistency.

✏️ Proposed fix 
-### Connecting Gupshup to Glific:
+### Step 4: Connect Gupshup to Glific
🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@docs/2`. Pre Onboarding/Adding a New Chatbot in Glific.md at line 150, The
heading "Connecting Gupshup to Glific" breaks the established step-heading
convention; change it from an unnumbered "### Connecting Gupshup to Glific:" to
the numbered format used elsewhere (e.g., "### Step 4: Connecting Gupshup to
Glific:") so it follows the `### Step N: …` pattern used in Steps 1–3 and keeps
numbering consistent across the document.


**To connect your Gupshup account with Glific, please follow these steps:**

- Log in to your Gupshup account.

- Make a note of your App Name.

<img width="1050" alt="image" src="https://github.com/user-attachments/assets/cb70dbb3-12e8-4ad8-9b9b-e09dee793ab8" />


- Copy your API Key from the app settings.

**Update Details in Glific**

- Log in to your Glific account.

- Go to Settings.

<img width="167" height="183" alt="image" src="https://github.com/user-attachments/assets/9db69e24-03db-441d-bb8c-3357db211adb" />

- Open the Gupshup section.

- Enter your Gupshup App Name.

- Enter your Gupshup API Key.

Note: You do not need to add the App ID. It will be generated automatically in Glific.

<img width="594" height="480" alt="image" src="https://github.com/user-attachments/assets/2bb32485-60ed-436a-9fa1-9c39e07a5c8e" />

- Click Save.

Once saved, your Gupshup account will be connected to Glific, and messages can start flowing through WhatsApp.