feat(integrations): add support for ninety-io

[hassan254-prog]

Describe the problem and your solution

• add support for ninety-io

[github-actions]

Preview Deploy

Status	URL	Deploy Logs	Last Updated
✅ Ready	Preview URL	Deploy Logs	13 Jul 2026, 08:58 UTC

[mintlify]

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

Project	Status	Preview	Updated (UTC)
nango	🟢 Ready	View Preview	Jul 8, 2026, 7:12 PM

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

[cubic-dev-ai]

2 issues found across 13 files

Confidence score: 4/5

• In docs/api-integrations/ninety-io.mdx, <Step> components are missing stable id props, so deep links and references can break if steps are reordered, which makes the guide harder to navigate and maintain—add unique semantic id values to each step before merging.
• In docs/api-integrations/ninety-io.mdx, the heading casing is out of convention (Ninety.io integration guides), which won’t break functionality but can create inconsistency across docs—update it to sentence case to align with project standards.

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="docs/api-integrations/ninety-io.mdx">

<violation number="1" location="docs/api-integrations/ninety-io.mdx:12">
P2: Steps are missing semantic `id` props. The project convention requires `id` props on `<Step>` components for deep-linking and stable references across reordering. Add a unique, stable `id` to each step (e.g., `id="create-integration"`, `id="authorize"`, `id="call-api"`, `id="implement-nango"`).</violation>

<violation number="2" location="docs/api-integrations/ninety-io.mdx:69">
P3: Heading should use sentence case per project convention: 'Ninety.io integration guides' (only 'Ninety.io' as proper noun stays capitalized).</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>