Paperclip AI Integrations: n8n, Slack, Telegram, Linear, OpenRouter & MCP

Paperclip AI integrations are what turn a dashboard full of agents into something your business actually feels. On its own, Paperclip is a control plane: org chart, tickets, budgets, audit log. It becomes useful when tickets come from your issue tracker, results land in your Slack, and agents can reach your data through n8n or MCP tools. This guide covers each integration that matters as of September 2026, how it connects, and which business need it solves. If you have not yet met the core concepts, our Paperclip AI guide is the place to start.

Two kinds of integration

It helps to separate the integrations into two groups, because they connect in opposite directions.

• Adapters connect an agent runtime to Paperclip. Paperclip sends the heartbeat, the runtime does the work. Claude Code, OpenClaw, Hermes and the generic HTTP adapter are all in this group.
• Plugins and connectors connect outside services to Paperclip. They push tickets in, mirror status out, send notifications, or supply models. Linear, Slack, Telegram and OpenRouter are here.

n8n is the interesting case because it can sit on either side.

n8n: worker or caller

n8n is the open-source workflow automation tool we use most at Neon Digital Media, and it pairs with Paperclip in two distinct ways.

n8n as a Paperclip employee

Paperclip's HTTP/webhook adapter treats any endpoint that can receive a heartbeat as an agent. Point it at an n8n webhook trigger, and that workflow becomes an employee. Paperclip sends the ticket payload, the workflow runs whatever nodes you built (an LLM node, a database lookup, an email send), and returns a result. There is no custom code involved; you paste the webhook URL into the agent configuration. This is the right shape for deterministic jobs that do not need an autonomous agent: nightly data pulls, invoice generation, report formatting. They get budgets, tickets and the audit trail like every other employee.

n8n calling Paperclip

Paperclip exposes a REST API (the docs list roughly thirty reference pages for it). An n8n workflow can create tickets, assign them to roles, poll status and read results. That is how you feed Paperclip from systems it has no plugin for: a form submission creates a ticket for the Research Analyst, a Stripe refund event creates a ticket for the Support Specialist, and so on. A community n8n template on the n8n workflow library does exactly this, creating, assigning and tracking Paperclip tasks from external events.

Most real deployments use both. n8n feeds tickets in from the outside world and also serves as a cheap deterministic worker inside the org chart.

Linear: bidirectional issue sync

The Linear plugin mirrors Paperclip tickets into Linear issues and back. Create an issue in Linear and it appears as a ticket for the mapped role. An agent's comments and status changes flow back into Linear, so a human team that already lives in Linear can supervise agents without opening the Paperclip dashboard. Status mirroring means a ticket moving to review in Paperclip moves the Linear issue to the matching state. For development companies using the Claude Code integration, this is usually the first plugin installed.

Slack and Telegram: notifications and approvals

The Slack and Telegram plugins post to a channel when a ticket is created, when it completes, and when it needs approval. The approval notification is the one that matters. Paperclip's governance model puts a human in the loop for anything sensitive, and that only works if the human sees the request quickly. A Telegram message with the ticket summary and a link to approve is the difference between an agent company that flows and one that stalls every night waiting for you to open a dashboard.

Do not confuse these notification plugins with OpenClaw's messaging channels. The plugins tell you what your agents are doing. OpenClaw's channels let an agent talk to customers. Our OpenClaw integration guide covers the customer-facing side.

OpenRouter: one key, many models

OpenRouter is a model provider aggregator. Its value inside Paperclip is that harnesses like OpenCode can be pointed at any model behind a single key, which makes it easy to give cheap roles cheap models and expensive roles expensive ones without managing six provider accounts. The official test drive shows the pattern:

OPENROUTER_API_KEY=... npx paperclipai test-drive --harness opencode --model openrouter/anthropic/claude-sonnet-4.5

Paperclip's cost tracking breaks spend down by provider and model, so you can see exactly which OpenRouter model each role is consuming and adjust budgets accordingly.

MCP tools inside agents

Model Context Protocol servers give agents structured access to external systems: a database, a CRM, a file store, an internal API. Paperclip does not host MCP servers itself. Each agent runtime (Claude Code, OpenClaw, Hermes) loads MCP tools in its own configuration, and Paperclip records every tool call in the ticket's trace. The practical workflow is: build or install the MCP server, configure it in the runtime, then restrict which roles may use it through the role's permissions in Paperclip. That way a Research Analyst can read the CRM through MCP while the Content Repurposer cannot.

The community list

The awesome-paperclip repository on GitHub (gsxdsm/awesome-paperclip) maintains a curated list of plugins, adapters, company templates and tooling built by the community. Paperclip's plugin system runs plugins as out-of-process workers with capability-gated access to host services, so a third-party plugin cannot silently read your secrets. Still, review anything you install; the audit log will tell you what it touched. Company templates and the emerging ClipMart marketplace are covered in our use cases and templates post.

Which integration solves which need

Business need	Integration	Direction
Feed tickets from forms, payments, CRM events	n8n calling the Paperclip API	In
Run deterministic jobs with budgets and audit	n8n as HTTP/webhook employee	Adapter
Let the human team supervise from their issue tracker	Linear plugin	Both
Approve sensitive actions from your phone	Telegram or Slack plugin	Out
Control model cost per role	OpenRouter with OpenCode harness	Provider
Give agents safe access to internal data	MCP servers in the runtime, permissions in Paperclip	Tool
Talk to customers on WhatsApp or Telegram	OpenClaw adapter	Adapter
Improve at repetitive work over time	Hermes adapter	Adapter

A sensible setup order

1. Install Paperclip and one adapter. Confirm a ticket runs end to end. Our install guide covers this.
2. Add the Telegram or Slack plugin so approvals reach you.
3. Add Linear if your team already uses it. If not, skip it.
4. Build one n8n inbound workflow that creates tickets from your highest-volume trigger.
5. Add MCP tools to specific roles only when a ticket type clearly needs data the agent cannot otherwise reach.

Each step adds a place where something can break. Doing them in this order means every failure has one obvious suspect.

Security notes for every integration

Every connector above needs a credential, and every credential belongs in Paperclip's encrypted secrets store rather than in a job description, a ticket or an n8n node's plain-text field. Grant secrets to roles, not to the whole company, so a compromised or misbehaving agent cannot reach systems its job does not require. Keep Paperclip, n8n and any OpenClaw or Hermes instances on a private network, and expose only the notification plugins' outbound connections to the public internet. Finally, read the audit log for the first week after adding any integration; it is the quickest way to spot a plugin or workflow touching more than you expected.

Frequently asked questions

Does Paperclip have a native n8n plugin?

As of September 2026 the connection is through Paperclip's HTTP/webhook adapter and REST API, plus community-built n8n templates. There is an open request in the Paperclip repository to list n8n-based agents in the official integrations directory.

Can Slack be an agent channel as well as a notification channel?

Notifications come from the Slack plugin. If you want an agent that answers people in Slack, use an OpenClaw employee connected to Slack. They are separate integrations doing separate jobs.

Does the Linear plugin require Linear's paid plan?

It uses Linear's API, which is available on Linear's standard plans. Check Linear's current terms for API access limits.

Where do MCP servers run?

Inside each agent runtime's own configuration, not in Paperclip. Paperclip logs the tool calls and controls which roles may use which skills.

Which integration should I set up first?

A notification plugin, so approval requests reach you. Everything else depends on you responding to those.