Resources · Make integration

AutoContent API Make integrationAutomate AutoContent API with Make.

What can the AutoContent API Make integration do for your content? Make offers 10 modules for this app: 1 trigger, 7 actions and 2 searches. This guide is for marketers and producers who want podcasts and transcripts handled without code, and it walks you to a working first scenario.

Try the AutoContent API integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the AutoContent API Make integration let you automate?

The AutoContent API Make integration links your AutoContent API account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, acts or searches. Once linked, Make can start podcasts, clone voices and pull transcripts for you, and pass the results to your other apps.

Turn an idea into an episode. A new row in your editorial planner can feed Create a Podcast, and Update a Podcast lets you correct it later without starting over.

Keep written copies of your audio. Watch New Content Creation spots fresh content, then Get a Transcript fetches the text so your blog or help center team can reuse it.

Keep an eye on usage. Get an Account Usage and Get a Content Status tell you where your account stands and whether a job is ready, handy before you chain the next step.

Know the limits before you start. Make's own documentation for this app is thin: it lists the modules but explains neither their fields nor their behavior, so plan to test each module with real data. For anything the list does not cover, Make an API Call reaches the rest of the API. New to the editor? The Make training covers the basics, and if you are also weighing n8n, read n8n vs Make. When a run fails, Make troubleshooting lists the usual fixes.

Connect

How do you connect AutoContent API to Make?

  1. 01

    Add an AutoContent API module

    In your scenario, click the + and search for AutoContent API, then pick any module. Make asks for a connection, meaning your AutoContent API account linked once and reused by every module of the app. Click Create a connection.

  2. 02

    Name it and authorize Make

    Give the connection a name you will recognize later, for example the client or workspace it belongs to. Then either authorize Make on the AutoContent API page that opens or paste the key the app gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. The connection now appears in the module, and every other AutoContent API module in your scenarios can pick it from the list instead of asking again.

First scenario

Build your first scenario with AutoContent API

GoalWhen a new article shows up in another app, Make runs Create a Podcast in AutoContent API with the data from that article.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the canvas. This first module is the starting point: the app where your articles live, such as a sheet or a CMS.

  2. 02

    Set up the starting module

    Pick the watch module of that app, connect your account and choose the folder or sheet it should read. Once the connection exists, Make lists what it can see, so you just select it.

  3. 03

    Add Create a Podcast

    Click the + on the right of the first module, search for AutoContent API and choose Create a Podcast. Link your account with Create a connection if you have not done it yet.

  4. 04

    Map the article data

    Fill the fields Make shows by clicking into them and picking values from the first module, like the title or the body of the article. Each article travels as one bundle, a single item passed from module to module.

  5. 05

    Test with Run once

    Click Run once. Make runs the scenario one time; open the bubbles above each module to read the bundles they received and confirm the podcast request went through.

  6. 06

    Schedule and switch it on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then turn the scenario on. On the Free plan, 15 minutes is also the shortest interval.

Triggers

What starts an AutoContent API scenario?

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

AutoContent API1Watch New Content Creation

Watch New Content Creation

triggerIn the docs only

This trigger starts your scenario with the new content AutoContent API has produced since the last check, so the next steps happen without you checking the app. Make's doc lists it without a description, so its exact output is something to discover on the first test.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default.
When to use it
as the first module when your podcasts are created in the AutoContent API app itself and you want Make to pick them up afterwards.
Watch out
each check that runs the module counts as an operation, one execution Make bills on your plan, so a very short schedule spends your quota faster.
Modules

What can AutoContent API do in Make?

AutoContent API gives you 9 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

AutoContent API1

Create a Podcast

ActionIn the docs only

You get a new podcast started in AutoContent API straight from your scenario, fed by data another app already holds, so nobody has to copy text into the app by hand.

When to use it
right after a piece of content is approved elsewhere and should become audio.
Watch out
the doc lists no fields for it, so open the module after connecting to see exactly what it expects.
AutoContent API2

Create a Voice Clone

ActionIn the docs only

This one sets up a cloned voice in your AutoContent API account from a scenario, which saves repeating the setup in the app for every new speaker or brand voice you add.

When to use it
when a new host or presenter joins and their voice should be ready for future episodes.
Watch out
Make documents none of its inputs, so test it once on a sample before you automate it.
AutoContent API3

Get a Content Status

ActionIn the docs only

