n8n-nodes-wordsmith

n8n community node for Wordsmith AI, the legal AI assistant for lawyers.

Use this node to send questions, attach files, continue conversations, and retrieve generated documents from Wordsmith — all from inside your n8n workflows.

Installation ·
Operations ·
Credentials ·
Compatibility ·
Usage ·
Resources

Installation

Follow the community nodes installation guide in the n8n docs and install n8n-nodes-wordsmith.

For self-hosted n8n instances, you can also install manually:

npm install n8n-nodes-wordsmith

Operations

Resource: Question

• Ask — Send a question to a Wordsmith assistant. Supports:
  • Wait for Answer (sync mode) — wait synchronously for the complete answer (recommended for n8n).
  • Session ID — continue an existing conversation.
  • Visibility — private, organization, or public.
  • Callback URL — async webhook notification when the question completes.
  • Attachments — one or more files attached by public URL or upload job ID, with optional ZIP unzip.
• Get Status — Retrieve the status, answer, and any generated attachments for a previously asked question. Useful for polling async questions.

Resource: Assistant

• Get Many — List the assistants (workspaces) that you have access to. The same endpoint also powers the assistant dropdown when asking a question.

Credentials

You need a Wordsmith API key.

1. Sign in at app.wordsmith.ai and open Settings → API Keys.
2. Generate a new API key.
3. In n8n, create new Wordsmith API credentials and paste the key.

The credentials also let you select the environment:

• Production (default) — https://api.wordsmith.ai
• Staging — https://staging.api.wordsmith.ai
• Custom — provide your own base URL (useful for local development or self-hosted deployments).

n8n will verify the credentials by calling the GET /api/v1/me endpoint when you save them.

Compatibility

• Requires n8n 1.x with the community-nodes API version 1 contract.
• Tested against Node.js 22+.

Usage

Quick start: synchronous "Ask Wordsmith"

1. Add a Wordsmith node to your workflow.
2. Select Resource: Question and Operation: Ask.
3. Pick an assistant from the dropdown (or leave it on default).
4. Type your question and (optionally) attach files via URL.
5. Make sure Wait for Answer is on — the node will return the full answer, attachments, session_id, and session_url in one step.

Async + webhook pattern

For long-running questions (large documents, deep research) consider using async mode:

1. Turn Wait for Answer off.
2. Either:
   • Provide a Callback URL (e.g. an n8n Webhook trigger) — Wordsmith will POST the final result to it when ready, or
   • Save the returned id, then use a follow-up Get Status operation to poll until status is completed or error.

Multi-turn conversations

To continue a conversation, pass the session_id returned from a previous Ask call into the next Ask call's Session ID field. Wordsmith preserves context across questions in the same session.

Using attachments

You can attach files to a question either by:

• Public URL — any HTTPS-accessible file (n8n can pull files from S3, Drive, etc. and upload them somewhere reachable, or use signed URLs).
• Upload Job ID — first call the Wordsmith file upload endpoint to obtain an upload_job_id, then reference it here.

Toggle Unzip to have Wordsmith automatically expand ZIP archives server-side.

Resources

• Wordsmith API documentation
• Create Assistant Question reference
• Get Question Status reference
• List Assistants reference
• n8n community nodes docs

Publishing (maintainers)

This package lives inside the wordsmith monorepo (like zapier/wordsmith/), so we don't use the n8n CLI's release-it-based release flow (which assumes each node has its own GitHub repo, and stages git commits + tags automatically).

Instead, version bumps land directly in package.json as part of normal monorepo PRs, and publishing is a single command:

# Local first publish / re-publish at current version
./deploy.zsh --otp <6-digit-code>

# Bump version and publish
./deploy.zsh --bump patch --otp <6-digit-code>     # 0.1.0 -> 0.1.1
./deploy.zsh --bump minor --otp <6-digit-code>     # 0.1.0 -> 0.2.0
./deploy.zsh --bump major --otp <6-digit-code>     # 0.1.0 -> 1.0.0

# Dry run (lint + build + version bump, no publish — no OTP needed)
./deploy.zsh --bump minor --dry-run

The --otp value is the current 6-digit code from your authenticator app. The npm registry requires this for any account with 2FA enabled (mandatory for most accounts since 2023), and the modern npm CLI doesn't reliably prompt for it from inside a script — so we pass it explicitly. Codes rotate every 30 seconds, so generate yours right before running the command.

The script:

1. Installs deps (pnpm install --frozen-lockfile)
2. Runs n8n's strict-mode linter (pnpm lint)
3. Builds (pnpm build)
4. Optionally bumps the version (with npm version <bump> --no-git-tag-version — no git tag is created, since the monorepo's release tags are managed separately)
5. Publishes to npm via npm publish --access public. When run from CI (CI=true, e.g. GitHub Actions), it also passes --provenance to attach an OIDC-signed attestation, which n8n Cloud requires for verified nodes.

If you've never published before, run npm login first.

Version history

• 0.1.0 — Initial release. Question (Ask, Get Status) and Assistant (Get Many) operations, plus dynamic assistant lookup.