Resources · Make integration

Promptitude.io Make integrationAutomate Promptitude.io with Make.

Can your Promptitude.io prompts run on their own, fed by your other apps? The Promptitude.io Make integration gives you 3 action modules and no trigger. This guide shows how to link your API key, build a first scenario and pick the right module.

Try the Promptitude.io integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Promptitude.io Make integration let you automate?

The Promptitude.io Make integration links your Promptitude.io account to Make, so your prompts become steps inside a scenario, the automation you build in Make as a chain of modules. You get three actions: Generate a Prompt, Add a Rating and Make an API Call. There is no trigger, so another app or a schedule starts the flow.

Put a prompt behind a form or a spreadsheet. Another app starts the scenario with a new entry, and Generate a Prompt runs your Promptitude.io prompt on it. Each entry travels as a bundle, one item passed from module to module, so every new row gets its own run.

Keep score of what works. Add a Rating sits after the prompt step when you want a rating stored in Promptitude.io from the scenario instead of by hand.

Reach the rest of the API. Make an API Call reuses the same connection to call any endpoint of the Promptitude.io API that the two named modules leave out.

Know the limits before you start. The Make documentation for this app lists no module groups and no module descriptions, and it flags its own text as AI-generated, to verify with Promptitude.io. When a detail matters, check it on the Promptitude.io side. For a wider view of the tool, read the Make review; to see how plans count runs, open Make pricing. The same app often has an n8n node too, and n8n vs Make lays out the criteria.

Connect

How do you connect Promptitude.io to Make?

  1. 01

    Copy your API key

    You need an active Promptitude.io account first. Open the Settings page of that account and copy the API key shown on screen. Keep it at hand: Make asks for it in the next step, and nothing else is required.

  2. 02

    Add a module and create the connection

    In your Make scenario, add any Promptitude.io module and click Create a connection. A connection is your Promptitude.io account linked to Make once, then reused by all three modules.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you run several accounts. Paste the API key you copied, or follow the on-screen instructions, and save.

First scenario

Build your first scenario with Promptitude.io

GoalWhen a new entry lands in another app, Make runs your Promptitude.io prompt on it with Generate a Prompt.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Promptitude.io has no trigger, so this first module comes from the app that holds your data.

  2. 02

    Pick the starting app

    Search that app by name, choose its module and click Create a connection to link the account. Fill its fields; Make lists what it can read once connected.

  3. 03

    Add Generate a Prompt

    Click the + on the right of the first module, search Promptitude.io and pick Generate a Prompt. Select your connection, then map data from the previous module into its fields.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open each module afterwards and read the bundles it received to confirm your prompt got the right data.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run counts as one operation, the unit Make tracks on your plan.

Modules

What the Promptitude.io modules do

Promptitude.io gives you 3 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Promptitude.io1

Add a Rating

ActionIn the docs only

Going by its name, this action records a rating in your Promptitude.io account from inside a scenario, so the feedback you collect elsewhere reaches Promptitude.io without copying it over. As an action, it acts on one bundle at a time.

When to use it
after a step that produces the score you want stored, placed later in the chain than the module that creates it.
Watch out
the documentation describes none of its fields, so open the module after connecting and read what Make displays.
Promptitude.io2

Generate a Prompt

ActionIn the docs only

Here is the module most scenarios are built around: going by its name, it asks Promptitude.io to generate a prompt from the data mapped from earlier modules. You get a Promptitude.io step that runs each time the scenario does, with no copy and paste.

When to use it
whenever a new record from another app should go through one of your prompts.
Watch out
the documentation does not list its settings or output, so run it once and inspect the bundle before mapping anything downstream.
Promptitude.io3

Make an API Call

ActionIn the docs only

Think of it as the open door: with the same connection, it calls any endpoint of the Promptitude.io API from your scenario. That covers what Generate a Prompt and Add a Rating do not.

When to use it
when you need a Promptitude.io feature that the two named modules leave out.
Watch out
you pick the endpoint and build the request yourself, so keep the Promptitude.io documentation open while you set it up.
Need help

Need help automating Promptitude.io with Make?

A person reads every message.

FAQ

Promptitude.io and Make: common questions

01Is the Promptitude.io Make integration free?
Yes, on the Make side. Promptitude.io 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 drop the interval to one minute and allow up to 40 minutes of execution. Promptitude.io itself needs an active account, and its own subscription terms are on the Promptitude.io pricing page, which this guide does not cover.
02What do you need to connect Promptitude.io to Make?
An active Promptitude.io account and its API key. Open the Settings page in Promptitude.io, copy the key displayed there, then in Make add a Promptitude.io module and click Create a connection. Naming the connection is optional. Paste the key and save. That single connection then serves Generate a Prompt, Add a Rating and Make an API Call alike, so you set it up only once per account. If you manage several accounts, give each connection a clear name.
03Does Promptitude.io trigger Make scenarios in real time?
No, because the app has no trigger module at all. A scenario that uses it has to start somewhere else. You can open it with a trigger from another app, such as a form or a spreadsheet that receives new entries, or run it on the schedule set on the first module, every 15 minutes by default on a new scenario. The Promptitude.io modules then act as later steps in the chain.
04What if a Promptitude.io module you need is missing in Make?
Use Make an API Call. It reuses your Promptitude.io connection and can reach any endpoint of the app's API, so it covers what Generate a Prompt and Add a Rating do not. You pick the endpoint and write the request yourself, with the Promptitude.io documentation open. The Make documentation for this app also warns that its text is AI-generated and may contain mistakes, so confirm any detail that matters directly with Promptitude.io.
05Should you use Make or n8n for Promptitude.io?
It depends on your criteria, not on a winner. On Make, Promptitude.io offers three actions and a generic API module, with no trigger. The same app often has an n8n node as well, so check which modules each side exposes for the task you have in mind, and pick the tool your team already runs its other automations on. That keeps every flow, with its connections and logs, in one place. The n8n vs Make comparison walks through the general criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations