- Home
- Resources
- Integrations
- One Simple API
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
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.
How do you connect One Simple API to n8n?
- 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.
- 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.
- 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.
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.
| Resource | Exchange Rate | Expand URL | Image Metadata | Generate PDF | Generate QR Code | Take Screenshot | Get SEO Data | Spotify | Validate Email | |
|---|---|---|---|---|---|---|---|---|---|---|
| Information | ✓ | ✓ | ||||||||
| Social Profile | ✓ | ✓ | ||||||||
| Utility | ✓ | ✓ | ✓ | |||||||
| Website | ✓ | ✓ | ✓ |
Operations index
Information
2 operationsConvert a value between currencies
information.exchangeRateWhat 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.
Get image metadata from a URL
information.imageMetadataWhat 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.
Social Profile
2 operationsGet details about an Instagram profile
socialProfile.instagramProfileWhat 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.
Get details about a Spotify artist
socialProfile.spotifyArtistProfileWhat 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.
Utility
3 operationsExpand a shortened URL
utility.expandURLWhat 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.
Generate a QR code utility
utility.qrCodeWhat 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
PNGorSVG.
Validate an email address
utility.validateEmailWhat 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.
1462) and in HubSpot (1461) and posting the outcome to Slack.Website
3 operationsGenerate PDF
website.pdfWhat 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
A0toA6, 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.
Get SEO Data
website.seoWhat 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.
Screenshot
website.screenshotWhat 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.
Need help automating One Simple API with n8n?
A person reads every message.


