Managed AI Agent

Managed AI Agent is an autonomous loop after the work is known — usually On Call End. It is not AI Response to Caller. It will not talk on the line.

Why this node

File the ticket, update the CRM, write the follow-up — a short tool loop with a cost cap. One HTTP call is still Connect To External Service. One completion is AI Response Generation.

What you configure

TaskREQUIRED

What the loop must finish. Seeded so a fresh card is not empty.

Built-in tools / API tools / MCP

What it may call. Runtime expects at least one tool.

Models

Primary (seeded). Optional escalation on the same provider.

Limits

Max iterations (default 15, 0 = no iteration cap) and max cost (USD, max 0.5). Stuck detection bails if the same tool+args fire twice.

Knowledge

Optional files + rerank. Same idea as the agent knowledge attach.

Dry run is on the node — use it while you test. Ports: Task completed, Task failed.

First setup — after hang-up, create a ticket

1. Connect the CRM on Integrations if the loop will write there.

2. On Call End → Managed AI Agent. Task: open a ticket from the call summary. Add the HubSpot (or API) tool it needs.

3. Leave limits at the seed. Save & go live, attach, hang up one call. Check the CRM — if nothing landed, no tool was added, HubSpot is disconnected, or dry run is on.

What “broken” looks like

• Needs setup — empty Task.
• Loop stops early — cost / iteration cap, or stuck detection.
• Mid-call silence — this node is on During Call.

Troubleshooting

Why not just chain API + Email?

Do that when the steps are fixed. Use this node when the set of writes depends on what happened on the call and you accept a capped loop.

Next Steps

On Call End.→HubSpot nodes — a single deterministic write.→AI Response Generation.→