Qyvo
Log inStart for free

Connect n8n

Use the n8n-nodes-qyvo community node, or wire the MCP Client node directly. Both are supported.

n8n offers two ways to use Qyvo: the community node (recommended), or the generic MCP Client node pointed at qyvo.io/mcp.

Option A — Community node (recommended)

n8n-nodes-qyvo is the official Qyvo community node, approved on n8n 2026-05-06. It exposes triggers and actions as native n8n nodes, with field-level dropdowns (template picker, tag picker, contact picker) — much friendlier than raw MCP for visual workflows.

The action node is usableAsTool: true, so you can chain it under n8n's AI Agent node directly. The agent treats each action as a tool, no MCP wiring needed.

Install

  1. Settings → Community Nodes in n8n
  2. Click Install a community node
  3. Enter n8n-nodes-qyvo
  4. Confirm — n8n downloads from npm, restarts the worker, and the Qyvo nodes appear in the editor

If your n8n is locked down (cloud plan without community nodes, or self-hosted with N8N_COMMUNITY_PACKAGES_ENABLED=false), use Option B.

Configure credentials

The first time you drop a Qyvo node onto a canvas, n8n asks for credentials:

  • Name — anything (e.g. Qyvo prod)
  • API token — paste your Qyvo Personal Access Token

The community node uses the same /api/v1/* REST endpoints documented under REST API — same auth, same scope.

Use under the AI Agent

Drop an AI Agent node, then add a Qyvo Action node as a tool. The agent reads the action's description and invokes it autonomously based on the conversation. Any LLM provider supported by n8n (OpenAI, Anthropic, Mistral, local) works.

Option B — Generic MCP Client node

n8n ships an MCP Client node that speaks raw MCP over HTTP. Point it at Qyvo:

  • Server URL — https://www.qyvo.io/mcp
  • Auth header — Authorization: Bearer YOUR_TOKEN_HERE

This gives you the full 35-tool catalogue (richer than the community node, which exposes the most common 15 actions). Use this when you want every MCP tool — create_segment, import_contacts, etc.

When to use which

Scenario Pick
Visual workflow, want field dropdowns Community node
AI Agent that should drive Qyvo conversationally Community node (each action is usableAsTool)
Need every MCP tool (including segments, imports, analytics) MCP Client node
Self-hosted with no community packages allowed MCP Client node

Polling triggers

The community node also exposes the four trigger nodes built on top of /api/v1/triggers/*:

  • New Message Received
  • New Campaign Sent
  • New Flow Triggered
  • New Sequence Triggered

They poll on a schedule (default 1 min) and de-duplicate by id. Use a webhook (see Webhooks) instead if you need real-time delivery.