PromptLayer Make integrationAutomate PromptLayer with Make.
Want your PromptLayer agent to get to work when new data shows up in another tool? The PromptLayer Make integration gives you one action module, Run Agent. This page walks ops and product teams through the connection, a first scenario and the questions that usually follow.
Verified Trustpilot reviews · AI, automation & growth agency
What does the PromptLayer Make integration let you automate?
The PromptLayer Make integration lets a Make scenario, the automation you build in Make, start an agent you set up in PromptLayer. It relies on a single module, meaning one brick of the scenario: Run Agent, an action. Something else has to start the scenario, such as another app or a schedule.
Answer incoming requests with your agent. A form tool or a chat app starts the scenario, Run Agent passes the message to your PromptLayer agent, and the next module delivers the reply wherever your team reads it. The pages on the 123FormBuilder Make integration and the 2Chat Make integration show what those first modules can look like.
Enrich records before they land in your stack. When a row or contact arrives from another app, Run Agent can process it and hand its output to the module that writes the record, so the enriched version is the one people see.
Run the same agent on a schedule. A scenario can also start on its own clock, every 15 minutes by default, and call Run Agent each time without any trigger from another app.
What Make does not do here: there is no PromptLayer trigger and no Make an API Call module, so everything beyond running an agent stays inside PromptLayer. The Make documentation for this app also warns that it was generated with AI and may contain mistakes, so check anything important against PromptLayer. If you are weighing tools, the n8n vs Make comparison lays out the criteria.
How do you connect PromptLayer to Make?
- 01
Copy your PromptLayer API key
Log in to PromptLayer and open the account menu in the top right corner. Click Settings, go to the API section and copy the key shown there. You need an active PromptLayer account for this.
- 02
Add the module and create the connection
In your scenario, add the Run Agent module and click Create a connection. A connection is your PromptLayer account linked to Make once, then reused by every PromptLayer module you add later.
- 03
Name it and paste the key
The Connection name field is optional, but a clear name helps when you manage several accounts. Paste the API key you copied, or follow the instructions on screen, and save.
Your first scenario with PromptLayer
GoalWhen a new entry arrives in another app, Make runs your PromptLayer agent on it.
- 01
Create the scenario
Open the Scenarios page, create a new scenario and click the + to add the first module. Since PromptLayer has no trigger, pick the app where your data starts, for example your form tool.
- 02
Add Run Agent
Click the + on the right of that first module, search for PromptLayer and choose Run Agent. Click Create a connection if you have not linked your account yet.
- 03
Map the incoming data
Fill the module fields and map data from the first module into them. Each item passing between modules is a bundle: one form entry, one message, one row.
- 04
Test with Run once
Click Run once to execute the scenario one time. Then read the bundles each module received to check what your agent returned.
- 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 on one bundle counts as one operation on your Make plan.
What the PromptLayer module does in Make
PromptLayer gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.
Run Agent
ActionIn Make“Run an Agent in PromptLayer”
You get your PromptLayer agent working inside a scenario: Run Agent starts an agent from your account and makes its result available to the modules that come after it.
Need help automating PromptLayer with Make?
A person reads every message.
