Outlit Node.js SDK

The Outlit Node.js SDK records backend product activity when you have user identity or an account ID. It supports:

Identified tracking - Use email or userId for user-scoped resolution
Customer attribution - Add customerId for account/workspace context, even before a user is known
Efficient batching - Events are queued and sent in batches
Device tracking - Use fingerprint for desktop/mobile apps (learn more)

Use it for product events that happen in your backend: feature usage from APIs, completed report exports, and background jobs. For the visitor’s first landing page, referrer, UTM data, and anonymous website activity, use the Outlit Browser SDK and identify that browser visitor when their email becomes available. An email-only server identify cannot link an otherwise anonymous browser visitor. Billing status comes from a verified integration such as Stripe.

Installation

npm install --save @outlit/node

pnpm add @outlit/node

yarn add @outlit/node

bun add @outlit/node

Quick start

import { Outlit } from '@outlit/node'

const outlit = new Outlit({
  publicKey: 'pk_your_public_key'
})

// Track an event
outlit.track({
  email: 'user@example.com',
  customerId: 'cust_123', // Your app's account/workspace/customer ID
  eventName: 'subscription_upgraded',
  properties: {
    fromPlan: 'starter',
    toPlan: 'pro',
    mrr: 99
  }
})

// Important: flush before process exits
await outlit.flush()

Configuration

const outlit = new Outlit({
  publicKey: 'pk_xxx',
  flushInterval: 10000, // ms, default 10s
  maxBatchSize: 100, // events per batch
  timeout: 10000, // request timeout ms
})

Options

string

required

Your organization’s public key.

string

default:"https://app.outlit.ai"

API endpoint for sending events.

number

default:"10000"

How often to automatically flush events (milliseconds).

number

default:"100"

Maximum events per batch before auto-flush.

number

default:"10000"

HTTP request timeout in milliseconds.

API reference

`outlit.track(options)`

Track a custom event for a user, a customer, or both.

outlit.track({
  email: 'jane@acme.com',
  userId: 'usr_12345', // optional if email provided
  customerId: 'cust_123', // Your app's account/workspace/customer ID
  eventName: 'report_exported',
  properties: {
    reportType: 'sales',
    format: 'pdf',
    rowCount: 1500
  },
  timestamp: Date.now() // optional, defaults to now
})

string

User’s email address. Resolves immediately to a customer profile.

string

Your system-owned user/contact ID.

string

Device identifier for anonymous tracking. See Device Tracking.

string

Your system-owned customer/account/workspace ID.

string

required

Name of the event. Use snake_case.

Record<string, any>

Additional data to attach to the event.

number

Unix timestamp in milliseconds. Defaults to current time.

At least one of email, userId, fingerprint, or customerId is required for track(). customerId-only events are valid immediately and can later link to a resolved customer when identify() uses the same customerId with an email.

`outlit.identify(options)`

Update user traits without tracking an event. Customer metadata can be included alongside the user identity.

outlit.identify({
  email: 'jane@acme.com',
  userId: 'usr_12345',
  customerId: 'cust_123', // Your app's account/workspace/customer ID
  customerTraits: {
    plan: 'enterprise',
    seats: 50
  },
  traits: {
    name: 'Jane Doe',
    role: 'admin'
  }
})

string

User’s email address. Use this or userId to establish user-scoped identity.

string

Your system-owned user/contact ID.

string

Device identifier for linking anonymous events. See Device Tracking.

Record<string, any>

Properties to update on the user profile.

string

Your system-owned customer/account/workspace ID. Send this with email or userId to link the account/workspace to the resolved contact profile.

Record<string, any>

Properties to update on the customer profile.

At least one of email or userId is required for identify(). Customer fields are optional additions.

Lifecycle and billing

Send ordinary product facts with track(). For activation, choose the ordinary event that represents your product’s value milestone and track it after the action succeeds:

outlit.track({
  email: 'user@example.com',
  eventName: 'onboarding_completed',
  properties: { flow: 'onboarding' }
})

Choose this event as your activation event in Outlit. The first matching event records activation once for each eligible resolved person and company, independently. Billing status comes from verified integrations such as Stripe. See Customer journey.

`outlit.flush()`

Immediately send all queued events. Call this before your process exits.

await outlit.flush()

`outlit.shutdown()`

Shut down gracefully: flushes remaining events and stops the timer.

await outlit.shutdown()

`outlit.queueSize`

Get the number of events waiting to be sent.

console.log(`Pending events: ${outlit.queueSize}`)

Framework examples

Express.js

import express from 'express'
import { Outlit } from '@outlit/node'

const app = express()
const outlit = new Outlit({ publicKey: 'pk_xxx' })

// Middleware to attach tracker to request
app.use((req, res, next) => {
  req.outlit = outlit
  next()
})

app.post('/api/reports/export', async (req, res) => {
  const { user, format } = req.body

  // Your export logic
  const report = await generateReport(format)

  // Track the event
  req.outlit.track({
    email: user.email,
    eventName: 'report_exported',
    properties: { format, size: report.size }
  })

  res.json({ success: true })
})

