Resources · Make integration

Brand.dev Make integrationAutomate Brand.dev with Make.

Need brand data on a company without looking it up by hand? The Brand.dev Make integration gives you 13 action modules that look up a brand by domain, email, name, ticker or ISIN. This guide shows how to connect your account and build a first scenario.

Try the Brand.dev integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Brand.dev Make integration do for you?

The Brand.dev Make integration lets a Make scenario ask Brand.dev who is behind a website, an email address or a company name, then pass the answer to your other tools. A scenario is the automation you build in Make, a chain of modules where each module is one brick, here a Brand.dev action.

Enriched leads. A form sends you a work email. Retrieve a Brand by Email Address finds the company behind it, and the next module writes that brand into your CRM, so sales reps open a record that already has context.

A design brief that builds itself. A designer drops a client URL into a sheet. Extract a Design System and Styleguide from a Website, Extract Fonts from a Website and Take a Screenshot of a Website gather the visual identity in one pass.

Finance and market data. Identify a Brand from Transaction Data turns a card line into a recognizable merchant, while Retrieve a Brand by Stock Ticker, Retrieve a Brand by ISIN and Retrieve a NAICS Code for a Brand serve analysts who start from a listed company or an industry code.

Two limits to know. Brand.dev has no trigger in Make, so another app or the schedule has to start the scenario. And Make's own documentation for Brand.dev is marked as limited, so test each module with Run once before relying on its output. If something breaks, the Make troubleshooting guide helps you read errors.

Wondering whether the same flow belongs in n8n instead? The n8n vs Make comparison lays out the criteria, and the Make pricing page explains how operations are counted.

Connect

How do you connect Brand.dev to Make?

  1. 01

    Add a Brand.dev module

    In your scenario, click the +, search for Brand.dev and pick any module. Then click Create a connection. A connection is your Brand.dev account linked to Make once and reused by every Brand.dev module afterward.

  2. 02

    Name it and authorize

    Give the connection a clear name if you like, useful once several people or accounts share the workspace. Then either authorize Make on the Brand.dev page that opens, or paste the key Brand.dev gives you, depending on what the window asks for.

  3. 03

    Save and reuse

    Click Save. The connection now appears in the dropdown of every Brand.dev module you add, so the other twelve modules skip this step entirely.

First scenario

Build your first Brand.dev scenario

GoalWhen a new lead with a website lands in another app, Make fetches the brand from Brand.dev and captures a screenshot of the site.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Start with the trigger of the app where your leads arrive, a form tool or a CRM, since Brand.dev cannot start a scenario itself.

  2. 02

    Look up the brand

    Click the + on the right of that first module and add Retrieve Brand Data by Domain. Pick your connection, then map the website or domain that the lead module delivers.

  3. 03

    Capture the site

    Add Take a Screenshot of a Website after it and map the same address. You now have the brand and a visual of the homepage traveling together in one bundle, the item that flows between modules.

  4. 04

    Test with Run once

    Click Run once and submit a test lead. Open each module's bubble to read what it received and returned, which matters here because the official Brand.dev documentation is thin.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run counts as one operation on your Make plan.

Modules

Every Brand.dev module, explained

Brand.dev gives you 13 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Brand.dev1

Extract Fonts from a Website

ActionIn the docs only

Point this module at a site and it pulls out the fonts that site uses, so you know which typefaces a brand relies on without opening a browser inspector.

When to use it
a client sends their URL for a new landing page and your designer needs the typography before the kickoff call.
Watch out
it covers type only; for colors and components, pick the design system module instead.
Brand.dev2

Extract Products from a Website

ActionIn the docs only

This module reads a website and returns the products it finds there, giving you a catalog view of a company from its own pages.

When to use it
you track competitors or prospects and want their product lineup stored in a sheet whenever a new domain enters your list.
Watch out
the documentation does not describe the output, so run it once on a real site before mapping fields downstream.
Brand.dev3

Extract a Design System and Styleguide from a Website

ActionIn the docs only

Here you get the broad visual picture of a site, its design system and styleguide, in a single step rather than piecing it together by hand.

When to use it
an agency onboarding a new client wants a starting brand sheet ready before anyone opens a design tool.
Watch out
if you only need typefaces, the lighter fonts module keeps the scenario simpler to read.
Brand.dev4

Identify a Brand from Transaction Data

ActionIn the docs only

Bank and card statements often show cryptic merchant labels. This module takes transaction data and tells you which brand is actually behind it.

When to use it
a finance team categorizing expenses, or a fintech app that wants to show a clean merchant name to its users.
Watch out
map the transaction text from the previous module and check a few results with Run once before trusting it at scale.
Brand.dev5

Make an API Call

ActionIn the docs only

When none of the other twelve modules does what you need, this one calls any endpoint of the Brand.dev API using the same connection, so you never have to set up authentication twice.

