feat(integrations): add support for hex#5929
Merged
Merged
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ce923c0078
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
ce923c0 to
41eb079
Compare
rbwest
approved these changes
Apr 24, 2026
Contributor
There was a problem hiding this comment.
1 issue found across 13 files
Confidence score: 4/5
- This PR looks safe to merge with minimal risk; the reported issue is documentation completeness rather than a runtime regression.
- In
docs/api-integrations/hex.mdx, the Hex setup currently omits the required subdomain, which can lead users to an incomplete configuration flow (subdomain + API token are both needed). - Given the 5/10 severity and high confidence, the impact is mainly user guidance quality, not core functionality breakage.
- Pay close attention to
docs/api-integrations/hex.mdx- ensure the Hex subdomain requirement is explicitly included in the setup steps.
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/hex.mdx">
<violation number="1" location="docs/api-integrations/hex.mdx:15">
P2: Include the Hex subdomain here as well; Hex connections need both subdomain and API token, so this step is currently incomplete.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review, or fix all with cubic.
| <Step title="Create the integration"> | ||
| In Nango ([free signup](https://app.nango.dev)), go to [Integrations](https://app.nango.dev/dev/integrations) -> _Configure New Integration_ -> _Hex_. | ||
| </Step> | ||
| <Step title="Add your API token"> |
Contributor
There was a problem hiding this comment.
P2: Include the Hex subdomain here as well; Hex connections need both subdomain and API token, so this step is currently incomplete.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At docs/api-integrations/hex.mdx, line 15:
<comment>Include the Hex subdomain here as well; Hex connections need both subdomain and API token, so this step is currently incomplete.</comment>
<file context>
@@ -0,0 +1,82 @@
+ <Step title="Create the integration">
+ In Nango ([free signup](https://app.nango.dev)), go to [Integrations](https://app.nango.dev/dev/integrations) -> _Configure New Integration_ -> _Hex_.
+ </Step>
+ <Step title="Add your API token">
+ Go to [Connections](https://app.nango.dev/dev/connections) -> _Add Test Connection_ and enter your Hex API token. Later, you'll let your users do the same directly from your app.
+ </Step>
</file context>
bahdcoder
pushed a commit
to usehivy/integrations
that referenced
this pull request
Apr 28, 2026
## Describe the problem and your solution - add support for hex <!-- Issue ticket number and link (if applicable) --> <!-- Testing instructions (skip if just adding/editing providers) -->
Open
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Describe the problem and your solution