feat(linkup): add Fetch action and search filter options

[shauryajain21]

Summary

Extends the existing Linkup app with a new Linkup Fetch action and exposes more of the search options supported by the Linkup API.

New action: Linkup Fetch (linkup-fetch, 0.0.1)

• Calls POST /v1/fetch and returns the page content as markdown.
• Props: url (required), renderJs, includeRawHtml, extractImages.
• Docs

Updated action: Linkup Search (linkup-search, 0.0.2 → 0.1.0)

• New optional props: includeDomains, excludeDomains, fromDate, toDate (YYYY-MM-DD), maxResults.
• Fixed the docs link, which now points to the current search reference.
• Set readOnlyHint: true, matching other search actions.

App and package

• New props are defined in linkup.app.mjs propDefinitions, and a fetch() method is added alongside search().
• linkup-sdk bumped from ^1.0.3 to ^2.7.0. This is the first SDK line that forwards maxResults and the fetch options, and it still supports Node >= 20.19. pnpm-lock.yaml updated accordingly.
• @pipedream/linkup 0.1.0 → 0.2.0.

Example (Fetch)

{
  "url": "https://docs.linkup.so",
  "renderJs": false
}

The action returns { "markdown": "..." }, plus rawHtml / images when requested.

Testing

• pnpm exec eslint on the changed files: passed.
• pnpm install --frozen-lockfile: lockfile is in sync.
• Ran the actions against the live API with a real key:
  • Search with each output type (searchResults, sourcedAnswer, structured). Include/exclude domain, date range, and max results filters were applied.
  • Fetch with the default options, then with renderJs, includeRawHtml, and extractImages all enabled.
  • An invalid key surfaces the SDK's authentication error.

Checklist

Please check the following items before your PR can be reviewed:

Versioning

• All components updated in this PR had their version updated (0.0.1 for new ones)
• The app updated in this PR had its package.json's version updated

New app

If this is a new app, please submit an app integration request - the PR will only be reviewed after the app is integrated.

• The app updated in this PR is already integrated

CodeRabbit review

After the PR is opened, and if new changes are pushed, CodeRabbit will automatically review it. Do not 'mark as resolved' CodeRabbit's comments, but reply to them instead, whether you agree (and update the PR accordingly) or disagree.

• I have addressed or acknowledged all of CodeRabbit's review comments

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
pipedream-docs-redirect-do-not-edit	Ignored		Oct 2, 2026 1:45pm UTC

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.

---

_{Comment @coderabbitai help to get the list of available commands.}

[pipedream-component-development]

Thank you so much for submitting this! We've added it to our backlog to review, and our team has been notified.

[pipedream-component-development]

Thanks for submitting this PR! When we review PRs, we follow the Pipedream component guidelines. If you're not familiar, here's a quick checklist:

• Create components to address specific use cases whenever possible
• Component keys should follow the format app_name_slug-slugified-component-name
• Components should follow the standard directory structure
• Prefer Node.js client libraries to REST APIs
• When making API requests, handle pagination to ensure all data / events are processed
• Use secret props to capture sensitive data
• Props and methods should be defined in app files whenever possible
• Document methods with JS Docs
• Use optional props whenever possible, and set a default value where you can
• Use standalone actions over async options and ensure the description of the prop indicates usage of the standalone action to fetch the data for the prop
• Please address all review comments as they are added
• Enable edits from maintainers to allow Pipedream maintainers to make changes to this PR