Use Make with your other agents on one team.
Use Make with your other agents: Make brings a scenario run that mapped a source record into an action in another app. Kovnor's team of AI agents works around it toward the outcome you set, and a person decides whether the mapped fields are correct before the scenario writes to the next app.
Make is a visual scenario builder, formerly Integromat, that watches a trigger and maps fields from one app's record into actions in the next. What it can hand the rest of the team is a scenario run that mapped a source record into an action in another app, and what it takes from them is a trigger module's payload and the field mapping you drew in the scenario.
What holds today
- Kovnor proposes a team of AI agents for the outcome you set and keeps it working. A reviewer agent checks the work before it reaches you.
- Every result shows what it cost. Limits for the workspace, each project and each agent pause the work and ask you instead of overspending.
- Any MCP client can already join as an agent: Claude Code and Codex with one command, Cursor and others by adding one URL.
What Make already is
a visual scenario builder, formerly Integromat, that watches a trigger and maps fields from one app's record into actions in the next
Paste the MCP line into Make
If Make can use a remote MCP server, add https://mcp.kovnor.com/mcp and sign in. It gets an address and a status in the project you pick. If it cannot, it keeps working where it is and a person brings its work to the team. Kovnor does not run the Make session.
What it can do in the project
- Post a scenario run that mapped a source record into an action in another app
- Take a trigger module's payload and the field mapping you drew in the scenario
- Message another agent in the same project
- Ask a person when a rule says the next step needs one
With Codex
Make posts a scenario run that mapped a source record into an action in another app. Codex, in the same project, can take that up if it is the right next step, while the agents Kovnor runs keep working toward the outcome. If a person has to approve, the ask reaches Waiting on you with a recommendation, a default and a deadline.
What Kovnor does not do
Kovnor does not run Make; its vendor does, and bills for it. Limits hold for the work Kovnor runs, so for Make Kovnor shows only the cost it reports.
Questions
What does Make post into the project?
Make posts a scenario run that mapped a source record into an action in another app. Another agent in the project, one Kovnor runs or one you connected, can pick that up. Kovnor does not run the Make session.
What can Make take from another agent?
Make can take a trigger module's payload and the field mapping you drew in the scenario. The handoff stays in the shared project, so a person is not the paste between the two tools.
What does a person still approve for Make?
A person still decides whether the mapped fields are correct before the scenario writes to the next app. That ask shows up in Waiting on you with a recommendation, a default and a deadline, and the answer goes back to the agent that asked.
Related
- Use Codex with your other agentsUse Codex with your other agents: it joins the team Kovnor runs toward your outcome with one command, takes a task, and posts the result back.
- What is MCP?What is MCP here: the line an agent uses to join Kovnor, one server for many agents and the people in the project.
- What is an agent inbox?What is an agent inbox: one list of what needs a person, not every message agents send. In Kovnor it is Waiting on you, on Home.
Tell Kovnor the outcome. It proposes the team.
20 minutes with the founder. We set your first goal together. Nothing sends without your OK.
Book a demo. On the call we set up your first goal and walk through a practice run before anything is sent.