Resources · Make integration

Cleanvoice AI Make integrationAutomate Cleanvoice AI with Make.

Can your podcast audio get cleaned while you work on something else? The Cleanvoice AI Make integration offers 3 modules: 1 trigger that spots finished edits and 2 actions. This guide is for creators and small production teams, and it walks you from the connection to a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Cleanvoice AI Make integration do for you?

Cleanvoice AI strips filler words and background noise from audio and video files. Linked to Make, it becomes part of a scenario, the automation you build as a chain of modules, where each module is one brick: a trigger that starts the flow or an action that does something. Your recordings get edited, and the rest of your tools hear about it, without you clicking through each step.

Episodes that clean themselves. A podcaster drops a raw recording into the storage app the team already uses. The scenario picks it up and hands it to Create an Edit, which starts a new edit from a custom template you prepared in Cleanvoice AI.

An editor who knows when to listen. Watch Completed Trigger notices each finished edit and passes it on, so a message can reach the person in charge of review in Slack or by email instead of everyone refreshing the dashboard.

A production board that stays honest. The same trigger can move a card in Notion or Trello once the audio is done, which keeps the content calendar in line with reality.

Know the limits before you build. The trigger is scheduled, not instant, and the app has no search module; anything the two actions do not cover goes through Make an API call. Make itself flags its Cleanvoice AI documentation as AI-generated, so check important details with Cleanvoice AI directly. If your team also looks at n8n, the n8n vs Make comparison lays out both tools, and the Make pricing page explains what each plan includes. Stuck on a failing run? Make troubleshooting covers the usual causes.

Connect

How do you connect Cleanvoice AI to Make?

  1. 01

    Copy your API key from Cleanvoice AI

    Log in to Cleanvoice AI, open Settings, then the API section. Your key is shown on screen: copy it and keep the tab open, you will paste it in Make a moment later.

  2. 02

    Add a Cleanvoice AI module and create the connection

    In your Make scenario, add any Cleanvoice AI module and click Create a connection. A connection is your Cleanvoice AI account linked to Make once, then reused by every module of the app. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste the key and save

    Paste the API key you copied, or follow the instructions Make shows on screen, then confirm. From now on, the three Cleanvoice AI modules can use this account without asking again.

First scenario

Build your first scenario with Cleanvoice AI

GoalWhen a new recording lands in your storage app, Make starts a Cleanvoice AI edit for it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. Search for the storage app where your raw recordings arrive and pick the module that watches for new files.

  2. 02

    Add Create an Edit

    Click the + on the right of that first module, search for Cleanvoice AI and choose Create an Edit. Click Create a connection if you have not linked your account yet.

  3. 03

    Map the recording into the edit

    Fill the fields of Create an Edit. Once the connection exists, Make lists what it can read from your account, and you map data from the previous module. Which fields the template asks for depends on your Cleanvoice AI setup; Run once will show you what reaches the module.

  4. 04

    Test with Run once

    Drop a test file in your folder, then click Run once. Make runs the scenario one time and shows the bundles each module received: one bundle is one item passing from a module to the next, here one recording.

  5. 05

    Schedule it and switch it on

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

Triggers

What starts a Cleanvoice AI scenario?

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

Cleanvoice AI1Watch Completed Trigger

Watch Completed Trigger

Scheduled trigger

In MakeTriggers when a new edit is completed.

This trigger tells your scenario that Cleanvoice AI has finished an edit, so the cleaned file can move on to review, publishing or a status update without anyone watching the dashboard. Each completed edit reaches the next module as its own bundle.

How it fires
it is a scheduled trigger, so Make checks the app on the scenario's schedule, every 15 minutes by default, rather than hearing from Cleanvoice AI the second an edit ends.
When to use it
a producer wants a Slack alert, or a Trello card moved, each time an episode is ready to listen to.
Watch out
on the Free plan the shortest interval between two checks is 15 minutes, so plan your review flow around that gap.
Modules

What can Make do in Cleanvoice AI?

Cleanvoice AI gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Cleanvoice AI1

Create an Edit

Action

In MakeCreates a new edit from a custom template.

Hand Cleanvoice AI a new job straight from your scenario: this action starts an edit based on a custom template you set up in the app, so every recording gets the same treatment.

When to use it
right after the module that brings in a fresh interview or episode from your storage app.
Watch out
each bundle that reaches it creates one edit and costs one operation, so a first module that returns ten files starts ten edits.
Cleanvoice AI2

Make an API call

Action

In MakePerforms an arbitrary authorized API call.

Reach any endpoint of the Cleanvoice AI API from your scenario, using the connection you already created, and cover what the two ready-made modules leave out.

When to use it
your process needs a Cleanvoice AI feature that neither Create an Edit nor the trigger offers.
Watch out
nothing is prefilled here; you choose the endpoint and write the request yourself, so test it with Run once before switching the scenario on.
Need help

Need help automating Cleanvoice AI with Make?

A person reads every message.

FAQ

Questions people ask about Cleanvoice AI and Make

01Is the Cleanvoice AI Make integration free?
Yes, on the Make side. Cleanvoice AI is a standard app, available from the Free plan onward. 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 drop the interval to 1 minute and allow 40 minutes of execution. Your Cleanvoice AI subscription is separate: its terms are on the Cleanvoice AI pricing page, and Make does not cover it.
02What do you need to connect Cleanvoice AI to Make?
An active Cleanvoice AI account and its API key. You find the key in Cleanvoice AI under Settings, then the API section, where it is displayed on screen. In Make, add any Cleanvoice AI module, click Create a connection, give it a name if you like, and paste the key. The connection is then shared by the trigger and the two actions, so you only do this once per account.
03Does the Cleanvoice AI trigger in Make react in real time?
No. Watch Completed Trigger is a scheduled trigger: Make checks Cleanvoice AI for completed edits on the scenario's schedule, which is every 15 minutes by default. On the Free plan you cannot go below 15 minutes; paid plans go down to 1 minute. If a finished edit needs to reach your team faster, a paid plan with a shorter schedule is the lever Make gives you, since the app offers no instant trigger.
04What if a Cleanvoice AI module is missing in Make?
Use Make an API call. It calls any endpoint of the Cleanvoice AI API with the same connection, so you are not limited to Create an Edit and the completed-edit trigger. You pick the endpoint and build the request, then test it with Run once. Keep in mind that Make labels its own Cleanvoice AI documentation as AI-generated, so confirm important behavior with Cleanvoice AI before you rely on it in production.
05Should you use Make or n8n for Cleanvoice AI?
It depends on which tool your team already works in. Many apps have both a Make app and an n8n node, so check whether one exists for Cleanvoice AI before choosing. On Make, the app gives you a scheduled trigger for completed edits, an action that creates edits from a template and an API call for the rest, all behind one connection. The n8n vs Make comparison on this site sets the two tools side by side, without ranking one above the other.