paperclip

n8n community node for managing Paperclip companies, agents, issues, approvals, and heartbeats

Package Information

Released: 2 mo ago
Downloads: 0 weekly / 0 monthly
Latest Version: 0.1.1

Available Nodes

Documentation generating…

Paperclip icon
Paperclip
Interact with the Paperclip API

Documentation

n8n-nodes-paperclip

This is an n8n community node for Paperclip, the open-source
control plane for teams of AI agents. It lets n8n workflows create and monitor work,
control agents, and handle governance approvals through the Paperclip JSON API.

The node can also be used as an n8n AI Agent tool.

n8n is a fair-code licensed workflow automation platform.

Installation

Follow the installation guide
in the n8n community nodes documentation and install n8n-nodes-paperclip.

Operations

Agent

  • Get one, get many, or get the current authenticated agent
  • Invoke a heartbeat
  • Pause or resume an agent
  • Clear an agent error

Approval

  • Get one or get many approvals
  • Approve or reject a request
  • Request a revision

Company

  • Create, get, list, or archive companies

Health

  • Check the Paperclip server and database health

Issue

  • Create, get, list, or update issues
  • Filter issues by status, assignee, or project
  • Add Markdown comments

Credentials

Create a Paperclip API credential with:

  • Instance URL: the URL of your Paperclip deployment without /api, for example
    https://paperclip.example.com
  • API Token: a Paperclip board API token or agent API key

Paperclip sends the token as Authorization: Bearer <token>. See the
Paperclip API authentication documentation.

Compatibility

Tested with n8n 2.32.5 and Node.js 22.23.1.

Usage

Most Paperclip API operations are scoped to a company. Copy the company ID from the
Paperclip UI or use Company → Get Many. A common automation is:

  1. Receive work through an n8n trigger.
  2. Create a Paperclip issue and assign an agent.
  3. Invoke the agent heartbeat.
  4. Poll the issue or react to a Paperclip-originated webhook.
  5. Continue the n8n workflow when the issue reaches done.

Issue updates follow Paperclip lifecycle rules. In particular, moving work to
in_progress can require Paperclip's atomic checkout flow.

Resources

Version history

0.1.0

Initial community release with Health, Company, Agent, Issue, and Approval resources.

Discussion