Skip to content

Conversation

@SangeetaMishr
Copy link
Collaborator

@SangeetaMishr SangeetaMishr commented Oct 7, 2025

changed expression added steps and more explaintion

Summary by CodeRabbit

  • Documentation
    • Major overhaul of Google Sheets integration guide with new header, updated UI terminology, and reorganized flow sections.
    • Replaced video tutorial with detailed "Read from Google Sheet" and "Add Writable Google Sheet" guides, including end-to-end setup and credentials steps.
    • Added Readable/Writable modes, "Why/When to use Write Mode", many practical examples (Daily Reminders, Dynamic Menu, Surveys, etc.), and sample imagery.
    • Clarified sheet result referencing, template message usage, permissions, and step-by-step configuration.

changed expression added steps and more explaintion
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Oct 7, 2025

Warning

Rate limit exceeded

@SangeetaMishr has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 3 minutes and 16 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between bc9f1e1 and 3d6fefc.

📒 Files selected for processing (1)
  • docs/4. Product Features/03. Flows/2. Flow Actions/12. Link Google Sheets.md (6 hunks)

Walkthrough

The "Link Google Sheets" documentation was restructured: a new HTML header block was added; the content was expanded and reorganized to cover Readable and Writable Google Sheets, setup steps, examples, UI terminology updates, standardized Glific expressions, and clarified @results.sheet.* usage and flow steps.

Changes

Cohort / File(s) Summary
Docs: Google Sheets flow integration
docs/4. Product Features/03. Flows/2. Flow Actions/12. Link Google Sheets.md
Replaced textual header with an HTML header table; removed Video Tutorial and added "Read from Google Sheet" and "Add Writable Google Sheet" sections; introduced Readable and Write Mode subsections with use-cases, setup steps, examples, and sample images; standardized UI terminology (e.g., "Link Google Sheets", "Read" checkbox) and Glific expressions; clarified permission wording and key/row matching; updated flow step numbering, node naming, variable references (e.g., @results.sheet.*), and template message examples using sheet-provided template_uuid; minor editorial edits.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  actor User as User
  participant Flow as Flow (Glific)
  participant GSheets as Google Sheets API

  rect rgb(240,248,255)
  note over Flow,GSheets: Readable Google Sheet (fetch options)
  User->>Flow: Trigger flow that reads sheet
  Flow->>GSheets: Fetch rows (key/filters)
  GSheets-->>Flow: Return rows (values, keys)
  Flow->>User: Send interactive message (options from sheet)
  User-->>Flow: Respond / select option
  Flow->>Flow: Populate variables (e.g., @results.sheet.*)
  end

  rect rgb(245,255,240)
  note over Flow,GSheets: Writable Google Sheet (append/update)
  User->>Flow: Provide input data
  Flow->>GSheets: Append or update row with variables
  GSheets-->>Flow: Return write result (status, row id)
  Flow->>User: Acknowledge / continue flow
  end
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I nibbled on cells with whiskers so bright,
Linked sheets and let rows hop into light. 🥕
Read, write, and template—each column a tune,
Flow paths stitched softly beneath the moon.
Small paws, big changes—our data takes flight.

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Title Check ❓ Inconclusive The current title “Update 12. Link Google Sheets.md” is generic and simply indicates that a file was updated without summarizing the nature of the changes; it also includes the file extension and numbering which aren’t meaningful to a reader looking for the main update. Please choose a more descriptive title that highlights the key updates, for example “Enhance Link Google Sheets flow documentation with read/write examples and improved UI guidance”.
✅ 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.

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

🧹 Nitpick comments (1)
docs/4. Product Features/03. Flows/2. Flow Actions/12. Link Google Sheets.md (1)

64-64: Promote “Examples” labels to proper headings.

