Resources · Make integration

ElevenLabs Make integrationAutomate ElevenLabs with Make.

Can Make write your ElevenLabs voiceovers and run your voice agents for you? The ElevenLabs Make integration gives you 16 modules: 1 instant trigger, 11 actions and 4 searches. This guide connects your account and builds a first scenario with you.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the ElevenLabs Make integration let you automate?

The ElevenLabs Make integration links your ElevenLabs account to Make, a no-code tool where you build a scenario (the automation itself: a chain of modules, where each module is one brick, such as a trigger, an action or a search). Your text becomes speech, and your conversational agents get created, copied or updated without opening the ElevenLabs dashboard.

Voiceovers from written content. A product description, a lesson script or a short announcement lands in another app. Create a speech synthesis turns that text into speech inside the same scenario, so nobody has to paste it into ElevenLabs by hand.

A tidy fleet of voice agents. Support teams that run one agent per brand or per language can build them from a template with Create a duplicate agent, then adjust the copy with Update an agent. List agents gives you the inventory whenever you need to check what exists.

Follow-up after each call. Watch new events starts a scenario the moment ElevenLabs reports something, and Get conversation details or List conversations pull what was said so a CRM or a shared sheet stays current.

The official doc gives no numeric limit for this app, and the listed modules do not cover the whole ElevenLabs API. For the rest, Make an API call reuses your connection to reach any other endpoint. ElevenLabs may also be available as an n8n node; the n8n vs Make page sets the two tools side by side. New to the editor? Make training covers the basics, and Make troubleshooting helps when a run fails.

Connect

How do you connect your ElevenLabs account to Make?

  1. 01

    Copy your API key from ElevenLabs

    Log in to ElevenLabs, click your profile icon in the top-right corner, then Profile. Next to the API Key field, click the eye icon to reveal the value, then copy it.

  2. 02

    Open a connection in Make

    In your scenario, add any ElevenLabs module and click Create a connection. A connection is your ElevenLabs account linked to Make once. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste the key and save

    Paste the value into the API Key field and click Save. If ElevenLabs asks you to authenticate and confirm access, accept. Every ElevenLabs module in your scenarios can now reuse this connection.

First scenario

Your first scenario: turn incoming text into speech

GoalWhen a new piece of text arrives in another app, Make sends it to ElevenLabs and gets the spoken version back.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Pick the app that holds your text, for example a table where scripts get written.

  2. 02

    Add the ElevenLabs action

    Click the + on the right of that first module, search for ElevenLabs and choose Create a speech synthesis. Click Create a connection if your account is not linked yet.

  3. 03

    Map the text

    In the module fields, map the text coming from the first module. Each item that flows between modules is called a bundle: here, one bundle is one script to read aloud.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time, and you can open each module to read the bundles it received and check that ElevenLabs returned the speech.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (a new scenario runs every 15 minutes by default) and switch the scenario on. Each module run counts as an operation on your Make plan.

Triggers

What can start an ElevenLabs scenario?

1 module starts a scenario when something happens in ElevenLabs. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by ElevenLabs as soon as it happens.

ElevenLabs1Watch new events

Watch new events

Instant trigger

In MakeWatch new events.

Watch new events puts ElevenLabs in charge of starting your scenario: as soon as your account reports an event, Make receives it and runs the modules that follow. It is the only trigger this app offers, so any flow that reacts to ElevenLabs activity starts here.

How it fires
this is an instant trigger (the lightning badge). ElevenLabs calls Make through a webhook as soon as the event happens, instead of Make checking on a timer.
When to use it
you want another tool, such as your CRM, to react to ElevenLabs activity without retyping anything.
Watch out
the doc does not list which event types arrive, so run the scenario once and read the bundle before mapping anything.
Modules

Every ElevenLabs module, explained

ElevenLabs gives you 15 modules in 2 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Actions

2 modules
ElevenLabs1

Create a speech synthesis

