cenkertekQ: Jivochat
I couldn't find jivochat under the integrations.
You replied to another question regardin dataforseo as follows „ A: You’re not limited to just those three DataForSEO calls — we only shipped the most common ones as first-class MCP actions, but you can absolutely hit any DataForSEO endpoint via our HTTP Request node (or by configuring a custom MCP server) and parse the JSON yourself“
Is it possible to connect jivochat the same way with http request node or custom mcp server at the time being.
SeanP_AgenticFlowAI
Apr 29, 2025A: Hey Cenkertek,
That's a great question, and yes, the same principle applies to Jivochat as it did to DataForSEO.
Jivochat MCP: You're correct, we do not have a specific, pre-built Jivochat MCP listed currently.
Connecting via API Call Node: If Jivochat offers a public API (Application Programming Interface), you can absolutely connect to it using our generic API Call node within an AgenticFlow Workflow.
You would need to check Jivochat's developer documentation to find their API endpoints, understand how their authentication works (e.g., API keys), and know what data format they expect/return.
Then, you would configure the API Call node in your workflow with the correct Jivochat URL, HTTP method (GET, POST, etc.), add your authentication details in the Headers, and structure any necessary data in the Body.
Custom MCP Server: Creating a custom MCP server is also technically possible but is a much more advanced option. It involves building and hosting your own intermediary server that speaks the MCP protocol (https://modelcontextprotocol.io/) on one side and makes the necessary Jivochat API calls on the other. This requires development effort outside of AgenticFlow.
Recommendation: The most practical method right now (assuming Jivochat has an API) is using the API Call node within a workflow. For easier, no-code integration in the future, please feel free to request or vote for a dedicated Jivochat MCP on our public roadmap: https://agenticflow.featurebase.app/
So, while it's not a one-click MCP integration today, connecting via their API using our workflow builder's API Call node is the way to go if they provide API access.