// Graceful shutdown
process.on('SIGTERM', async () => {
  await outlit.shutdown()
  process.exit(0)
})

Next.js API routes

// app/api/subscription/upgrade/route.ts
import { Outlit } from '@outlit/node'

const outlit = new Outlit({ publicKey: process.env.OUTLIT_KEY! })

export async function POST(request: Request) {
  const { userId, email, customerId, newPlan } = await request.json()

  // Your upgrade logic
  await upgradeSubscription(userId, newPlan)

  // Track the event
  outlit.track({
    email,
    userId,
    customerId,
    eventName: 'subscription_upgraded',
    properties: { plan: newPlan }
  })

  // Flush immediately (serverless)
  await outlit.flush()

  return Response.json({ success: true })
}

Serverless functions (AWS Lambda, Vercel)

In serverless environments, always call flush() before returning. The function may be terminated before the background flush runs.

import { Outlit } from '@outlit/node'

const outlit = new Outlit({ publicKey: process.env.OUTLIT_KEY! })

export async function handler(event) {
  const { email, action } = JSON.parse(event.body)

  outlit.track({
    email,
    eventName: action,
    properties: { source: 'lambda' }
  })

  // Critical: flush before returning
  await outlit.flush()

  return { statusCode: 200, body: 'OK' }
}

Stripe webhooks

Connect Stripe as a verified Outlit integration. Subscription state then updates account billing status automatically; do not translate Stripe webhooks into SDK events.

Background jobs (Bull, Agenda)

import { Queue, Worker } from 'bullmq'
import { Outlit } from '@outlit/node'

const outlit = new Outlit({ publicKey: 'pk_xxx' })

const worker = new Worker('emails', async (job) => {
  const { email, templateId } = job.data

  // Your job logic
  await sendEmail(email, templateId)

  // Track completion
  outlit.track({
    email,
    eventName: 'email_sent',
    properties: { templateId, jobId: job.id }
  })
})

// Periodic flush (events batch automatically)
// No need to flush per job unless critical

Common events to track

Here are recommended server-side events:

Event	When	Properties
`feature_used`	Feature usage	`feature`, `count`
`api_key_created`	API key created	`keyName`, `permissions`
`export_completed`	Data export	`format`, `rowCount`, `size`
`invite_sent`	Team invite	`role`
`user_role_changed`	Permission change	`fromRole`, `toRole`

Error handling

The SDK silently handles errors to not disrupt your application. For debugging:

const outlit = new Outlit({ publicKey: 'pk_xxx' })

// Events are queued even if the network is down
outlit.track({ email: 'user@test.com', eventName: 'test' })

// Check queue size to detect potential issues
if (outlit.queueSize > 500) {
  console.warn('Outlit queue backing up - possible connectivity issue')
}

TypeScript support

Full TypeScript support is included:

import {
  Outlit,
  type OutlitOptions,
  type ServerTrackOptions,
  type ServerIdentifyOptions,
} from '@outlit/node'

const options: OutlitOptions = {
  publicKey: 'pk_xxx',
  flushInterval: 5000,
}

const outlit = new Outlit(options)

const trackOptions: ServerTrackOptions = {
  email: 'user@test.com',
  customerId: 'cust_123', // Your app's account/workspace/customer ID
  eventName: 'test',
  properties: { key: 'value' }
}

outlit.track(trackOptions)

Agents

CLI

Concepts

Outlit SDKs

Examples

Outlit Node.js SDK

Installation

Quick start

Configuration

Options

API reference

`outlit.track(options)`

`outlit.identify(options)`

Lifecycle and billing

`outlit.flush()`

`outlit.shutdown()`

`outlit.queueSize`

Framework examples

Express.js

Next.js API routes

Serverless functions (AWS Lambda, Vercel)

Stripe webhooks

Background jobs (Bull, Agenda)

Common events to track

Error handling

TypeScript support

Next steps

Identity resolution

Customer journey

​Installation

​Quick start

​Configuration

​Options

​API reference

​outlit.track(options)

​outlit.identify(options)

​Lifecycle and billing

​outlit.flush()

​outlit.shutdown()

​outlit.queueSize

​Framework examples

​Express.js

​Next.js API routes

​Serverless functions (AWS Lambda, Vercel)

​Stripe webhooks

​Background jobs (Bull, Agenda)

​Common events to track

​Error handling

​TypeScript support

​Next steps

Identity resolution

Customer journey

Installation

Quick start

Configuration

Options

API reference

`outlit.track(options)`

`outlit.identify(options)`

Lifecycle and billing

`outlit.flush()`

`outlit.shutdown()`

`outlit.queueSize`

Framework examples

Express.js

Next.js API routes

Serverless functions (AWS Lambda, Vercel)

Stripe webhooks

Background jobs (Bull, Agenda)

Common events to track

Error handling

TypeScript support

Next steps