Revise LinkedIn provider instructions for clarity + Advertising API r…

[hobojoe1848]

…equest form

Updated text for clarity, added additional information on the Advertising API request form, and corrected minor grammatical errors.

Summary by CodeRabbit

Release Notes

• Documentation
  • Updated LinkedIn provider documentation with guidance on required products: Share on LinkedIn, Advertising API, and Sign In with LinkedIn using OpenID Connect.
  • Improved clarity of setup instructions and corrected terminology for consistency.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[vercel]

@hobojoe1848 is attempting to deploy a commit to the Listinai Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Note

.coderabbit.yaml has unrecognized properties

CodeRabbit is using all valid settings from your configuration. Unrecognized properties (listed below) have been ignored and may indicate typos or deprecated fields that can be removed.

⚠️ Parsing warnings (1)

Validation error: Unrecognized key(s) in object: 'autopilot'

⚙️ Configuration instructions

• Please see the configuration documentation for more information.
• You can also validate your configuration using the online YAML validator.
• 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

Walkthrough

This pull request updates the LinkedIn provider documentation by adding three new required products (Share on LinkedIn, Advertising API, Sign In with LinkedIn), improving developer guidance, and correcting minor terminology inconsistencies in the configuration instructions.

Changes

Cohort / File(s)	Summary
LinkedIn provider documentation pages/providers/linkedin.mdx	Adds three new required LinkedIn products to the list; rewrites developer instructions for clarity ("fill in" → "fill out"); corrects "LinkedIN Page" label to "LinkedIn Page"; adds guidance paragraph about preparing information and clarifying data collection policies.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

• Single documentation file with straightforward wording improvements and additions
• No complex logic or structural changes requiring detailed analysis
• Corrections are self-contained within one cohesive topic (LinkedIn provider setup)

Possibly related PRs

• Add details for Linkedin Pages integration #45 — Both PRs reference the "linkedin-page" integration and redirect URL in LinkedIn provider documentation.
• Update linkedin-page.mdx #59 — Both PRs modify LinkedIn provider docs and add the same three required products (Share on LinkedIn, Advertising API, Sign In with LinkedIn).

Suggested reviewers

• egelhaus

Poem

🐰 LinkedIn docs now shine so bright,
With products listed, left and right,
Three new friends join the fold,
"Fill out" replaces "fill in" of old,
Our documentation's crystal clear! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main changes: revising LinkedIn provider instructions for clarity and adding the Advertising API request form.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ce86e9d and 6bbb839.

📒 Files selected for processing (1)

• pages/providers/linkedin.mdx (1 hunks)

🔇 Additional comments (5)

pages/providers/linkedin.mdx (5)

14-18: Required products list is clear and helpful.

The three required products (Share on LinkedIn, Advertising API, Sign In with LinkedIn using OpenID Connect) are explicitly defined, which provides helpful guidance for developers setting up the integration.

---

22-22: Consistent form terminology.

Using "fill out" for form submission is idiomatic and aligns with standard documentation conventions.

---

24-24: Developer guidance is practical and actionable.

The new paragraph provides useful preparation tips and actionable advice (mentioning the app doesn't collect member data) that helps developers navigate the Advertising API request process successfully. The reference to LinkedIn's official documentation adds credibility.

---

28-28: Correct branding capitalization.

Using "LinkedIn Page" (not "LinkedIN") aligns with official LinkedIn branding standards.

---

36-36: Improved navigation guidance.

Explicitly referencing the "Auth Tab" of the "LinkedIn App in the developer portal" provides clear guidance for locating Client ID and Client Secret.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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