Resources · Make integration

Hugging Face Make integrationAutomate Hugging Face with Make.

What if the text piling up in your other tools could be summarized, translated or sorted without a single copy and paste? The Hugging Face Make integration gives you 7 modules: six actions and one search. This page helps you connect your account and build a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Hugging Face Make integration do for you?

The Hugging Face Make integration lets a Make scenario, the automation you build as a chain of bricks, send text to Hugging Face and get back an answer, a summary, a translation, a label or an image. Each brick is called a module, and none of them needs a line of code.

Shorter reading for your team. A long text arrives from another app, Create a Summary turns it into a few lines, and the next module posts that digest wherever your team reads it.

Content that speaks every language of your customers. A product description or a support reply goes through Create a Translation before it is sent, so the same scenario serves several markets.

A first sort on incoming messages. Create a Text Classification attaches a category to each message, and a filter in Make routes it to the right person. For open questions, Create a Chat Completion (Prompt) and Create an Answer write the reply, and Generate an Image draws a visual from a text prompt.

Hugging Face has no trigger in Make: it never starts a scenario by itself. Something else does, another app or a schedule, and Hugging Face works in the middle of the chain. When a listed module does not cover your need, Make an API Call reaches the rest of the API. The same app also exists on n8n: see the Hugging Face n8n integration and our n8n vs Make comparison, or start with the Make training if the editor is new to you.

Connect

How do you connect your Hugging Face account to Make?

  1. 01

    Add a Hugging Face module

    In your scenario, click the + and search for Hugging Face, then pick any of its modules. On the connection line, click Create a connection. A connection is your account linked to Make once and reused by every Hugging Face module.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, such as your team or project, so you can spot it later. Then authorize Make on the Hugging Face page that opens, or paste the key Hugging Face gives you, depending on what the window asks for.

  3. 03

    Save and reuse it

    Click Save. The connection now appears in the list of every Hugging Face module you add, in this scenario and the next ones, so the authorization happens only once per account.

First scenario

Your first scenario with Hugging Face and Make

GoalWhen a new text lands in another app, Make summarizes it with Hugging Face and translates the summary.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Choose the app where your texts arrive, for example a form tool or a spreadsheet, and its module that picks up new items.

  2. 02

    Add Create a Summary

    Click the + on the right of that first module, search for Hugging Face and pick Create a Summary. Select your connection, or click Create a connection if this is your first Hugging Face module.

  3. 03

    Map the text to summarize

    In the module fields, map the text coming from the first module. Each item flowing between modules is a bundle: one message, one row, one entry. Make then summarizes each bundle separately.

  4. 04

    Chain Create a Translation

    Add Create a Translation after the summary and map the summary text into it. The output is a short version of the original text, in the language your readers expect.

  5. 05

    Test with Run once

    Click Run once. Make runs the scenario one time, and a bubble on each module shows the bundles it received. Open them to check the summary and the translation before going further.

  6. 06

    Schedule and switch it on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Modules

What each Hugging Face module does in Make

Hugging Face gives you 7 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Hugging Face1

Create a Chat Completion (Prompt)

Action

In MakeGenerates a response given a list of messages in a conversational context.

This module sends a conversation, a list of messages, to a Hugging Face model and gets back the next reply. You obtain a written response that takes the earlier turns into account, not just the last line.

When to use it
a support assistant that must remember what the customer already said before drafting its answer.
Watch out
for a single standalone question, Create an Answer is simpler to set up.
Hugging Face2

Create an Answer

Action

In MakeCreates an answer for a given question.

Hand it one question and it writes one answer. It fits cases where each request stands alone and no conversation history matters, which keeps the mapping short in the editor.

When to use it
a question typed into a web form that needs a first draft reply before a person checks it.
Watch out
each question processed counts as one operation, so a batch of many bundles uses as many operations.
Hugging Face3

Create a Summary

Action

In MakeSummarizes longer text into shorter text.

Long text goes in, a shorter version comes out. Your readers get the gist of a report, an email thread or a transcript without opening the original document.

When to use it
a long customer email that lands in a shared inbox and should reach the team as a digest in your chat tool.
Watch out
map only the body of the text, since headers and signatures add noise to the result.
Hugging Face4

Create a Translation

Action

In MakeCreates a translation of the text.

You get the same text in another language, ready to be sent or stored by the next module. It lets one scenario feed several markets instead of maintaining one copy per language by hand.

When to use it
a product sheet written once that has to reach a second storefront in the local language.
Watch out
have a native speaker review the first results with Run once before the scenario runs on its own.
Hugging Face5

Generate an Image

Action

In MakeGenerates an image based on a given text prompt.

Describe a picture in words and this module produces the image. It turns a line of text coming from another app into a visual you can pass along to the rest of the scenario.

When to use it
an illustration for each new blog draft, built from its title or its summary.
Watch out
the quality depends on the prompt, so test several wordings with Run once before switching the scenario on.
Hugging Face6

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

This one opens the rest of the Hugging Face API to your scenario, with the same connection as the other modules. It covers what the six ready-made modules leave out.

When to use it
a task Hugging Face offers through its API that no listed module handles.
Watch out
you write the request yourself, so keep the Hugging Face API reference open while you fill the module.
Hugging Face7

Create a Text Classification

Search

In MakeCreates a text classification.

It reads a text and tells you which category it belongs to. Unlike the other modules, it is a search: it can return zero, one or several results, each as its own bundle.

When to use it
sorting incoming messages so complaints, questions and sales leads each go to the right person.
Watch out
add a filter after it in Make to route each bundle on the label you care about.
Need help

Need help automating Hugging Face with Make?

A person reads every message.

FAQ

Questions about the Hugging Face Make integration

01Is the Hugging Face Make integration free?
Yes, on the Make side. Hugging Face is a standard app, available from the Free plan, like the 3,000+ standard apps on every plan. The Free plan allows 2 active scenarios, a minimum interval of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Make counts usage in operations: one each time a module handles a bundle, so a busy scenario uses more of your plan. What Hugging Face bills on its own side is not covered here.
02What do you need to connect Hugging Face to Make?
A Hugging Face account and a Make account. The Make documentation lists no specific prerequisite for this app. You add any Hugging Face module, click Create a connection, give it a name if you want, then authorize Make on the Hugging Face page or paste the key Hugging Face gives you, and click Save. The connection is stored once and every Hugging Face module in your scenarios can reuse it, so you never repeat the authorization for each new module.
03Can Hugging Face start a Make scenario on its own?
No. The Hugging Face app has no trigger in Make, only six actions and one search. Your scenario starts elsewhere: a trigger from another app, such as a new form entry or a new row in a spreadsheet, or the schedule on the first module, which runs every 15 minutes by default. Hugging Face then sits in the middle of the chain and processes each bundle it receives. On the Free plan the shortest scheduled interval is 15 minutes; paid plans go down to 1 minute.
04What if a Hugging Face module is missing in Make?
Use Make an API Call. This module is part of the Hugging Face app in Make and calls any endpoint of the Hugging Face API with the connection you already set up, so you cover what the six other modules do not. You write the request yourself, which asks for a look at the Hugging Face API reference. The Make documentation gives no numbered limit for this app, so none applies beyond the limits of your Make plan, such as execution time per run.
05Make or n8n for Hugging Face?
It depends on the tool your team already uses. Hugging Face exists on both platforms, so the choice comes down to where your other automations live and which editor your team prefers. In Make, the app offers 7 modules, including Make an API Call for the rest of the API, and it works from the Free plan. If your workflows already run in n8n, the n8n node is the natural pick. Both platforms have a dedicated page on this site if you want to compare them side by side.