feat(linkup): add fetch operation to the Linkup block by shauryajain21 · Pull Request #8547 · simstudioai/sim

shauryajain21 · 2026-10-01T21:50:23Z

Summary

Adds a Linkup Fetch tool (linkup_fetch, POST https://api.linkup.so/v1/fetch) that returns a webpage as clean markdown, and exposes it as a second operation on the existing Linkup block. The block now has an operation dropdown (Search / Fetch) with operation-conditioned sub-blocks, following the same structure as the Exa block.

tools/linkup/fetch.ts: params url (required), renderJs, includeRawHtml, extractImages; outputs markdown, rawHtml, images[{alt, url}], favicon. Uses the same hosted-key / BYOK config as linkup_search (LINKUP_API_KEY, provider linkup), priced per Linkup's pricing: $0.001/call, $0.005 with renderJs.
Linkup block: operation dropdown defaulting to linkup_search, fetch sub-blocks, tools.access + tools.config.tool, inputs/outputs, canvas sentences, and a fetch-page-markdown skill.
Backwards compatible: blocks saved before this change have no stored operation. Search fields are gated on operation !== 'linkup_fetch' and the tool selector falls back to linkup_search, so existing workflows keep rendering, serializing, and running as search. The default canvas sentence still covers those blocks.
Registered in tools/registry.ts; regenerated tool metadata, integration docs (integrations/linkup.mdx) and integrations.json; added Fetch rows to the Linkup tab in platform/costs.mdx.

Usage: add a Linkup block, choose Fetch, set URL to https://docs.linkup.so, then reference <linkup.markdown> downstream. Agents can also call linkup_fetch as a tool.

Type of Change

Testing

tools/linkup/linkup.test.ts (new, mocked): request body (url trimming, option passthrough incl. explicit false), transformResponse mapping and defaults, hosted pricing, block routing (including blocks with no stored operation), and condition visibility for legacy vs. fetch.
bunx vitest run tools/linkup blocks/blocks.test.ts blocks/password-masking.test.ts blocks/registry-lookup.test.ts tools/metadata.test.ts tools/index.test.ts tools/model-input-selectors.test.ts tools/param-shape.test.ts lib/workflows/blocks lib/workflows/migrations: 22 files, 573 tests passing.
bun run type-check (apps/sim), biome check on changed files.
check:canvas-sentences, tool-metadata:check, docs:check, deployment-config:check, integration-catalog:check, check:byok-providers, check:tool-param-reachability, check:tool-request-boundary, check:tool-registry-boundary, check:test-patterns, check-block-registry.ts: all pass.
Live check against the Linkup API with a real key: linkup_search (sourcedAnswer) and linkup_fetch (with includeRawHtml / extractImages) both return the expected outputs through the tool configs.

Worth a look: the "not fetch" condition used for backwards compatibility with blocks that predate the operation dropdown.

Checklist

Code follows project style guidelines
Self-reviewed my changes
Tests added/updated and passing
No new warnings introduced
I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

Screenshots/Videos

vercel · 2026-10-01T21:50:29Z

@shauryajain21 is attempting to deploy a commit to the Sim Team on Vercel.

A member of the Team first needs to authorize it.

greptile-apps · 2026-10-02T00:39:36Z

Confidence Score: 4/5

[Medium risk] Adds a webpage fetch operation to the Linkup integration tool.

The PR should not merge until Fetch handles string-valued Render JavaScript inputs consistently and the repository testing and typing requirements are met.

Findings

Render pricing misses string switches ▶
Optional outputs can be null ▶
Legacy cards lose query placeholder ▶
New code uses any ▶
Tests stop before execution ▶

Summary

The PR adds Linkup Fetch as a second block operation and agent tool, with hosted-key pricing, output metadata, tests, and documentation.

Legacy blocks continue to route to Search, although an empty legacy card loses its query placeholder.
String-valued Render JavaScript inputs need consistent request and billing conversion.
Fetch output declarations and new test/type conventions need attention.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  A[Linkup block] --> B{operation}
  B -->|missing or Search| C[linkup_search]
  B -->|Fetch| D[linkup_fetch]
  D --> E[POST api.linkup.so/v1/fetch]
  E --> F[markdown and optional page assets]

_{Reviews (1) · Last reviewed commit: "feat(linkup): add fetch operation to the..."}

greptile-apps · 2026-10-02T00:39:39Z

+        // Linkup pricing (https://docs.linkup.so/pages/documentation/platform/pricing):
+        //   Standard:            $0.001/call
+        //   Standard + renderJs: $0.005/call
+        const renderJs = params.renderJs === true


Render pricing misses string switches

A workflow variable or legacy switch can pass Render JavaScript as the string 'true'. The request forwards that string, but this check charges the rendered rate only for boolean true. If Linkup accepts the string as enabling rendering, the call is billed at $0.001 instead of $0.005; if it rejects the string, the requested fetch fails. Convert the value consistently before building the request and calculating its cost.

greptile-apps · 2026-10-02T00:39:39Z

+    rawHtml: {
+      type: 'string',
+      description: 'The raw HTML of the webpage, when includeRawHtml is enabled',
+      optional: true,
+    },


Optional outputs can be null

When Linkup omits rawHtml or favicon, the transform returns null for those fields, but both are declared only as optional strings. Consumers of the output schema can therefore expect a string or a missing field and receive null instead. Declare both outputs nullable, or omit them when absent.

greptile-apps · 2026-10-02T00:39:39Z

+        'Search the web',
+        { text: 'for', field: 'q' },


Legacy cards lose query placeholder

Saved blocks without an operation use this default sentence. When their query is empty, the new non-core clause disappears, leaving only “Search the web” where the card previously showed a Search Query placeholder. Keeping the query clause core would preserve that cue on existing cards.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

greptile-apps · 2026-10-02T00:39:39Z

+      Authorization: `Bearer ${params.apiKey}`,
+    }),
+    body: (params) => {
+      const body: Record<string, any> = {


New code uses any

The new request body uses Record<string, any>, and the test helper repeats that cast. The repository’s TypeScript directive prohibits any and calls for precise types or unknown with guards. Please type these values to match their actual shapes before merging.

Context Used: CLAUDE.md (source)

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

greptile-apps · 2026-10-02T00:39:39Z

+describe('linkup block', () => {
+  const selectTool = (params: Record<string, unknown>) =>
+    LinkupBlock.tools.config?.tool?.(params as never)
+
+  it('routes blocks saved before the operation dropdown to search', () => {
+    expect(selectTool({ q: 'latest news' })).toBe('linkup_search')
+  })
+
+  it('routes each operation to its tool', () => {
+    expect(selectTool({ operation: 'linkup_search' })).toBe('linkup_search')
+    expect(selectTool({ operation: 'linkup_fetch' })).toBe('linkup_fetch')
+  })


Tests stop before execution

These tests call the block’s tool selector directly, so they cannot catch failures between a saved Linkup block and an executed Fetch request, including input conversion or hosted-key handling. The repository’s testing directive discourages tests that restate declarations and favors checks at the real boundary. Add execution-boundary coverage before merging.

Context Used: CLAUDE.md (source)

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

Render JavaScript and the other fetch switches can arrive as strings from block inputs. Normalize them once so the request sends booleans and hosted pricing bills the same rendering decision. Declare rawHtml/favicon as nullable, type the request and response bodies, and cover the string cases plus an executor-level fetch run in tests.

feat(linkup): add fetch operation to the Linkup block

2c39728

waleedlatif1 marked this pull request as ready for review October 2, 2026 00:34

greptile-apps Bot reviewed Oct 2, 2026

View reviewed changes

shauryajain21 force-pushed the add-linkup-integration branch from 5a2f643 to 2c39728 Compare October 2, 2026 13:45

Navigation Menu

feat(linkup): add fetch operation to the Linkup block - #8547

feat(linkup): add fetch operation to the Linkup block#8547
shauryajain21 wants to merge 2 commits into
simstudioai:stagingfrom
shauryajain21:add-linkup-integration

shauryajain21 commented Oct 1, 2026

Uh oh!

vercel Bot commented Oct 1, 2026

Uh oh!

greptile-apps Bot commented Oct 2, 2026 •

edited

Loading

Uh oh!

greptile-apps Bot Oct 2, 2026

Uh oh!

greptile-apps Bot Oct 2, 2026

Uh oh!

greptile-apps Bot Oct 2, 2026

Uh oh!

greptile-apps Bot Oct 2, 2026

Uh oh!

greptile-apps Bot Oct 2, 2026

Uh oh!

This branch has not been deployed

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

shauryajain21 commented Oct 1, 2026

Summary

Type of Change

Testing

Checklist

Screenshots/Videos

Uh oh!

vercel Bot commented Oct 1, 2026

Uh oh!

greptile-apps Bot commented Oct 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Confidence Score: 4/5

Findings

Summary

Uh oh!

greptile-apps Bot Oct 2, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps Bot Oct 2, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps Bot Oct 2, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps Bot Oct 2, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps Bot Oct 2, 2026

Choose a reason for hiding this comment

Uh oh!

This branch has not been deployed

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

greptile-apps Bot commented Oct 2, 2026 •

edited

Loading