Skip to content

Conversation

@mahajantejas
Copy link
Collaborator

@mahajantejas mahajantejas commented Jul 16, 2025

added the documentation + template sheet for anyone to use google sheets with app script to sync sheets as per their org's / program's requirements

Summary by CodeRabbit

  • Documentation
    • Added a comprehensive guide detailing a Google App Script-based solution for resolving Google Sheet sync failures with Glific, including step-by-step setup instructions, error handling, retry mechanisms, and notification features for large-scale WhatsApp campaigns.

added the documentation + template sheet for anyone to use google sheets with app script to sync sheets as per their org's / program's requirements
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 16, 2025

Walkthrough

A new documentation file has been introduced, detailing a Google App Script-based solution to address failures in syncing large Google Sheets with Glific for WhatsApp nudging campaigns. The document provides context, outlines limitations of existing sync methods, and offers step-by-step setup and configuration instructions for the proposed workaround.

Changes

File(s) Change Summary
docs/Use Cases/Solving For Sheet Sync Failures Issues.md Added comprehensive documentation for a Google App Script solution to improve sheet sync reliability with Glific.

Suggested reviewers

  • SangeetaMishr

Poem

In the warren of docs, a new guide appears,
For syncing big sheets, to calm all your fears.
With scripts and retries, and emails that ping,
Your data flows smoothly—oh, what joy it will bring!
So hop to the triggers, let sync bunnies run,
Glific and Sheets, now working as one. 🐇✨


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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions
Copy link

@github-actions github-actions bot temporarily deployed to pull request July 16, 2025 17:09 Inactive
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: 0

🧹 Nitpick comments (8)
docs/Use Cases/Solving For Sheet Sync Failures Issues.md (8)

1-1: Header is visually cluttered and harms readability

The excessive number of &nbsp; entities stretches the header far beyond what’s necessary and can cause unpredictable wrapping on different screen sizes.
Recommend trimming it down to a simple “5-minute read · Advanced” pattern.


6-6: Run-on sentence—split for clarity

The summary line tries to convey too many ideas at once, making it hard to parse. Consider breaking it into two sentences:

-… this Google App Script method provides a scalable and reliable workaround.
+… This Google App Script–based approach provides a scalable, reliable workaround.
+It includes retries, logging, and notifications so you can reach your audience without manual intervention.

9-14: Parenthesis imbalance and minor grammatical issues

Line 13 opens a parenthetical but never closes it, and the clause is hard to follow.

-… (which means data pull for each teachers’ message to share data specific to observations made them, or journey undertaken by them in the LMS. 
+… (meaning Glific must pull data for each teacher to share personalised observations or LMS-journey updates).

15-17: Comma splice and wording

Remove the stray comma and tighten wording.

-The teachers across Nagaland and more geographies, need to access plans specific to them 
+Teachers across Nagaland and other regions need to access plans specific to them

20-21: Typo & wrong verb agreement

“failt” → “fail” and “render these flows useless”.

-The problem arises when the sheets linked in these flows failt to auto-sync, which render these flows useless. 
+The problem arises when the sheets linked in these flows fail to auto-sync, rendering the flows useless.

28-28: Incorrect word: “useful” should be “useless”

The sentence currently states the opposite of the intended meaning.

-… which means, the flows which use these sheet become useful and fail to send any content.
+… which means the flows that use these sheets become useless and fail to send any content.

32-38: Minor wording & article usage

“call sync a sheet” is awkward; “a AppScript” should be “an App Script”.

-Use the Glific APIs to call sync a sheet specific to your org. 
+Use the Glific APIs to trigger a sync for sheets specific to your org.
-… by using time-driven “triggers” which is a AppScript functionality.
+… by using time-driven “triggers”, an App Script feature.

63-66: Grammar & spelling fixes

-Replace the “YOUR-NGO-SHORTCODE” with you the shortcode you use…
+Replace “YOUR-NGO-SHORTCODE” with the shortcode you use…
-Replace “YOUR-EMAIL-ID” on line 165 in order to get notifications to your email, incase this function fails.
+Replace “YOUR-EMAIL-ID” on line 165 to receive failure notifications; use “in case” not “incase”.
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4196c9a and 4bdadb8.

📒 Files selected for processing (1)
  • docs/Use Cases/Solving For Sheet Sync Failures Issues.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/Use Cases/Solving For Sheet Sync Failures Issues.md

[grammar] ~20-~20: Ensure spelling is correct
Context: ...s when the sheets linked in these flows failt to auto-sync, which render these flows ...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[style] ~65-~65: Consider a more concise word here.
Context: ... 5. Replace “YOUR-EMAIL-ID” on line 165 in order to get notifications to your email, incase...

(IN_ORDER_TO_PREMIUM)

@SangeetaMishr SangeetaMishr merged commit 2b57070 into main Jul 17, 2025
7 checks passed
@coderabbitai coderabbitai bot mentioned this pull request Dec 24, 2025
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