Refactor _meta.json to rename 'slack' section to 'docs' and update ti…

[vrijraj]

…tle to 'Docs' for improved clarity and consistency in documentation structure.

Summary by CodeRabbit

• New Features

  • Added new Apps and Data Sources documentation section with 16 integrated platforms including Airtable, AWS S3, Firecrawl, Google Drive, Notion, Postgres, Slack, and more.

• Bug Fixes

  • Updated redirect paths for Crawler and Scraper nodes to point to correct integration documentation.

• Documentation

  • Added legacy node slug references to integration pages for historical reference.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
site	Error		Feb 13, 2026 5:50pm

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR establishes a new integrations directory structure for app nodes by creating legacy-to-integration mappings, updating redirect destinations from deprecated node documentation paths to new integration pages, and adding legacy node slug metadata to integration documentation files.

Changes

Cohort / File(s)	Summary
Data Structure & Mappings lib/movedAppNodes.ts	Created new module exporting three key mappings: MOVED_APP_NODES (array of legacy node definitions), LEGACY_NODE_TO_INTEGRATION (legacyPath → integrationSlug), and INTEGRATION_TO_LEGACY_NODES (integrationSlug → legacyPaths array).
Redirect Configuration next.config.mjs	Updated two permanent redirect destinations: crawler-node and scraper-node now redirect to /integrations/apps-data-sources/firecrawl instead of legacy docs paths.
Navigation & Metadata pages/_meta.json, pages/docs/nodes/_meta.json, pages/integrations/apps-data-sources/_meta.json	Fixed indentation formatting in docs entry; added new "apps" entry linking to /integrations/apps-data-sources; created new metadata file with 16 integration mappings (airtable, aws-s3, firecrawl, github, google-drive, google-sheets, n8n, notion, onedrive, postgres, sharepoint, slack, teams, twilio, webflow, websearch).
Integration Documentation pages/integrations/apps-data-sources/airtable.mdx, aws-s3.mdx, firecrawl.mdx, google-drive.mdx, google-sheets.mdx, n8n.mdx, notion.mdx, onedrive.mdx, postgres.mdx, sharepoint.mdx, slack.mdx, twilio.mdx, websearch.mdx	Added legacyNodeSlugs front matter field to each integration page mapping previous node identifiers; google-drive.mdx additionally imports and renders NodeTypeInfo component with batch trigger/action details.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• 404 fix #437 — Updates redirect mappings in next.config.mjs alongside this PR's changes to the same permanent redirects configuration.
• Refactor permanent redirects and update NodesIndex component for impr… #466 — Addresses legacy app node routes and integrations redirects with similar scope of reorganizing app nodes to /integrations/apps-data-sources namespace.
• Dev #449 — Modifies pages/integrations/apps-data-sources/firecrawl.mdx and establishes legacy node-to-integration mappings using the same pattern.

Poem

🐰 Hoppy trails lead far and wide,
Legacy nodes now redirected with pride,
New integrations shine so bright,
Metadata mapped to make all right!

🚥 Pre-merge checks | ✅ 3 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The PR title partially describes the changeset—it mentions renaming a section and updating titles in _meta.json, which is partially relevant, but the changeset involves substantial additional work: adding a new TypeScript module, updating redirect mappings, adding legacyNodeSlugs to multiple integration files, and restructuring documentation navigation.	Revise the title to reflect the full scope of changes, such as 'Add legacy node mappings, update integration redirects, and reorganize documentation navigation' or similar to better represent all significant changes in the PR.

✅ Passed checks (3 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.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main

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

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch docs/google-drive-update

---

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

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

next.config.mjs (1)

107-111: ⚠️ Potential issue | 🟠 Major

permanentRedirects are served with permanent: false — likely unintentional.

The permanentRedirects array is mapped with permanent: false (Line 110), identical to nonPermanentRedirects. If these are truly meant to be permanent (HTTP 308), this should be permanent: true. This is a pre-existing issue but worth noting since this PR adds entries to the permanentRedirects array.

Proposed fix

     ...permanentRedirects.map(([source, destination]) => ({
       source,
       destination,
-      permanent: false,
+      permanent: true,
     })),

🧹 Nitpick comments (1)

pages/integrations/apps-data-sources/google-drive.mdx (1)

19-26: Redundant description across NodeTypeInfo, the paragraph below it, and the Overview paragraph above.

The description prop on NodeTypeInfo (lines 23), the paragraph on line 26, and the overview paragraph on line 17 all convey essentially the same information — that this node is a Batch Trigger for file fetching/sync and an Action node for doc/folder management. Consider removing the free-text paragraph on line 26, since NodeTypeInfo already renders the description and the Overview section already covers it.

Suggested diff

 <NodeTypeInfo
   batchTrigger={true}
   eventTrigger={false}
   action={true}
   description="This node is a Batch Trigger node that automates file fetching and synchronization from Google Drive, and an Action node for creating, editing, and managing docs and folders."
 />
-
-This node is a **Batch Trigger** node that streamlines file collection from Google Drive and prepares files for vectorization and indexing to enhance RAG flows. It also supports **Action** mode for direct operations on Google Drive (create doc, edit file, create folder, list files, move file, get file metadata).