It tells your scenario where a piece of content stands in AutoContent API, which lets you decide whether to continue or wait instead of sending an unfinished job to the next app.

When to use it
between Create a Podcast and any step that needs the finished result.
Watch out
read the status values it returns during Run once, since the doc does not describe them.
AutoContent API4

Get a Transcript

ActionIn the docs only

With this module you pull the text version of a piece of content into Make, ready to drop into a document, a newsletter draft or a knowledge base without retyping anything.

When to use it
after Watch New Content Creation, to keep a written copy of each new episode.
Watch out
it works on one item at a time, so point it at the exact content you want.
AutoContent API5

Get an Account Usage

ActionIn the docs only

Your scenario reads how much of your AutoContent API account you have used, so a report or an alert can warn someone before the account runs short in the middle of a batch.

When to use it
at the start of a scenario that creates many podcasts, as a quick check.
Watch out
the doc gives no detail on the figures returned, so check them against the app once.
AutoContent API6

List Podcasts

SearchIn the docs only

As a search, it brings back your podcasts from AutoContent API as separate bundles: zero, one or several, one per podcast, which you can then filter, count or copy into a sheet.

When to use it
to build an inventory of episodes or find one before running Update a Podcast.
Watch out
every podcast returned makes the following modules run once more, and each run costs an operation.
AutoContent API7

List Voices

SearchIn the docs only

Here you get the voices available in your account, returned one bundle per voice, which is the simplest way to see which voice to pick before you create anything in a scenario.

When to use it
when a scenario must choose a voice, or after Create a Voice Clone to confirm it appears.
Watch out
an empty result is a normal outcome for a search, not an error.
AutoContent API8

Make an API Call

ActionIn the docs only

This module opens the rest of the AutoContent API to your scenario: any endpoint of the app can be called with the same connection, even one no listed module covers yet.

When to use it
when the nine other modules stop short of what you need and the app's API offers it.
Watch out
you write the request yourself here, so keep the AutoContent API reference open while you set it up.
AutoContent API9

Update a Podcast

ActionIn the docs only

You change an existing podcast in AutoContent API from Make, which spares you from deleting and recreating it when a detail needs fixing after the first version.

When to use it
after List Podcasts has found the episode that needs a correction.
Watch out
the doc lists no fields, so check on a test podcast which details the module can actually change.
Need help

Need help automating AutoContent API with Make?

A person reads every message.

FAQ

AutoContent API and Make: common questions

01Is the AutoContent API Make integration free?
Yes, on Make's side. AutoContent API is a standard app, so its modules work from the Free plan. That plan allows 2 active scenarios, a scheduled run every 15 minutes at the shortest, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Make counts usage in operations per month. What your AutoContent API account itself costs is a separate matter with the app.
02What does it take to connect AutoContent API to Make?
An AutoContent API account and a Make account. Make's doc lists no other prerequisite for this app. You add any AutoContent API module, click Create a connection, give it a name if you like, then either authorize Make on the app's page or paste the key the app provides. Click Save and the connection is ready for every module of the app in all your scenarios. If the window asks for something unexpected, keep in mind that Make describes its documentation for this app as limited.
03Does the AutoContent API Make trigger react in real time?
No. The only trigger, Watch New Content Creation, is scheduled: Make checks AutoContent API on the scenario's schedule instead of being called by the app. A new scenario checks every 15 minutes by default, which is also the minimum on the Free plan; paid plans go down to 1 minute. So new content reaches your scenario at the next check, not the second it is created. Keep in mind that each check uses an operation from your plan, even when nothing new turns up.
04What if an AutoContent API module is missing in Make?
Use Make an API Call. It lets a scenario call any endpoint of the AutoContent API with the connection you already set up, so you are not limited to the 10 listed modules. You do need to build the request yourself from the app's own API reference. This matters more than usual here: Make states that its documentation for AutoContent API is limited, so the listed modules come with no field descriptions and testing each one with Run once is the safest path.
05Make or n8n for AutoContent API: which one fits?
It depends on the tool your team already runs. On Make, AutoContent API brings 10 modules, works from the Free plan and includes Make an API Call for anything missing. If you work in n8n, first check whether an AutoContent API node exists there before comparing. Pick the editor your team finds easier to maintain, then test your real case on it. The comparison article linked above on this page lays out how the two tools differ.
Same platform

Other docs you might need on this stack.

Browse all integrations