User Feedback

The Node SDK can forward user feedback to OwlMetry so it lands in the dashboard's feedback tracker alongside feedback captured by the Swift SDK. Use this when your users submit feedback through your own UI — a web form, a chat widget, a support page — and your Node server acts as the bridge.

See the Feedback concept page for the status lifecycle, comments, and how to work with feedback once it's captured.

Forwarding Feedback

import { Owl } from "@owlmetry/node";

const receipt = await Owl.sendFeedback("The dashboard was really helpful", {
    name: "Jane Doe",
    email: "[email protected]",
    userId: "user_123",
});

console.log(receipt.id);        // uuid of the new feedback row
console.log(receipt.createdAt); // ISO-8601 timestamp

Unlike the logging methods, sendFeedback is not fire-and-forget — it awaits the server response and throws on failure. Wrap calls in try/catch so you can report a useful error back to the user.

Express Example

import express from "express";
import { Owl } from "@owlmetry/node";

const app = express();
app.use(express.json());

app.post("/api/feedback", async (req, res) => {
    try {
        const receipt = await Owl.sendFeedback(req.body.message, {
            name: req.body.name,
            email: req.body.email,
            userId: req.auth?.userId,
            sessionId: req.headers["x-owl-session-id"] as string | undefined,
        });
        res.json({ id: receipt.id });
    } catch (err) {
        res.status(400).json({ error: (err as Error).message });
    }
});

Using a Scoped Logger

A scoped instance auto-fills user_id and session_id so a single request handler can log and send feedback without repeating IDs:

const owl = Owl.withUser(userId).withSession(req.headers["x-owl-session-id"]);
owl.info("feedback form submitted");
await owl.sendFeedback(message, { email });

Pass any option explicitly in the second argument to override what the scope provides.

Options

Limits

• message is required, trimmed, and capped at 4000 characters (enforced server-side).
• The server rejects invalid emails and environments that don't match the API key's app platform — those come back as thrown errors with the server's reason in the message.