Markdownlint flagged the bold text used as a heading. Converting the emphasized “Examples” lines to real headings (e.g., #### Examples) clears MD036 and keeps the structure consistent.

Also applies to: 118-118

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fef017f and 7eaeb6d.

📒 Files selected for processing (1)
  • docs/4. Product Features/03. Flows/2. Flow Actions/12. Link Google Sheets.md (6 hunks)
🧰 Additional context used
🪛 GitHub Actions: Build and Deploy to Netlify
docs/4. Product Features/03. Flows/2. Flow Actions/12. Link Google Sheets.md

[error] 147-147: MDX compilation failed during build. Unexpected character '%' (U+0025) before name in MDX file. Details: Unexpected character % before name, expected a character that can start a name (line 147, column 150). Command: yarn build (Docusaurus build).

🪛 GitHub Actions: Test deployment
docs/4. Product Features/03. Flows/2. Flow Actions/12. Link Google Sheets.md

[error] 147-147: MDX compilation failed during 'yarn build'. Unexpected character '%' (U+0025) before name, expected a character that can start a name (line 147, column 150).

🪛 markdownlint-cli2 (0.18.1)
docs/4. Product Features/03. Flows/2. Flow Actions/12. Link Google Sheets.md

64-64: Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)


118-118: Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

Comment on lines 147 to 149
5. In the next step, `Send contact a message` is used and an expression is given in place of the template selection drop-down. The expression reads <%= `Glific.send_template("@results.sheet.template_uuid", ["@contact.name"] ) %>` and if no variables then `<%= Glific.send_template("@results.sheet.template_uuid", [] ) %>`

![Screenshot 2023-09-15 at 1 56 54 PM](https://user-images.githubusercontent.com/132430123/268223071-9f2730b9-9364-46fc-b062-1bbd39c102f9.png)

Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🔴 Critical

Fix MDX parse failure around <%= expressions.

The inline <%= snippets are parsed as JSX, causing the MDX build to abort (Unexpected character '%' ... line 147). Wrap those expressions in code fences or escape the < so the compiler treats them as plain text. Example fix:

-5. ... The expression reads <%= `Glific.send_template("@results.sheet.template_uuid", ["@contact.name"] ) %>` and if no variables then `<%= Glific.send_template("@results.sheet.template_uuid", [] ) %>`
+5. ... The expression reads:
+
+```elixir
+<%= Glific.send_template("@results.sheet.template_uuid", ["@contact.name"]) %>
+```
+
+If no variables are required, use:
+
+```elixir
+<%= Glific.send_template("@results.sheet.template_uuid", []) %>
+```
🧰 Tools
🪛 GitHub Actions: Build and Deploy to Netlify

[error] 147-147: MDX compilation failed during build. Unexpected character '%' (U+0025) before name in MDX file. Details: Unexpected character % before name, expected a character that can start a name (line 147, column 150). Command: yarn build (Docusaurus build).

🪛 GitHub Actions: Test deployment

[error] 147-147: MDX compilation failed during 'yarn build'. Unexpected character '%' (U+0025) before name, expected a character that can start a name (line 147, column 150).

🤖 Prompt for AI Agents
In docs/4. Product Features/03. Flows/2. Flow Actions/12. Link Google Sheets.md
around lines 147-149, the inline ERB-style snippets like <%= ... %> are being
parsed as JSX/MDX and causing a build error; wrap those expressions in code
fences or escape the opening '<' so the MDX compiler treats them as literal
text. Replace the inline occurrences with fenced code blocks (specifying
language if desired) containing the expressions, and ensure the "no variables"
example is also inside its own fenced block so both render without MDX parsing
errors.

@github-actions
Copy link

github-actions bot commented Oct 7, 2025

@github-actions github-actions bot temporarily deployed to pull request October 7, 2025 12:59 Inactive
@SangeetaMishr SangeetaMishr assigned Fawas003 and unassigned Fawas003 Oct 7, 2025
@SangeetaMishr SangeetaMishr requested a review from Fawas003 October 8, 2025 09:20
@Fawas003 Fawas003 merged commit ac8bb2c into main Oct 9, 2025
7 checks passed
@akanshaaa19 akanshaaa19 deleted the Link-to-the-Google-Sheets.md branch October 22, 2025 09:15
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