A: Hey Christian814,

That's a really smart idea – combining the AI agent orchestration of AgenticFlow with the RPA capabilities of RoboMotion could be incredibly powerful!

RoboMotion MCP Connector:

- Currently, we do not have a dedicated, pre-built MCP connector specifically for RoboMotion.
- Your Best Next Step: Please submit this as a feature request (or vote for it if it's already there) on our public roadmap: https://agenticflow.featurebase.app/. We prioritize building new MCPs based heavily on community demand, so your vote definitely helps!

Alternative Ways to Make This Work (Now or Soon):

- API Call Node (If RoboMotion has an API): If RoboMotion offers a REST API that allows you to trigger RPA bots or pass data, you can use AgenticFlow's API Call node within a workflow or have an agent use it. You'd configure this node with RoboMotion's API details.
- Webhook Trigger (If RoboMotion can send webhooks): If RoboMotion can send a webhook when one of its RPA tasks completes, you could potentially trigger an AgenticFlow workflow via our API endpoint to process the results. (A native webhook trigger node is on our roadmap).
- MCP in Workflows (Coming ETA Next Week): Once our "MCPs in Workflows" feature is live (https://agenticflow.featurebase.app/p/use-2500-mcp-as-nodes-in-workflow), if there's a more generic "RPA orchestrator" MCP or even if RoboMotion gets its own community-built MCP server, you could integrate it more seamlessly.

- Custom MCP Server: For a really tight integration, a developer could potentially build a custom MCP server that acts as a bridge between AgenticFlow and RoboMotion's API (if available).

For now, the API Call node is likely your most immediate path if RoboMotion has an API. Definitely get RoboMotion onto the roadmap as an MCP request – it's a great suggestion for combining AI and RPA!

Thanks!
— Sean