Action

In MakeSynthesizes a text into speech.

Hand ElevenLabs a piece of text and get it back as spoken audio, right inside your scenario. This is the heart of the app for anyone producing voiceovers at volume.

When to use it
a new blog summary or course script is ready and needs a narrated version.
Watch out
pick the voice first with List voices so the synthesis sounds the way you expect.
ElevenLabs2

Make an API call

Action

In MakePerforms an arbitrary authorized API call.

Reach any ElevenLabs API endpoint that the other modules skip, using the same connection you already set up. It keeps your scenario going when a feature has no dedicated module.

When to use it
you need an ElevenLabs capability that none of the 15 named modules covers.
Watch out
the request is only as good as what you describe, so keep the ElevenLabs API reference open and test with Run once.

Other modules

13 modules
ElevenLabs3

Create a duplicate agent

Action

In MakeCreate a new agent by duplicating an existing one.

Clone an agent you already tuned and get a fresh copy you can adapt, without rebuilding its setup by hand. Handy when several agents share the same base.

When to use it
a new client or a new language needs an agent that behaves like your template.
Watch out
treat the copy as its own agent and adjust it with Update an agent.
ElevenLabs4

Create an agent

Action

In MakeCreate an agent from a config object.

Build a brand new conversational agent from a configuration object, straight from Make. Pick it over duplication when no existing agent is close enough to copy.

When to use it
a form or a table describes the agent you want, and Make should create it from those values.
Watch out
the module builds the agent from the config object you pass, so check the result with Get an agent config after the first run.
ElevenLabs5

Delete an agent

Action

In MakeDelete an agent.

Remove an agent from your ElevenLabs account as a step of a scenario, which keeps your agent list clean when projects close.

When to use it
a campaign or a client contract ends and its dedicated agent should disappear with it.
Watch out
treat the deletion as final: place a filter before this module and test on a throwaway agent first.
ElevenLabs6

Get an agent config

Action

In MakeRetrieve config for an agent.

Read the full configuration of one agent and pass it to the next modules, so you can inspect or archive how that agent is set up.

When to use it
before updating an agent, you want a copy of its current settings stored in a sheet or a document.
Watch out
it needs the agent identifier; List agents is the easy way to find it.
ElevenLabs7

Get a voice

Action

In MakeRetrieves metadata about a specific voice.

Fetch the metadata of one specific voice, so later modules know exactly which voice they are working with. It answers questions about a single voice rather than listing them all.

When to use it
you store a voice identifier per brand and want its details before generating audio.
Watch out
this returns information about the voice, not audio; the sound comes from Create a speech synthesis.
ElevenLabs8

Get conversation details

Action

In MakeGet the details of a particular conversation.

Pull everything ElevenLabs keeps about one conversation between an agent and a caller, ready to send to another app. It is the module that turns a call into a usable record.

When to use it
after Watch new events, once Run once shows that the event concerns a conversation, to copy that call into your helpdesk or CRM.
Watch out
run it once and read the bundle, since the doc does not describe which details come back.
ElevenLabs9

Get user subscription

Action

In MakeGets extended information about the users subscription.

Read extended information about your ElevenLabs subscription and use it inside a scenario. It lets an automation check your plan situation without anyone logging in.

When to use it
before launching a big batch of speech syntheses, to see where your ElevenLabs account stands.
Watch out
it reads the account behind the connection, so a scenario using a different connection sees a different subscription.
ElevenLabs10

Outbound call via Twilio

Action

In MakeHandle an outbound call via Twilio.

Have an ElevenLabs agent place a phone call through Twilio, triggered by your scenario rather than by a person dialing. This is how a voice agent can reach out instead of only answering.

When to use it
a lead fills in a callback form and an agent should call them back.
Watch out
the doc does not describe the Twilio setup it relies on, so test with your own number before calling real contacts.
ElevenLabs11

Update an agent

Action

In MakePatches an agent's settings.

