Resources · n8n integration

Peekalink n8n integrationAutomate Peekalink with n8n.

The Peekalink n8n integration turns a raw link into something a workflow can actually read. The node ships 1 resource and 2 operations: one checks whether a preview exists, the other returns it. There is no Peekalink trigger, so the workflow starts from a Schedule Trigger or a Webhook.

Try the Peekalink integration on n8nSee the 2 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Peekalink n8n integration actually do?

The Peekalink node reads a URL and hands back what sits behind it, so a workflow can treat a link as data instead of text. n8n ships the node with the app itself, on n8n Cloud and on a self-hosted instance, and you authenticate it once with a Peekalink API key. Two operations cover the whole job: a check that says whether a preview is available, and the call that returns that preview.

Take a link cleanup pass first. A column of URLs collected by a sales team goes stale fast. A Schedule Trigger, the n8n node that fires at a fixed interval, walks the rows in Google Sheets, default.isAvailable answers for each one, and the links that come back negative are flagged for a human. Nothing gets fetched twice, because the check runs before the preview call.

Richer notifications are the second pattern. A teammate drops a URL into a channel, the workflow calls default.preview, and the answer goes back to Slack with the preview attached rather than a bare link. The same shape works for a link arriving by mail through Gmail.

Third pattern, an internal archive. Links saved by an editorial team land in Postgres, and the preview returned by the node is stored next to each record, so the archive keeps a readable trace even after the source page changes.

Where the node stops is easy to state: it exposes 2 operations and nothing more. Anything else the Peekalink API offers goes through the HTTP Request node, which calls any endpoint of that API and reuses the same credential through predefined authentication. There is also no Peekalink trigger in n8n, so the start of the workflow always comes from somewhere else.

n8n publishes a ready-made workflow named Check for preview for a link, which is a fair place to see the node in context before you branch on its answer. On the platform question, the split with Make sits in hosting, control over the data and per-operation billing; the n8n review walks through those criteria.

Connect

How do you connect Peekalink to n8n?

  1. 01

    Create the Peekalink account

    Everything starts with an account on Peekalink itself. Once it exists, open the Peekalink dashboard and look for the section named Your API Key. The value shown there is the only secret the node needs, so copy it into a password manager rather than into a workflow note where the next person to open the canvas will read it.

  2. 02

    Store the API key credential

    In n8n, open the Credentials menu and create a Peekalink credential. A credential is a set of secrets saved once and reused by every workflow on the instance, which is why you never paste the key into a node. The form asks for one field, API Key, and you drop the dashboard value in. The next Peekalink node offers it in a dropdown.

  3. 03

    Run the node on its own

    Add a Peekalink node, select the credential, fill URL with a link you control, and execute that node alone to see the response before you wire anything after it. Peekalink has no trigger node, so pair it with a Schedule Trigger or with an n8n Webhook, a URL that another service calls when it has something to hand over.

Actions

What can the Peekalink node do?

The Peekalink node exposes 2 operations. For each one: the node as you configure it in n8n, the required fields, and our field notes.

01

Check whether the preview for a given link is available

isAvailable

What you see in n8n

Notes & use cases

This operation asks Peekalink whether a preview can be produced for a link, without returning the preview itself. It works as a gate: the answer tells you if the next node has anything to work with.

Key parameters

  • URL: the link to test, typed in or read from the incoming item with an expression such as {{ $json.field }}. The field is required, and an empty value stops the node.
Use cases
a monthly sweep over a list of partner URLs, where every link that fails the check goes down a review branch instead of the enrichment branch.
02

Return the preview for a link

preview

What you see in n8n

Notes & use cases

Here the node calls Peekalink and brings back the preview of the page behind the link, ready for the rest of the workflow to store or display.

Key parameters

  • URL: the address to preview. Coming from an earlier node it is mapped with {{ $json.field }}, the expression that reads a field of the incoming item. Required, so drop empty rows upstream rather than letting the node fail.
Use cases
an internal digest where each saved link travels with its preview, so readers judge a page before clicking it.
Need help

Need help automating Peekalink with n8n?

A person reads every message.

FAQ

Peekalink and n8n, common questions

01Is the Peekalink n8n integration free?
Yes, on the n8n side. The Peekalink node ships with n8n, so there is nothing to install and nothing extra to pay for the connector, whether you run n8n Cloud, the hosted offer from n8n, or your own instance under the Community Edition and its Sustainable Use license. A workflow behaves the same way in both setups, and the credential you create works across them. What Peekalink itself charges for API usage is a separate matter that belongs to the service, not to the node, so check the plan attached to the account that issued your key before pointing a high volume workflow at it.
02What credentials do you need for Peekalink in n8n?
An API key, and nothing else. Peekalink supports a single authentication method here, so there is no OAuth flow to approve and no list of scopes to review. Create the account first, open the Peekalink dashboard, and copy the value from the Your API Key section. In n8n, the Credentials menu holds a Peekalink entry with one field, API Key, and any Peekalink node on the instance then selects it from a dropdown. The same key covers both operations the node exposes, so one credential is enough for a whole family of workflows.
03What are the limits of the Peekalink node in n8n?
It does two things, and that is the limit. The node covers 1 resource and 2 operations, the availability check and the preview, and each call takes a single URL. Neither operation returns a list, so there is no Return All or Limit setting to reason about here, unlike the list-style operations you meet on other n8n nodes. For anything else the Peekalink API exposes, the HTTP Request node calls any endpoint of that API and reuses the same credential through predefined authentication, which keeps the key in one place instead of two.
04Does Peekalink have a trigger node in n8n?
No. There is no Peekalink trigger, so a workflow using it has to start elsewhere. Three routes cover most needs: a Schedule Trigger that fires at a fixed interval and walks a list of links, an n8n Webhook, meaning a URL another service calls when it has a link to pass on, or the trigger of another tool already in the workflow. The practical consequence is that Peekalink answers when your schedule or your webhook says so, not the moment a link appears somewhere, so pick an interval that matches how fast new links actually arrive.
05n8n or Make for Peekalink?
It depends on hosting and on how you want to pay. Make is hosted only, with no self-hosting option, and bills per operation, so a workflow that checks and previews a lot of links has a cost that follows volume closely. n8n runs on its own Cloud offer or on your server, which matters when the URLs being inspected are internal or sensitive and should stay on your infrastructure. Both give you a visual canvas to build in. When the Peekalink calls sit inside a longer workflow that already touches a database, self-hosting usually wins on cost; when you want nothing to maintain, hosted is simpler.
Same platform

Other docs you might need on this stack.

Browse all integrations