FlowRunner
Features Pricing
Theme
Start Free

Connect over an API key to turn any URL into structured link-preview metadata, including titles, descriptions, images, favicons, and platform-specific details for recognized services.

Verified 1 action API key available
Peekalink website Platform Documentation Capability data verified 2026-10-13
A user-submitted URL arrives for enrichment
Agent calls Preview Link to fetch title, description, image, and details
Agent reads the ok field and drops links that cannot be previewed
Agent reads the core metadata and any service-specific fields
Agent confirms the title and image are present and sensible
Agent posts the enriched preview for review
A person approves the preview before it appears on public material

What This Integration Enables

The Peekalink connector gives agents one focused read action. Preview Link generates a rich preview for a URL, returning the title, description, domain, type, a main image, and a favicon, plus a type-specific details object for recognized services with data such as video, author, or product information. Peekalink exposes a single endpoint, so every preview is billed, and the same call that enriches a link also screens it: the result's ok field reports whether the link is valid. The action reads; nothing writes. The connector supplies the enrichment; the surrounding flow decides what to store and what to publish.

Without FlowRunner

Links stored raw Only the bare URL is saved, with no title or image
Dead links slip in Unpreviewable URLs get stored and surface as broken cards later
Previews built by hand Someone copies a title and grabs an image for each shared link

With FlowRunner

Links stored enriched The agent attaches title, description, and image on the way in
Dead links filtered The ok field on each preview screens out URLs that will not resolve
Previews built in the flow Preview Link assembles the card automatically for review

Flows you can build with Peekalink

  • URL Enrichment on Intake

    When a user submits a URL, the agent calls Preview Link to fetch the title, description, and preview image, then stores the enriched record rather than the bare link. Later views show a proper card instead of a naked address, and the enrichment happens without anyone assembling it by hand.

    • Peekalink
    • Google Sheets

    Batch Pre-Validation

    Given a list of URLs, the agent removes duplicates first, because there is no cheaper pre-check and every Preview Link call is billed. It then previews each remaining URL, keeps the results whose ok field is true, and logs their metadata to Google Sheets. Unpreviewable links never reach the downstream store.

  • Preview Card for Sharing

    Before a link is shared to a channel or a content feed, the agent calls Preview Link to build a rich card with title, description, and image. It posts the card for review so the shared link carries context, and a person confirms it before it goes out.

Human-in-Loop Highlight

Fetching a preview is a safe read, and the connector only reads; it never publishes anything on its own. The judgment lies downstream, because a preview that lands on public material, a shared card, a content feed, an outbound message, becomes the face of that link to everyone who sees it. This is human-in-the-loop at the boundary between enriching a link and publishing it: when a fetched preview would appear on public material, the agent pauses and routes the assembled card to a person through their preferred channel. The message is specific: "This link previews as a pricing-page title with last quarter's hero image. Publish the card as fetched, or fix it first?" The agent gathers the metadata; a person owns the preview the outside world reads.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

1 actions

Link Preview

1
  • Preview Link Generate a rich preview for a single URL, returning title, description, domain, type, a main image, and a favicon. For recognized services a type-specific details object adds platform data such as video, author, or product information.

Frequently asked questions

What can FlowRunner do with Peekalink?

FlowRunner agents can run Preview Link in Peekalink.

Does connecting Peekalink to FlowRunner require OAuth?

No. Peekalink connects to FlowRunner with an API key, no OAuth flow required.

Can Peekalink trigger a FlowRunner workflow automatically?

Peekalink doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Peekalink

Free plan, no card required. Connect in minutes.