Resources · n8n integration

One Simple API n8n integrationAutomate One Simple API with n8n.

One small utility is missing from your workflow, and the whole automation stalls. The One Simple API n8n integration covers that gap with 10 operations spread over 4 resources: currency, image and profile lookups, link and email checks, page captures. No trigger node, so another step starts the run.

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the One Simple API n8n integration actually give you?

One Simple API is described in n8n as a toolbox of no-code utilities, and the node reflects that literally. It groups 10 operations under 4 resources: Information, Social Profile, Utility and Website. Each one answers a small question that would otherwise need its own service, its own account and its own credential inside your workflow.

The node earns its place when a workflow needs one extra piece of data and you would rather not add a fifth vendor to get it. Currency conversion, image metadata, an expanded link, a verified email, a rendered page: all of it runs through a single API token stored once in n8n.

Cleaning a signup list before it reaches your CRM. A form fills a row, utility.validateEmail checks the address, and only the addresses that pass continue to the rest of the flow. Pair it with Google Sheets to keep a log of what was rejected, and with Gmail to send the welcome message only to real inboxes. The two public templates for this node do exactly that shape of work, one against Mautic (1462) and one against HubSpot (1461).

Watching a page you do not control. A Schedule Trigger fires, website.seo reads the SEO information of a competitor page, website.screenshot captures how it looks, and both land in a Slack message. Nobody opens a browser to notice that a title tag changed.

Turning content into files. website.pdf renders an order confirmation page as a PDF, utility.qrCode encodes the tracking link, and the binary output goes straight into an email attachment. The file never touches a local disk.

Reach for the HTTP Request node when One Simple API exposes something these 4 resources do not cover. It calls any endpoint of the service and reuses the same predefined credential, so you keep one token rather than two.

Two limits are worth knowing before you build. There is no One Simple API trigger node, so every workflow starts somewhere else: a Schedule Trigger on a fixed interval, an n8n Webhook called by another service, or the trigger of another app. And the node covers what its 10 operations describe and nothing more, so a screenshot of a page behind a login is outside its scope. If you are weighing the platform itself, the n8n review goes into that, and the n8n training covers building these flows hands-on.

Connect

How do you connect One Simple API to n8n?

  1. 01

    Create the account and the token

    Register on One Simple API first, then open the API Tokens page from your Profile menu and create a new API token. The docs are explicit on one point: select appropriate permissions for the token while you create it. That choice decides which operations the token is allowed to run, so a token scoped too tightly will fail on the operation you actually wanted.

  2. 02

    Store the credential in n8n

    In n8n, go to the Credentials menu and add a One Simple API credential. The single field it asks for is the API token you just generated. A credential is created once and reused by every workflow on the instance, so you paste the token here and never again. This works the same way on n8n Cloud and on a self-hosted instance.

  3. 03

    Pick the credential in the node

    Drop a One Simple API node into a workflow. Its credential dropdown lists what you saved, so you select the entry rather than typing anything. Then choose a resource among Information, Social Profile, Utility and Website, and the operation below it. The node is shipped with n8n, on Cloud and self-hosted alike, so there is nothing to install and no extra cost on the n8n side.

Actions

What can the One Simple API node do in a workflow?

The One Simple API node exposes 10 operations across 4 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceExchange RateExpand URLImage MetadataInstagramGenerate PDFGenerate QR CodeTake ScreenshotGet SEO DataSpotifyValidate Email
Information✓✓
Social Profile✓✓
Utility✓✓✓
Website✓✓✓

Information

2 operations
01

Convert a value between currencies

information.exchangeRate

What you see in n8n

Notes & use cases

Converts an amount from one currency into another and returns the converted value, so a workflow can normalize prices that arrive in several currencies.

Key parameters

  • Value: the amount to convert, usually pulled from the previous step with {{ $json.amount }} rather than typed by hand.
  • From Currency: the source currency, entered as a code like USD.
  • To Currency: the target currency, same format, for example EUR.
Use cases
an invoice arrives in dollars and your reporting sheet is kept in euros, so the conversion happens in the workflow instead of in a monthly manual pass.
02

Get image metadata from a URL

information.imageMetadata

What you see in n8n

Notes & use cases

Point this operation at an image that lives on the web and it retrieves the metadata of that file, without downloading the image into the workflow.

Key parameters

  • Link To Image: the address of the image to read, often an expression such as {{ $json.image_url }} coming from a product feed or a form upload.
Use cases
a supplier sends a catalog of image links and you want to check what those files really are before they are published on a product page.

Social Profile

2 operations
03

Get details about an Instagram profile

socialProfile.instagramProfile

What you see in n8n

Notes & use cases

Returns the public details of an Instagram profile from its handle, which lets a workflow enrich a record without anyone opening the app.

Key parameters

  • Profile Name: the profile name to get details of, so the handle itself and not a full profile URL.
Use cases
a partnership form collects an Instagram handle, and the workflow attaches the profile details to the request before it reaches the person who has to answer it.
04

Get details about a Spotify artist

socialProfile.spotifyArtistProfile

What you see in n8n

Notes & use cases

Looks up an artist on Spotify by name and brings back the details of that artist profile as regular workflow data.

Key parameters

  • Artist Name: the artist name to get details for, spelled as it appears on Spotify, since the lookup goes through the name and not an identifier.
Use cases
a label or a venue keeps a booking pipeline, and each new artist entry gets its Spotify details attached automatically when the row is created.

Utility

3 operations
05

Expand a shortened URL

utility.expandURL

What you see in n8n

Notes & use cases

Takes a shortened link and returns the address it actually points to, so the destination is known before anything in the workflow acts on it.

