LiveAgent previously supported triggering FlowHunt flows from rules using the generic HTTP request action (see Triggering FlowHunt AI agents via rules). The AI Agents feature is the recommended replacement for that approach and offers several important improvements:
| Capability | HTTP request action (legacy) | AI Agents |
|---|---|---|
| Setup complexity | Requires manually constructing the FlowHunt API URL, headers, and JSON body in every rule | Configure once in a named AI agent; reference by name in any rule |
| Reusability | Each rule requires its own complete HTTP action configuration | One agent can be reused across unlimited rules |
| Execution visibility | No built-in visibility into whether the flow ran, what it did, or whether it succeeded | Full run log with status, duration, tool call count, and failure reasons |
| Throttle handling | Rate-limit errors are not retried; the execution is silently lost | Throttled runs pause automatically and resume when the rate limit clears |
| Tool access control | The flow has no action restrictions imposed by LiveAgent | Each agent explicitly limits which actions the AI may take on a ticket |
| Budget protection | No centralized limits; runaway flows can cause unbounded tool usage | Monthly credit budgets protect against runaway runs |
| Authentication management | API keys are embedded directly in rule action fields as plain text | Tokens are managed centrally, scoped per agent, and revoked automatically when an agent is deleted |
Related articles
- AI Agents feature overview
- Triggering FlowHunt AI agents via rules (legacy)
- Setting up AI Agents feature via FlowHunt