[inkeep]

Changes

Updates the Vitally data source documentation to reflect the four new tables added in PostHog/posthog#128721:

• Admins - Full refresh sync
• Meetings - Full refresh sync
• Project_Templates - Full refresh sync
• Project_Categories - Full refresh sync

The intro text now mentions "meetings" and "admins" alongside the existing data types, and adds "users" and "projects" which were already supported but missing from the description.

Why

The previous intro text only listed "accounts, conversations, notes, tasks, and more" which didn't reflect the full range of data types available from the Vitally connector. The <SourceTables /> component shows the complete table list automatically, but the intro text should give users a quick overview of the main data types they can sync.

---

This PR was created by the Inkeep Content Writer agent, which is maintained by the Docs and Wizard team. Please reach out on Slack for help if needed.

[github-actions]

Deploy preview

Status	Details	Updated (UTC)
🟢 Ready	View preview	Nov 04, 2026 12:54AM

Changed pages

Page	Source
Linking Vitally as a source	contents/docs/data-pipelines/sources/vitally.md

[github-actions]

Vale prose linter → found 0 errors, 3 warnings, 0 suggestions in your markdown

Full report → Copy the linter results into an LLM to batch-fix issues.

Linter being weird? Update the rules!

contents/docs/data-pipelines/sources/vitally.md — 0 errors, 3 warnings, 0 suggestions

Line	Severity	Message	Rule
30:328	warning	Don't put a comma after 'e.g.,'. Write 'i.e.' or 'e.g.' with no comma after it.	PostHogBase.LatinAbbreviationComma
32:93	warning	'toggleable' is a possible misspelling.	PostHogBase.Spelling
32:189	warning	Don't put a comma after 'e.g.,'. Write 'i.e.' or 'e.g.' with no comma after it.	PostHogBase.LatinAbbreviationComma

[github-actions]

Bundle report

Total JS (gzip)

11.71 MiB (+0.1 KiB / +0.0%)

Eager graph (modules shipped in each entrypoint's initial chunks)

Entrypoint	Eager size	Budget	Modules
✅ app	9.94 MiB (no change)	report-only	1024

Largest modules in the app closure

Module	Size
css ./node_modules/.pnpm/css-loader@5.2.7_webpack@5.101.3/node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[8].oneOf[1].use[1]!./node_modules/.pnpm/postcss-loader@4.3.0_postcss@8.5.6_webpack@5.101.3/node_modules/postcss-loader/dist/cjs.js??ruleSet[1].rules[8].oneOf[1].use[2]!./src/styles/global.css	839.5 KiB
./src/components/Stickers/Stickers.tsx	696.4 KiB
./node_modules/.pnpm/@posthog+icons@0.36.6_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/@posthog/icons/dist/posthog-icons.es.js	354.8 KiB
./node_modules/.pnpm/react-markdown@8.0.7_@types+react@16.14.66_react@18.3.1/node_modules/react-markdown/lib/react-markdown.js + 88 modules	351.4 KiB
./node_modules/.pnpm/framer-motion@14.0.0_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/framer-motion/dist/es/render/components/motion/proxy.mjs + 126 modules	287.2 KiB
./node_modules/.pnpm/cloudinary-core@2.14.0_lodash@4.17.21/node_modules/cloudinary-core/cloudinary-core.js	281.9 KiB
./src/components/SearchUI/index.tsx + 87 modules	273.1 KiB
./gatsby-browser.tsx + 59 modules	259.1 KiB
./node_modules/.pnpm/@posthog+brand@0.13.0_react@18.3.1/node_modules/@posthog/brand/dist/generated/hoggies/svg/construction-1.mjs	248.5 KiB
./src/components/Pricing/PricingSlider/Slider.tsx + 87 modules	240.2 KiB
./node_modules/.pnpm/@posthog+brand@0.13.0_react@18.3.1/node_modules/@posthog/brand/dist/generated/hoggies/svg/construction-2.mjs	228.2 KiB
./node_modules/.pnpm/@posthog+brand@0.13.0_react@18.3.1/node_modules/@posthog/brand/dist/generated/hoggies/svg/magnifying-glass.mjs	221.7 KiB
./src/hooks/skills.tsx + 2 modules	150.7 KiB
./src/hooks/useProduct.ts + 9 modules	149.9 KiB
./src/components/Icons/Icons.tsx	147.4 KiB

---

Eager-graph budgets are report-only until a baseline is established. Sizes are gzip of public/**/*.js; eager size is webpack module source bytes for the modules actually shipped in the entrypoint's initial chunks (post-tree-shake).

[github-actions]

Hey @Gilbert09! This docs PR was generated for you by an agent. You're responsible for reviewing and merging it into production.

1. Review and approve the PR
2. Merge the PR
   a. Check the preview env and CI build and merge it yourself
   b. Enable auto-merge if you're confident in the changes