When to use it
Brand.dev offers an endpoint that Make has not packaged as a module yet.
Watch out
you write the request yourself, so keep the Brand.dev API reference open while you build it.
Brand.dev6

Retrieve Brand Data

ActionIn the docs only

This is the general lookup: it fetches the data Brand.dev holds on a brand and hands it to the next module of your scenario.

When to use it
you want the full brand profile and none of the more specific lookups by email, ticker or name fits what you already have.
Watch out
if your starting point is a domain, the dedicated domain module states your intent more clearly.
Brand.dev7

Retrieve Brand Data by Domain

ActionIn the docs only

Give it a domain and it returns the matching brand, the most direct path from a website address to a company profile.

When to use it
a signup, a lead or a row in a sheet contains a company website and you want the brand behind it attached to the record.
Watch out
clean the value first if your source stores full URLs with paths, then test with Run once.
Brand.dev8

Retrieve a Brand by Company Name

ActionIn the docs only

Starting from nothing more than a company name, this module finds the brand that goes with it, handy when no website or email is available.

When to use it
an event attendee list or a trade show export only gives you names typed by people.
Watch out
names are ambiguous by nature, so review a sample of matches before letting the result overwrite anything.
Brand.dev9

Retrieve a Brand by Email Address

ActionIn the docs only

Feed it an email address and it identifies the company behind it, turning a bare contact into a lead with a brand attached.

When to use it
a newsletter or demo form collects work emails and sales wants to know which company each person belongs to.
Watch out
personal addresses from free email providers may not lead to any company, so consider filtering them out before this module to save operations.
Brand.dev10

Retrieve a Brand by ISIN

ActionIn the docs only

Securities people work with ISIN codes, and this module translates one into the brand of the issuing company, so your reports show a name people recognize instead of a code.

When to use it
a portfolio report or an investment dashboard that should show a recognizable company name next to each holding.
Watch out
map the ISIN exactly as your source stores it and test a few lines first.
Brand.dev11

Retrieve a Brand by Stock Ticker

ActionIn the docs only

From a stock ticker, this module returns the listed company's brand, which saves you a manual search every time a symbol shows up.

When to use it
a watchlist sheet or a market newsletter that you want enriched with each company's brand data.
Watch out
check the returned brand with Run once on symbols you know.
Brand.dev12

Retrieve a NAICS Code for a Brand

ActionIn the docs only

NAICS is the North American industry classification. This module gives you the code for a brand, so you can sort companies by sector without guessing.

When to use it
you segment a lead list by industry for targeted campaigns or territory planning.
Watch out
store the code in its own column in your CRM or sheet so later filters stay simple.
Brand.dev13

Take a Screenshot of a Website

ActionIn the docs only

This module captures an image of a website, giving you a visual record of a page without opening it yourself.

When to use it
you want a thumbnail of each prospect's homepage in your CRM, or a snapshot of a competitor page kept alongside your notes.
Watch out
on the Free plan, files are capped at 5 MB, so check the size of what you pass to the next module.
Need help

Need help automating Brand.dev with Make?

A person reads every message.

FAQ

Brand.dev and Make: common questions

01Is the Brand.dev Make integration free?
Yes, on the Make side. Brand.dev is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute and remove the cap on active scenarios. Every module run is an operation, which is what Make counts on your plan. Your Brand.dev account and its own terms are a separate matter.
02What do you need to connect Brand.dev to Make?
A Brand.dev account and a Make account. Make's documentation lists no specific prerequisite for this app. You add any Brand.dev module, click Create a connection, optionally name it, then authorize Make or paste the key Brand.dev provides, and click Save. Make marks its Brand.dev documentation as limited, so follow what the connection window asks for and confirm the link by running one module with Run once. The same connection then serves all 13 modules.
03Does Brand.dev have a trigger in the Make integration?
No. All 13 Brand.dev modules are actions, so Brand.dev cannot start a scenario by itself. You have two ways to start one. Put the trigger of another app first, such as a form, a CRM or a spreadsheet, and let Brand.dev act on what it sends. Or use Make's scheduling, the clock on the first module, which runs a new scenario every 15 minutes by default and down to 1 minute on paid plans. Brand.dev modules then work on the data that first step provides.
04What if a Brand.dev module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Brand.dev API from your scenario with the connection you already created, so anything the 12 packaged modules do not cover stays reachable. You write the request yourself, so keep the Brand.dev API reference at hand. Also keep in mind that Make's own Brand.dev documentation is marked as limited, which makes testing each module with Run once the fastest way to see what it really returns before you map its output.
05Should you use Make or n8n for Brand.dev?
It depends on your criteria, not on a winner. In Make, Brand.dev comes with 13 modules including Make an API Call, it is available from the Free plan, and you build visually with a connection set up once. Whether Brand.dev also has an n8n node is worth checking on the n8n side before you decide. Compare the tools on how your team already works, the other apps your scenario needs, and how each one counts usage.
Same platform

Other docs you might need on this stack.

Browse all integrations