Skip to content

docs: add the Salesforce live data source - #1812

Draft
sdolidze wants to merge 3 commits into
mainfrom
docs/salesforce-live-data-source
Draft

sdolidze wants to merge 3 commits into
mainfrom
docs/salesforce-live-data-source

Conversation

@sdolidze

Copy link
Copy Markdown
Contributor

Draft docs for lightdash/lightdash#32992 (tracked in lightdash/lightdash#32991). Merge after that PR ships.

Adds a Salesforce page under Live data sources: connecting with OAuth (production or sandbox), the fields that come from the object's describe, filters, limits and troubleshooting. Self-hosting gains the Connected App setup and SALESFORCE_OAUTH_CLIENT_ID / SALESFORCE_OAUTH_CLIENT_SECRET.

Live data sources ─┬─ ... Attio
                   └─ Salesforce   (new page, card, nav, self-host env vars)

Test plan: docs.json parses; page follows the LinkedIn Ads page layout. Not checked against a real org.

@mintlify

mintlify Bot commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
lightdash 🟢 Ready View Preview Nov 20, 2026, 11:57 AM

💡 Tip: Enable Automations to automatically generate PRs for you.

@github-actions

github-actions Bot commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Documentation validation

❌ 1 blocking finding(s), including 0 auto-fixable.

Location Rule Finding
integrations/live-data-sources/salesforce.mdx:1 frontmatter.description-length Description is 104 characters; cards crowd past 100.

Component system

73 finding(s) across the corpus. Largest: prose.filler-word 24 · heading.question 24 · prose.anchor-index 13 · heading.overview 10 · prose.interface-narration 1.

Findings on lines this pull request touched are annotated inline in Files changed.

View the validation run.

@github-actions

Copy link
Copy Markdown
Contributor

I refreshed the sidebar navigation index in ff27fc3 to match the navigation, page titles, and API schema.

Next: someone with write access needs to select Approve workflows to run in the PR merge box. GitHub requires this approval because the update uses GITHUB_TOKEN. The follow-up CI run must pass on the corrected commit before merging.

View the index update run.

This branch was successfully deployed

1 active deployment
staging — ff27fc38 Deployed Nov 20, 2026 by mintlify[bot]
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.

1 participant