How-to guide
How to Choose Which Turns Show Ads in n8n
This guide shows how to choose which turns show ads in a n8n app, the goal being to control ad placement and frequency across a conversation. It builds on the Monetzly server SDK, so the approach is specific to how n8n produces and streams responses.
Overview
Not every turn in a n8n conversation should carry an ad. Placement and frequency shape both revenue and user experience: too many ads erodes trust, too few leaves revenue on the table.
You control this by deciding which responses you route through injection — for example, skipping very short replies or the first turn, and allowing ads on substantive answers where a recommendation is genuinely useful.
n8n apps are usually built for automated AI workflows, chatbot backends, and agent orchestration, so choose which turns show 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 n8n
n8n runs on Node, so a Code node (or a small custom node) can import @monetzly/server-sdk and wrap the token output of an upstream LLM node. Because n8n items are usually discrete rather than a live token stream, confirm whether you inject over a buffered response or a true stream for your workflow.
Because Monetzly's inject() accepts any async token stream, the n8n side of this task is just mapping your output to it, no rewrite of your n8n model call.
Steps
- Decide your policy: which n8n turns are ad-eligible (e.g. skip trivial or first replies).
- Route only eligible turns through the injection call.
- Measure revenue and engagement, then adjust frequency.
Frequently asked questions
Start monetizing in about 5 minutes
Wrap your existing LLM response stream with the Monetzly SDK and earn on every session, no paywall required.