External Web Request, MCP, or Power Automate?
The question to use either Web Requests, MCP Servers or the Power Automate Connector needs to be judged based on your use case. The following table is meant to give you a guideline.
| Integration method | Primary Benefit | Timing sensitivity1 | Flexibility | Administrative effort |
|---|---|---|---|---|
| 🌐Web Requests | Lightweight, direct API calls from Nimbus to external systems. Usable in Virtual User orchestrating AI tools, e.g. CRM lookup, routing decisions, priority setting. | ▲ High – designed to be executed inline during call handling and workflow execution. Executed at exactly the point when the workflow reaches the Web Request activity. | ▼ Low – simple, text-based request/response handling into external CRM systems with limited parsing and transformation. | ▲ Simple – configured directly in Nimbus with minimal dependencies. Debugging usually clear via simple response codes. |
| 🧠MCP (Model Context Protocol) | Flexible Orchestration of AI tools, knowledge, and assistive capabilities within the Nimbus AI framework. Can be easily incorporated into the Nimbus configuration experience. | ► Medium – suitable for AI-driven interactions, but not primarily optimized for hard real-time call control. Timing depends on the complexity of the connected tools and the speed on which the AI can formulate an answer. | ▲ High – supports rich, structured context and complex AI interactions. Can onboard new capabilities with ease by adjusting AI instructions in Nimbus. | ► Advanced – requires AI knowledge, MCP server management knowledge. Harder to troubleshoot, as the LLM system operates mostly “black box” without extensive logging or debugging tools. |
| 🔁Power Automate | Complex integrations, multi-step workflows, and asynchronous or post-call automation. Suitable for standardized data query and optimization tasks prior to returning the data. | ▼ Low – dependent on Trigger Event during ongoing tasks. A long chain of actions and integrations may cause delays in response. Can work in parallel during a Workflow, but not suitable for time-critical tasks, during calls. | ▲ High – advanced data manipulation, conditions, branching, and connector support to various systems. Allows direct control over in- and outputs. | ▼ Substantial – involves knowledge about flow design, permission management, connector maintenance to ensure 3rd party integration connectivity. |
1💡Good to know: As part of the “Wait for Parameter” Check Activities, Nimbus is able to wait for external integrations until Parameters have been updated, only then continue with the workflow. However this also means your workflow might be delayed by long-running, failed or timed-out operations.