AIOps SRE
Search

Make · cloud scenario automation platform

Make AI Agent (New)

Official documentation

Make AI Agent (New) places agent work inside a cloud automation scenario. Configure instructions, a provider, knowledge, inputs and tools, then test the agent as part of that scenario. Tools can include modules, scenarios, MCP connections and other agents. The useful design choice is where judgment is needed: Make distinguishes agents for variable decisions, AI modules for bounded transformations and ordinary scenarios for fixed logic. A known rule often needs the latter rather than an agent. Current documentation labels the new app open beta, so functionality and pricing can change. Make's provider is available across plans, while custom provider connections require paid access. Start with synthetic inputs and inspect the actions and result before turning a scenario into recurring work.

Product profileDocumentation checked

AutomationAgents

In this profile

When it fits

Useful for

  • Adding a judgment step to a visual cloud automation scenario
  • Choosing among fixed logic, a bounded AI transformation and an agent inside one platform

Limits to consider

  • Adding an agent where the rule is already known and explicit
  • Assuming open-beta behavior or pricing will remain fixed

Capabilities and platforms

  • Agents accept configured instructions, provider, knowledge and scenario inputs
  • Agent tools can use modules, scenarios, MCP connections and other agents
  • Ordinary scenarios and AI modules provide alternatives to agent reasoning for fixed or bounded work

Where it runs

  • Cloud platform

Access and setup

Make account; the documented Make provider spans plans, while custom provider connections require paid plans. New-agent functionality and pricing remain subject to beta changes.

Current access and pricing
  1. Open the current Make AI Agent (New) documentation and check beta availability and provider access for the account.
  2. Configure instructions and a small synthetic input, selecting only the modules or scenarios required as tools.
  3. Test the agent inside a scenario and inspect its proposed actions and output; keep fixed rules in explicit scenario logic.

Proposed exercise · not hands-on tested

Draft an internal inquiry route

Input

Synthetic inquiries and a known set of destinations, including an unresolved option.

  1. Keep explicit eligibility rules in the scenario and send only the variable classification question to the agent.
  2. Have the agent return a destination suggestion with the reason and unknown cases preserved.
  3. Inspect the scenario test result and action history before connecting an external send or enabling a repeat trigger.

Artifact to inspect

A routing draft with fixed rules separated from judgment.

What to verify

As an unexecuted exercise, success remains to be established: compare suggestions with the known labels and inspect whether any tool exceeded its assigned role.

Data handling and permissions

Make scenarios run in the cloud, and their connected services and model providers determine additional data destinations. A custom-provider connection changes the processing path, rather than making the scenario local. Review what each module, tool and provider receives before passing internal records through an agent. The open-beta and provider-access descriptions do not establish a blanket training, retention or compliance guarantee. Check current terms, connection permissions and scenario records for the account being used. The proposed routing exercise uses synthetic inquiries so its result can be evaluated before real messages or customer material enter the workflow. Keep publishing and recurring execution separate from inspecting a draft.

Other options

n8n
Consider it when self-hosting or more explicit technical operation matters.
Zapier Agents / AI by Zapier
Compare for agentic tool use alongside ordinary Zap steps.

Sources and scope

Documentation-based product profile; no hands-on testing. The proposed workflow is an authored exercise, not a verified outcome or a practical guide. Capabilities and policy statements describe vendor documentation checked October 2, 2026; task-fit comparisons are editorial judgments. Plan, region, administrator and interface limits may apply.

Source review: . Product access and terms can change.

Suggest a correction