n8n-nodes-logit

n8n community node for Logit — send workflow events to Logit channels from your automations, with the same concepts as the Logit TypeScript SDK (logit on npm).

Installation · Operations · Credentials · Compatibility · Usage · Resources · Version history

Installation

Install as a community node (see n8n docs for your deployment). Package name: n8n-nodes-logit.

For programmatic logging from Node/TypeScript apps, use the SDK instead:

npm install logit

See packages/sdk/README.md for SDK quick start and examples.

Operations

| Operation | Description | | ----------- | ------------------------------------ | | Log Event | POST an event to a named channel |

Parameters (Log Event)

These mirror the SDK’s logit.now(channel, { ... }) payload:

| Field | Required | Notes | | --------------- | -------- | --------------------------------------------------------------------- | | Channel | Yes | Same as the SDK channel string (e.g. payments, user-signups). | | Event | Yes | Event title (e.g. User signed up, Payment successful). | | Description | No | Human-readable details. | | Icon | No | Emoji for the event. | | Notify | No | Send a push notification when true. | | Inbox | No | Show in the real-time inbox (default on). | | Tracking ID | No | Link to an existing timeline using an ID from a previous log call. | | Tags | No | JSON object, e.g. {"environment":"production","priority":"high"}. | | Metadata | No | JSON object for structured fields (e.g. userId, email, amounts). |

The node returns the API response JSON (including an id when successful), one output item per input item.

Credentials

Create Logit API credentials in n8n:

1. Get an API token from Logit (same token you would pass as token to init({ token }) in the SDK).
2. API Token — required.
3. Project ID — optional; inferred from the token if omitted.
4. Base URL — optional; defaults to https://api.logit.now (same idea as the SDK’s optional baseUrl).

Documentation: https://logit.now/docs

Compatibility

Built with n8nNodesApiVersion 1 and n8n-workflow as a peer dependency. Use a current n8n release that supports community nodes. If something breaks on a new n8n major, open an issue with your n8n version.

Usage

• Tags and Metadata must be valid JSON objects (not arrays at the root). Invalid JSON surfaces as a node error for that item.
• Enable Continue On Fail on the node if you want failed requests to pass through with an error field instead of stopping the workflow.
• For high-volume or custom error handling in code, prefer the logit package and patterns in the SDK README (e.g. LogitError).

Resources

• Logit
• Logit docs
• Logit TypeScript SDK (logit) — packages/sdk
• n8n community nodes

Version history

See npm package releases for published versions; package.json reflects the current package version.