Resources · Make integration

Presentations.AI Make integrationAutomate Presentations.AI with Make.

Could a deck build itself from the source file? The Presentations.AI Make integration gives you 2 action modules: one starts a presentation from a file, the other adds a slide. This guide walks you through the connection, a first scenario and the limits worth knowing.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Presentations.AI Make integration do for you?

The Presentations.AI Make integration lets a Make scenario (the automation you build, a chain of modules) create presentations for you. It has 2 modules, both actions: one builds a presentation from a file, the other adds a slide. Nothing in Presentations.AI starts a scenario, so the starting point comes from another app or from a schedule.

A deck out of every new document. A sales team drops a brief into its storage app; a trigger from that app hands the file to Create a Presentation from a File, and the first draft of the deck exists without anyone opening Presentations.AI.

A closing slide that is always there. After the deck step, Create a Slide produces one more slide, for instance a contact slide or a summary built from data an earlier module passed along. Check in the editor how it attaches to a presentation, since the documentation says nothing on that point.

Content from forms or tables. Answers collected by a form tool, say the one described on our 123FormBuilder Make integration page, can feed Create a Slide so each submission ends up on a slide.

Be aware of what is missing. Make's own documentation for this app is marked as limited, because there is not enough public information about Presentations.AI; it lists no field, prerequisite or connection step. Expect to discover the module settings in the editor, and read Make troubleshooting if a run fails. The app also has no Make an API Call module.

Weighing tools before you start? Our n8n vs Make comparison sets out the criteria, and the Make training covers scenario basics step by step.

Connect

How do you connect Presentations.AI to Make?

  1. 01

    Add a Presentations.AI module

    In your scenario, add either Presentations.AI module and click Create a connection. A connection is your Presentations.AI account linked to Make once, then reused by both modules of the app.

  2. 02

    Name the connection if you like

    Make offers a name field for the connection. Filling it is optional, but a clear name such as the account owner or the team helps when several people share the same Make organization.

  3. 03

    Authorize Make and save

    Depending on what the app asks, approve access on the Presentations.AI page that opens or paste the key the app gives you. Then click Save; the module can now use your account.

First scenario

Your first scenario with Presentations.AI

GoalWhen a new file lands in another app, Make turns it into a Presentations.AI presentation and adds a slide to it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Pick the trigger of the app where your source files arrive, since Presentations.AI has no trigger of its own.

  2. 02

    Add the presentation module

    Click the + to the right of the trigger, search for Presentations.AI and choose Create a Presentation from a File. Create the connection, then map the file coming from the trigger.

  3. 03

    Add the slide

    Add Create a Slide after it. Fill the fields the editor shows and map data from earlier modules; the documentation lists none, so read each label before choosing.

  4. 04

    Test with Run once

    Click Run once, then drop a test file in the source app. Open each module's bubble to read the bundles it received, a bundle being one item passed from one module to the next.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module; a new scenario checks 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 the Presentations.AI modules do

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

Presentations.AI1

Create a Presentation from a File

ActionIn the docs only

Gives you a new Presentations.AI presentation built from a file that an earlier module hands over, so a document becomes a deck without manual copying. It is the natural first Presentations.AI step of any scenario, since it is the module that creates the deck itself.

When to use it
a report, brief or proposal arrives in a storage or email app and should become slides straight away.
Watch out
Make documents this app only partially, so check in the editor which file inputs the module accepts before relying on it.
Presentations.AI2

Create a Slide

ActionIn the docs only

Gets you a single new slide in Presentations.AI, filled with data mapped from other apps, instead of producing a whole deck. Choose it over the file module when your content comes as small pieces, such as a row or an answer, rather than as a finished document.

When to use it
each new form submission or table row should show up as its own slide.
Watch out
every slide created is one operation, so a list of many rows adds up quickly on your plan.
Need help

Need help automating Presentations.AI with Make?

A person reads every message.

FAQ

Questions about the Presentations.AI Make integration

01Is the Presentations.AI Make integration free?
Yes, on the Make side. Presentations.AI 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, Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations per month. Your Presentations.AI subscription is a separate matter that this page does not cover.
02What do you need to connect Presentations.AI to Make?
A Presentations.AI account and a Make account. Make's documentation lists no specific prerequisite for this app and does not detail its connection steps, so the generic flow applies: add a Presentations.AI module, click Create a connection, optionally name it, authorize Make on the Presentations.AI page or paste the key the app provides, then click Save. The same connection then serves both modules, so you only set it up once per account.
03Can Presentations.AI start a Make scenario on its own?
No. Presentations.AI has no trigger module in Make, scheduled or instant, so nothing happening in the app can start a scenario. You start the flow elsewhere: with a trigger from the app where your files or data arrive, or with the schedule on the first module, which is every 15 minutes by default for a new scenario. The Presentations.AI modules then run as later steps. On the Free plan, scheduled runs cannot be closer than 15 minutes apart; paid plans go down to 1 minute.
04What if a Presentations.AI module you need is missing in Make?
It depends on the need. The app offers only 2 modules, Create a Presentation from a File and Create a Slide, and it has no Make an API Call module to reach other features. Make also flags its documentation for this app as limited, due to scarce public information. If your use case goes beyond those two actions, look for another presentation tool in Make that covers it, or ask the team for help designing the scenario around what is available.
05Should you use Make or n8n for Presentations.AI?
It depends on your criteria, not on a winner. On Make, Presentations.AI comes with 2 action modules and a connection reused by both, and the app is available from the Free plan. An app listed on Make often has an n8n node too, but check that one exists for Presentations.AI before choosing. Compare what each tool lets you do with this app, how you prefer to build, and which tool your team already uses for its other automations.