What session id should I use in Flowise?

Any stable identifier for the conversation — reuse your existing Flowise session or thread id so turns are grouped correctly.

Is passing the prompt required for Flowise?

It is optional but strongly recommended: the prompt is what makes the injected ad contextually relevant to the current turn.

How-to guide

How to Pass Session Context to Ads in Flowise

This guide shows how to pass session context to ads in a Flowise app, the goal being to supply session id, prompt, and metadata so injected ads are relevant. It builds on the Monetzly server SDK, so the approach is specific to how Flowise produces and streams responses.

Overview

Ad relevance in a Flowise app comes from context. When you inject, you pass a session id, the live prompt, and optional metadata — that is what lets Monetzly match a recommendation to what the user is actually asking about in that turn.

The session id groups turns from the same conversation; the prompt drives per-turn relevance; metadata carries anything extra you want to target on. All are supplied per injection call.

Flowise apps are usually built for visual chatbot building, no-code RAG, and prototyping agent flows, so pass session context to ads typically comes up while a user is mid-conversation, the moment where monetization has to be additive rather than disruptive.

How this works on Flowise

Flowise runs on Node, so the Monetzly SDK can live in the layer that consumes a flow's prediction stream. Call the Flowise prediction API with streaming enabled, adapt its SSE token events to { content }, and pass them through sdk.inject() before relaying to your users. Confirm the streaming response shape for your Flowise version / deployment.

Because Monetzly's inject() accepts any async token stream, the Flowise side of this task is just mapping your output to it, no rewrite of your Flowise model call.

Steps

Choose a stable session id for the conversation (reuse your Flowise session or thread id).
Pass the current user prompt on each injection call.
Add optional metadata (topic, user type) to sharpen targeting.

Integration snippet

import { MonetzlySDK } from "@monetzly/server-sdk";

const sdk = new MonetzlySDK({
  apiKey: process.env.MONETZLY_API_KEY!,
  serverAddress: process.env.MONETZLY_SERVER_ADDRESS!,
});
await sdk.connect();

// TODO_VERIFY: adapt to your Flowise streaming prediction response shape.
async function* flowiseChunks() {
  const res = await fetch(`${FLOWISE_URL}/api/v1/prediction/${flowId}`, {
    method: "POST",
    headers: { "Content-Type": "application/json" },
    body: JSON.stringify({ question, streaming: true }),
  });
  for await (const token of parseSSE(res.body!)) yield { content: token };
}

for await (const t of sdk.inject(flowiseChunks(), { prompt: question })) send(t.content ?? "");
await sdk.disconnect();