seamless

n8n community nodes for Seamless

Package Information

Released: this month
Downloads: 271 weekly / 1,593 monthly
Latest Version: 0.6.21
Author: Seamless Engineering

Documentation

n8n-nodes-seamless

Seamless.ai community nodes for n8n — search contacts, enrich leads, run campaigns, and automate your sales pipeline.

npm version
License: MIT
n8n community

Compatibility

Requirement Version
n8n >= 1.71.0
n8n-workflow >= 1.120.0
Node.js >= 20

Nodes

Seamless

Full REST API node for managing Seamless.ai resources:

  • Contact — Search, research, get, and poll contacts
  • Company — Search, research, get, and poll companies
  • Campaign — Create, update, clone, manage contacts, and execute actions
  • Campaign Step — Create, update, delete, and execute campaign steps
  • List — Create, get, update, and delete lists
  • Saved Search — Create, get, update, and delete saved searches
  • Template — Create, get, update, and delete email templates
  • Email — Create drafts, send, preview, and send bulk emails
  • Task — Create, get, update, delete, and execute task actions
  • Call — Log and retrieve calls
  • Activity — Retrieve engagement activity events
  • Email Account — Manage email accounts
  • Credits — Check credit balance
  • Email Footer — Retrieve email footers

This node is also usable as an AI tool in n8n's AI agent workflows.

Seamless Trigger

Polling trigger node that watches for new events:

  • Activity Event — Triggers on new engagement activity
  • Company Researched — Triggers when a company research completes
  • Contact Researched — Triggers when a contact research completes

Installation

From npm (recommended)

In your n8n instance, go to Settings > Community Nodes and install:

@seamless-oss/n8n-nodes-seamless

Local development

git clone https://github.com/SeamlessAI/n8n-nodes-seamless.git
cd n8n-nodes-seamless
npm install
npm run dev   # Starts local n8n with the node loaded at localhost:5678

Credentials

Two authentication methods are supported:

OAuth2 (recommended)

Select OAuth2 in the node's Authentication dropdown and follow n8n's standard OAuth2 flow to connect your Seamless.ai account — no manual key management required.

API Key

Select API Key in the node's Authentication dropdown, then create Seamless API credentials and provide:

Field Description
MCP Server URL The Seamless MCP endpoint (defaults to https://mcp.seamless.ai/mcp)
API Key Your Seamless.ai API key

You can find your API key in the Seamless.ai app under Settings > Integrations > API.

Usage example

  1. Add the Seamless node to your workflow.
  2. Select a Resource (e.g. Contact) and an Operation (e.g. Search).
  3. Fill in the required fields and any optional filters.
  4. Execute the workflow to retrieve data from Seamless.ai.

For trigger-based workflows, add the Seamless Trigger node and choose the event type to poll for.

Contributing

Contributions are welcome! Please open an issue or submit a pull request.

  1. Fork the repository
  2. Create your feature branch (git checkout -b feature/my-feature)
  3. Run linting: npm run lint
  4. Commit your changes (git commit -m 'feat: add my feature')
  5. Push to the branch (git push origin feature/my-feature)
  6. Open a Pull Request

Known lint issue: repo checked out directly under /

If the repo lives in a directory whose parent is the filesystem root (e.g. /workspace, the default for Cursor Cloud Agents), npm run lint reports four false @n8n/community-nodes/no-credential-reuse errors claiming seamlessApi / seamlessOAuth2Api are not defined in this package. This is an upstream bug in @n8n/eslint-plugin-community-nodes: its findPackageJson loop stops before checking package.json in a top-level directory, so the rule never sees the credentials list. The code is fine; lint from any deeper path instead:

git worktree add /tmp/lint-wt HEAD
ln -s "$PWD/node_modules" /tmp/lint-wt/node_modules
(cd /tmp/lint-wt && npm run lint)
git worktree remove --force /tmp/lint-wt

Publishing

This package is published to npm via a GitHub Actions workflow with provenance, triggered by pushing a version tag:

  1. Update version in package.json
  2. Commit: chore: release vX.Y.Z
  3. Tag: git tag vX.Y.Z
  4. Push: git push origin vX.Y.Z

Support

Changelog

See GitHub Releases for version history.

License

MIT

Discussion