feat(integrations): add Upsales API integration

[frkst]

Adds Upsales CRM API integration to Nango.

Features:

• API Key authentication via query parameter (token)
• Rate limiting support with X-RateLimit-Reset header
• Offset-based pagination (offset and limit parameters)
• Base URL: https://integration.upsales.com/api/v2

Files added:
Provider configuration in providers.yaml
Documentation at docs/integrations/all/upsales.mdx
Connect guide at docs/integrations/all/upsales/connect.mdx
Logo SVG

---

The integration also surfaces reusable documentation snippets, registers the new pages in the docs navigation, and exposes verification plus rate-limit metadata so client applications can programmatically confirm connectivity and handle throttling guidance.

---

This summary was automatically generated by @propel-code-bot

[my-senior-dev-pr-review]

🤖 My Senior Dev — Analysis Complete

👤 For @frkst

📁 Expert in docs (5 edits)

View your contributor analytics →

---

📊 7 files reviewed • 3 need attention

⚠️ Needs Attention:

• docs/api-integrations/upsales.mdx — Contains essential integration documentation that impacts security and user guidance.

---

🚀 Open Interactive Review →

The full interface unlocks features not available in GitHub:

• 💬 AI Chat — Ask questions on any file, get context-aware answers
• 🔍 Smart Hovers — See symbol definitions and usage without leaving the diff
• 📚 Code Archeology — Understand how files evolved over time (/archeology)
• 🎯 Learning Insights — See how this PR compares to similar changes

---

💬 Chat here: @my-senior-dev explain this change — or try @chaos-monkey @security-auditor @optimizer @skeptic @junior-dev

📖 View all 12 personas & slash commands

You can interact with me by mentioning @my-senior-dev in any comment:

In PR comments or on any line of code:

• Ask questions about the code or PR
• Request explanations of specific changes
• Get suggestions for improvements

Slash commands:

• /help — Show all available commands
• /archeology — See the history and evolution of changed files
• /profile — Performance analysis and suggestions
• /expertise — Find who knows this code best
• /personas — List all available AI personas

AI Personas (mention to get their perspective):

Persona	Focus
@chaos-monkey 🐵	Edge cases & failure scenarios
@skeptic 🤨	Challenge assumptions
@optimizer ⚡	Performance & efficiency
@security-auditor 🔒	Security vulnerabilities
@accessibility-advocate ♿	Inclusive design
@junior-dev 🌱	Simple explanations
@tech-debt-collector 💳	Code quality & shortcuts
@ux-champion 🎨	User experience
@devops-engineer 🚀	Deployment & scaling
@documentation-nazi 📚	Documentation gaps
@legacy-whisperer 🏛️	Working with existing code
@test-driven-purist ✅	Testing & TDD

For the best experience, view this PR on myseniordev.com — includes AI chat, file annotations, and interactive reviews.

[hassan254-prog]

Thank you for the contribution, small comments inline otherwise looks good 💪 .

[hassan254-prog]

For the main docs page, please use the updated styling from the newer docs. You can use this as an example, also updating the docs.json file with the correct file path.

[frkst]

pushed, we good to go?

[hassan254-prog]

@frkst, it looks like this comment may have been missed. Move the files to the new docs directory.

[frkst]

@frkst, it looks like this comment may have been missed. Move the files to the new docs directory.

Sorry I might be stupid, but what exactly is it you want me to change? It looks correct to me so i'm a bit lost

[hassan254-prog]

@frkst, it looks like this comment may have been missed. Move the files to the new docs directory.

Sorry I might be stupid, but what exactly is it you want me to change? It looks correct to me so i'm a bit lost

The new docs folder is located at docs/api-integrations. You can use this reference
when making changes to all the related documentation files.

[frkst]

do you mean like this? or anything else needed?

[frkst]

<3

[bayking]

@hassan254-prog This integration looks ready to merge. Could you re-review when you have a chance?