Key parameters

  • URL: the shortened link to unshorten, typically {{ $json.link }} extracted from an inbound message.
Use cases
an inbox automation receives messages full of short links, and the flow resolves each one before deciding whether the message is worth routing to a human. It also pairs well with Bitly when you shorten on one side and need to read back on the other.
06

Generate a QR code utility

utility.qrCode

What you see in n8n

Notes & use cases

Turns a piece of text into a QR code image, either as a binary file inside the workflow or as a link to the generated code.

Key parameters

  • QR Content: the text that should be turned into a QR code, a website URL for instance.
  • Download Image?: on, the image comes back as a file; off, the node returns a link to it.
  • Put Output In Field: the name of the output field that holds the binary file data, the field an email or upload step will point to.
  • Size and Format: optional, Small, Medium or Large, in PNG or SVG.
Use cases
a ticketing flow generates one code per booking and attaches it to the confirmation email.
07

Validate an email address

utility.validateEmail

What you see in n8n

Notes & use cases

Checks an email address and returns the result of that validation, which a following IF node can branch on before the address enters any list.

Key parameters

  • Email Address: the address to validate, almost always an expression like {{ $json.email }} taken from the form or CRM record that triggered the run.
Use cases
the two public templates built on this node do exactly this, checking new contacts in Mautic (1462) and in HubSpot (1461) and posting the outcome to Slack.

Website

3 operations
08

Generate PDF

website.pdf

What you see in n8n

Notes & use cases

Renders a webpage as a PDF document, so a page that already exists becomes a file you can attach, archive or send.

Key parameters

  • Webpage URL: the link to the webpage to convert.
  • Download PDF?: on, the PDF is returned as a file; off, you get a link to it.
  • Put Output In Field: the output field that receives the binary file data.
  • Page Size: optional, from A0 to A6, plus Ledger, Legal, Letter and Tabloid.
  • Force Refresh: the API normally reuses a previously taken capture of the URL for a faster response, this option retakes it at that exact moment.
Use cases
an order page is archived as a PDF the moment the order is confirmed.
09

Get SEO Data

website.seo

What you see in n8n

Notes & use cases

Reads the SEO information of a webpage and hands it back as structured data the rest of the workflow can compare, store or alert on.

Key parameters

  • Webpage URL: the webpage to get SEO information for, one page per item, so a list of pages means a list of items feeding the node.
  • Include Headers?: optional, turn it on when the response headers matter as much as the page itself.
Use cases
a scheduled run walks through a set of landing pages and writes the result into a sheet, which makes an accidental change visible the next morning.
10

Screenshot

website.screenshot

What you see in n8n

Notes & use cases

Creates a screenshot of a webpage, either full page or limited to the viewable area of the screen size you pick.

Key parameters

  • Webpage URL: the link to the webpage to capture.
  • Download Screenshot?: on for a file, off for a link to the image.
  • Put Output In Field: the output field that carries the binary file data.
  • Screen Size: optional, Phone, Phone Landscape, Retina, Tablet or Tablet Landscape.
  • Full Page: the capture covers the viewable area by default, this option takes the whole length of the page.
  • Force Refresh: forces a new capture instead of the cached one.
Use cases
a daily capture of a pricing page becomes a visual archive nobody has to maintain.
Need help

Need help automating One Simple API with n8n?

A person reads every message.

FAQ

One Simple API and n8n, the questions that come up

01Is the One Simple API n8n integration free to use?
On the n8n side, yes. The One Simple API node ships with n8n, so there is nothing to install and no extra cost on n8n, whether you run n8n Cloud or a self-hosted instance under the Community Edition and its Sustainable Use license. A workflow behaves the same way in both setups, which means you can build it on one and move it to the other. What One Simple API itself charges is a separate question and this page does not cover it, because the n8n documentation for the node says nothing about it. Check the service directly for that part.
02What credentials do you need for One Simple API in n8n?
One method, an API token. You create a One Simple API account, open the API Tokens page from your Profile menu, and generate a token there. The documentation asks you to select appropriate permissions for that token, which is the step most people skip. In n8n you then create a One Simple API credential with that token as its only field. Credentials live at instance level, so the same entry is offered in the dropdown of every One Simple API node you add later, in any workflow, and you never paste the token into a node itself.
03What are the limits of the One Simple API node in n8n?
The node exposes 10 operations across 4 resources, and that set is the boundary. Information covers currency conversion and image metadata, Social Profile covers Instagram and Spotify lookups, Utility covers link expansion, QR codes and email validation, Website covers PDF, SEO data and screenshots. Anything One Simple API offers beyond those goes through the HTTP Request node, which calls any endpoint of the service and reuses the same predefined credential, so you still manage a single token. Note also that operations returning a file need an output field name, otherwise the binary data has nowhere to go.
04Does One Simple API have a trigger node in n8n?
No. There is no One Simple API trigger, so nothing on this side can start a workflow on its own. You start the run somewhere else and then call the node. The usual choices are a Schedule Trigger firing on a fixed interval, which fits recurring work like a nightly screenshot or a weekly SEO read, or an n8n Webhook, meaning a URL that n8n exposes and another service calls when something happens. The trigger of another app works too, which is how the public templates run: a new contact appears in a CRM, and the email validation follows.
05n8n or Make for One Simple API?
It depends on four things, and price is only one of them. Make is a hosted automation platform with no self-hosting option, billed per operation, so a workflow that runs often has a cost that grows with volume. n8n runs on Cloud or on your own server, which matters when the data passing through these operations should not leave your infrastructure. Both are visual, so the real question is where your team is comfortable. If the node lacks an operation you need, n8n lets you fall back on HTTP Request with the same credential, which is the kind of escape hatch that decides the choice.