KonbiniAPI

Automation clients with live social data.

Put a KonbiniAPI call inside a scheduled workflow, so a recurring report or alert runs without anyone starting it.

All of them reach the same hosted MCP server, the same endpoints, and the same credits as the REST API. What differs is where the URL goes and what each one asks for when you authorize.

What you can connect.

Each has a tested setup guide. Follow it once — the cards below are the short version — and the tools appear in the client.

  • Zapier

    Setup
    Apps → Add connection → MCP Client, over Streamable HTTP. Then pick a KonbiniAPI tool inside a Zap and map its inputs.
    Auth
    OAuth or API key
    Notes
    Zapier lists MCP Client as beta.
  • n8n

    Setup
    The MCP Client node when you want tools as ordinary workflow steps, or MCP Client Tool to hand them to an n8n AI Agent.
    Auth
    OAuth2 or API key
  • Make

    Setup
    The MCP Client module in a scenario. Make loads the tool list itself, so you pick a tool and map inputs in the UI.
    Auth
    OAuth or API key
  • Pipedream

    Setup
    Point an MCP-aware workflow at the server URL, load the tool list, and call the typed tool you need.
    Auth
    OAuth or API key

Step-by-step guides.

For the jobs where the client changes how the work is done.

Connect a automation client.

One API key works for MCP and the REST API. The free plan includes 100 credits and no credit card.