Change the settings of an existing agent without touching the rest of its configuration, since the module patches only what you send. Your agents stay in sync with the source of truth you keep elsewhere.

When to use it
opening hours or a product answer change in your knowledge table and the agent must follow.
Watch out
save the current state with Get an agent config first, so you can roll back by hand.
ElevenLabs12

List agents

Search

In MakeLists agents and their metadata.

Return the agents on your account with their metadata, one bundle per agent. It gives a scenario the full inventory to loop over or report on.

When to use it
you need to find the identifier of an agent before reading, updating or deleting it.
Watch out
as a search, it can return zero, one or many bundles, and every following module runs once per bundle, which adds operations.
ElevenLabs13

List conversations

Search

In MakeGet all conversations of agents that user owns. With option to restrict to a specific agent.

Collect the conversations handled by the agents you own, with the option to narrow the list to a single agent. Use it to catch up on activity in one pass rather than one call at a time.

When to use it
a manager wants a digest of the calls one support agent handled.
Watch out
without the agent filter you get conversations from every agent, which can mean many bundles.
ElevenLabs14

List models

Search

In MakeGets a list of available models.

See which ElevenLabs models are available to your account, returned as bundles your scenario can read or store. It keeps your setup honest about what can actually be used.

When to use it
you maintain a reference sheet of models for the team and want it filled from the source.
Watch out
it only lists models; choosing one still happens in the module that generates or configures.
ElevenLabs15

List voices

Search

In MakeLists all available voices for a user.

Get every voice available to your ElevenLabs user, so you can pick one by name or keep a catalog up to date. Each voice arrives as its own bundle.

When to use it
you want to choose the right voice identifier before setting up Create a speech synthesis.
Watch out
add a filter after it when you only need one voice, otherwise the next modules run for all of them.
Need help

Need help automating ElevenLabs with Make?

A person reads every message.

FAQ

ElevenLabs and Make: common questions

01Is the ElevenLabs Make integration free?
Yes, on the Make side. ElevenLabs is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum 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 (Core, Pro, Teams and Enterprise) drop the interval to 1 minute and remove the cap on active scenarios. Make counts every module run as an operation, and the ElevenLabs account itself is a separate matter handled with ElevenLabs.
02What do you need to connect ElevenLabs to Make?
An ElevenLabs account and its API key. In ElevenLabs, open your profile icon, then Profile, click the eye icon next to API Key and copy the value. In Make, add an ElevenLabs module, click Create a connection, paste the key in the API Key field and click Save. If you are asked to authenticate and confirm access, accept. The connection is created once and every ElevenLabs module can reuse it, so there is nothing else to set up per module.
03Does the ElevenLabs trigger in Make react in real time?
Yes. Watch new events is an instant trigger, marked with the lightning badge in the editor. ElevenLabs calls Make through a webhook as soon as the event happens, so the scenario does not wait for a scheduled check. That is the only trigger of the app. If your flow starts elsewhere, for example a new script in a table, you open the scenario with that other app and add ElevenLabs actions after it; the first module then follows the scenario schedule, every 15 minutes by default.
04What if an ElevenLabs module is missing in Make?
Use Make an API call. It is part of the ElevenLabs app in Make and lets a scenario call any endpoint of the ElevenLabs API with the connection you already created. The official doc gives no numeric limit for the app, so there is no documented cap to plan around. When a request fails, start by running the scenario once and reading the bundle each module received, to see where the flow stops. The 15 named modules cover speech synthesis, agents, voices, models and conversations.
05Should you use Make or n8n for ElevenLabs?
It depends on where you want to build. This page covers Make, where ElevenLabs offers 16 modules including an instant trigger and a way to call the rest of the API. ElevenLabs may also exist as a node in n8n, and the comparison page linked in the section above lays out how the two tools differ. A practical test: list the actions your flow needs, check that the modules on this page cover them, then build a first scenario and run it once before deciding.