Resources · n8n integration

Brandfetch n8n integrationAutomate Brandfetch with n8n.

Every brand asset a workflow needs starts from one domain name. The Brandfetch n8n integration puts 5 operations in the node: colors, company data, fonts, industry and logo. No trigger node ships with it, so a schedule or a form starts the run. Made for sales and ops teams who enrich lists.

Try the Brandfetch integration on n8nSee the 5 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Brandfetch n8n integration actually do?

Brandfetch keeps what a company looks like on the web: its logo files, its palette, its typefaces, the sector it sits in. The n8n node reads that record on demand. Hand it a domain name, get the brand data back as regular items, and the rest of the workflow treats those values like any other field it received.

Sales lists are the first job people wire up. A form drops one company domain per row into a Google Sheets tab, the workflow walks the new rows and runs default.company on each one, and the sheet fills itself with the name and description. Add default.industry in the same pass and the list arrives sorted by sector, before a rep opens it.

The second job is visual. default.logo pulls the logo and icon files for a domain, so a proposal, a one-pager or a Gmail draft can carry the prospect's own mark instead of a grey square. Switch Download on and the image travels with the item as binary data, ready to attach without a second download step.

Design handoffs come third. Before a landing page or an ad set gets built, default.color and default.font return the palette and the typefaces for that same domain, and a Slack message drops both into the project channel. The brief lands with the brand already inside it.

Those 5 operations are what the node offers. Anything else the Brandfetch API exposes is reachable with the HTTP Request node, which reuses the same credential through its predefined authentication, so no second key is needed. Domain is required everywhere: an empty value stops the step before the call goes out, which is why that field usually holds an expression such as {{ $json.domain }} rather than a value typed by hand.

If the real question is whether to build any of this in n8n, the n8n review looks at the platform itself, and the n8n training is there when a team wants to ship workflows without queuing behind anyone.

Connect

How do you connect Brandfetch to n8n?

  1. 01

    Open a Brandfetch developer account

    Start on the Brandfetch developer site and create a developer account, which is the prerequisite for any API access. From the dashboard, generate an API key. That key is the single piece of information n8n asks for, so keep the page open while the credential gets created on the other side.

  2. 02

    Save the API key as a credential

    In n8n, go to the Credentials menu and add a Brandfetch credential. The supported authentication method is API key, so there is one field to fill: API Key, pasted from the developer dashboard. A credential is created once and reused by every workflow, which is why this step never comes back later.

  3. 03

    Run one operation against a real domain

    Drop the Brandfetch node into a workflow, pick the credential in the dropdown, choose an operation and fill Domain with a company you know. Execute that single step and read the output panel. If the data comes back, the credential works and the workflow can be built around it.

Actions

What can the Brandfetch node do?

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

01

Return a company's colors

color

What you see in n8n

Notes & use cases

Sends one domain to Brandfetch and gets the accent and brand color palette back, so a workflow can style something with the brand's real colors instead of a guess.

Key parameters

  • Domain: the company's domain name, typed in full or passed from an earlier node with {{ $json.domain }}. It is required, so an empty value stops the step.
Use cases
a client onboarding workflow collects the palette on day one and writes it into the project record, so every asset produced later starts from the same colors.
02

Return a company's data

company

What you see in n8n

Notes & use cases

One call brings back all available Brandfetch attributes for a domain: name, description, logos, colors, company data and more, in a single item. Worth using when the workflow needs the whole record rather than one slice of it.

Key parameters

  • Domain: where the lookup starts. Brandfetch keys its record on the web domain, so a value in the shape of n8n.io is what the field expects.
Use cases
an inbound lead form sends a work email, the workflow splits out the domain, and this operation fills the company fields of the record before a human reads the lead.
03

Return a company's fonts

font

What you see in n8n

Notes & use cases

Returns the typefaces Brandfetch associates with a domain. The output slots into anything that has to match a brand's type: a slide master, an email template, an ad variant.

Key parameters

  • Domain: the brand whose type you want. It is the same value the other operations take, so one list of domains can feed all of them in the same run.
Use cases
an agency preparing a pitch runs the prospect's domain through this step, and the deck picks up the right fonts before anyone opens the design tool.
04

Return a company's industry

industry

What you see in n8n

Notes & use cases

Answers one question about a domain: what sector the company belongs to. The answer comes back as data, so a filter or a switch can act on it immediately after.

Key parameters

  • Domain: the domain to classify. It usually arrives from a spreadsheet column or a form field, so an expression fits better here than a fixed value.
Use cases
a lead router sends each new domain to the rep who covers that sector, and the value stays in the sheet for later segmentation.
Need help

Need help automating Brandfetch with n8n?

A person reads every message.

FAQ

Brandfetch and n8n, the questions that come up next

01Is the Brandfetch n8n integration free?
On the n8n side, yes. The Brandfetch node ships with n8n, so there is nothing to install and no extra n8n cost, whether the instance runs on n8n Cloud or self-hosted under the Community Edition and its Sustainable Use licence. What Brandfetch charges for API access is set by Brandfetch and is not covered here. The only cost worth planning for inside n8n is the few minutes it takes to create the credential, and that happens once: every later workflow picks the same credential from the node's dropdown instead of asking for a new key.
02What credentials does the Brandfetch node need?
An API key, and nothing else. Create a Brandfetch developer account first, then generate the key from the developer dashboard and paste it into a Brandfetch credential in n8n. API key is the supported authentication method for this node, so there is no consent screen to walk through and no list of scopes to tick. The credential lives in the Credentials menu, separate from any workflow, which means the key never has to be copied into a node or shared with the person building the next automation on the same instance.
03What are the limits of the Brandfetch node in n8n?
The node exposes 5 operations: colors, company data, fonts, industry and logo. Anything else the Brandfetch API offers goes through the HTTP Request node, which can reuse the same credential via predefined authentication, so a second key is never needed for those calls. Every operation is keyed on Domain, and that field is required: leave it empty and n8n stops the node instead of calling the API. On the logo operation, Download, Image Type and Image Format are required too, so a run that leaves them blank will not go through.
04Can a Brandfetch workflow run on its own without a trigger node?
Yes. Brandfetch has no trigger node in n8n, so the workflow starts somewhere else: a Schedule Trigger firing at a fixed interval, an n8n Webhook called by another service, or the trigger of another app already in the workflow. A common setup is a Schedule Trigger that reads the new rows of a sheet every morning and enriches only what arrived since the last run. Another is a webhook fired by a form, passing the submitted domain straight into the node. The lookup happens when new data shows up, on your terms.
05n8n or Make for Brandfetch?
It depends on where the workflow should run and how the bill should behave. Make is hosted by Make, has no self-hosting option, and charges per operation, so the cost tracks volume directly. n8n runs on n8n Cloud or on a server you own, which keeps the brand data and the API key on infrastructure you chose. For a handful of enrichments a day, both do the job and the visual logic is a matter of taste. For thousands of rows a month, or when the data has to stay in house, self-hosting settles the question. Neither tool is the wrong answer here.
Same platform

Other docs you might need on this stack.

Browse all integrations