docs: consolidated legacy-integration docs (migration wizard + Tool Library filter)#660
Draft
jordanc-relevanceai wants to merge 4 commits into
Draft
docs: consolidated legacy-integration docs (migration wizard + Tool Library filter)#660jordanc-relevanceai wants to merge 4 commits into
jordanc-relevanceai wants to merge 4 commits into
Conversation
…tions Add a new page explaining how to migrate Pipedream-based tool integrations to native integrations using the migration wizard. Update the integrations introduction and add-integrations pages to reference the new guide, and add the page to the navigation in docs.json. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Documents the Tool Library interface including the new "Contains legacy tool-steps" filter (PR #15255), which helps users identify tools built on Pipedream-based steps that have native replacements available. Adds cross-references from integrations/introduction and tool-steps getting-started pages, and registers the new page in docs.json. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…legacy-integrations
This was referenced Jun 3, 2026
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
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
1 participant
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.
This PR consolidates 2 drafter PRs that overlap on the legacy/native integrations story. Opened as draft for review before the source PRs are closed.
Source PRs (being closed in favor of this one)
Why consolidated
Both edit
integrations/introduction.mdx(each adds a callout to the same spot about legacy Pipedream tools) and both add a nav entry todocs.json. Shipping separately conflicts on both files and risks two near-duplicate callouts. Consolidating lets the intro point users through one flow: find legacy tools, then migrate them.Changes by source PR
#653 — TSP-1263
integrations/migrate-legacy-integrations.mdxdocumenting the migration wizard (legacy Pipedream → native integrations).integrations/add-integrations.mdx(migration prompt note) and adds the page todocs.json(Integrations → Overview).#654 — TSP-1266
build/tools/tool-library.mdxdocumenting the Tool Library (search, cloneable/embeddable filters, and the Contains legacy tool-steps filter).build/tools/tool-steps/getting-started.mdxand adds the page todocs.json(Tools).Reconciliation note
<Note>to the same place inintegrations/introduction.mdx. Merged into one single-paragraph callout linking both: find legacy tools via the Tool Library's "Contains legacy tool-steps" filter, then upgrade them with the migration wizard.docs.jsonauto-merged — both nav entries verified in the correct groups (tool-libraryunder Tools,migrate-legacy-integrationsunder Integrations → Overview).