Marketing & Content workflow ideas
Campaign assets and content at scale — ad creative, social calendars, SEO copy, and outreach.
A Boolean Constant
The smallest possible graph, and a real one: a pinned flag feeding a branch, so a switch lives in the workflow rather than in someone's head.
A Campaign Concept from a Brief
A brief becomes a concept with a line, a visual idea and three channel executions. Asking for the executions is what forces the concept to be one that survives contact with a media plan.
A Fixed Point in Time
A pinned timestamp with an explicit timezone. Anything that has to be reproducible needs the date fixed in the graph rather than read off the clock at run time.
A Webhook That Answers
An HTTP POST arrives and the graph replies in prose. The trigger hands you the request body, headers and method; this one reads the body and writes a one-line summary a human can act on. Register the workflow to get a delivery URL, or drive it from the CLI with `--trigger-event '{"node_id":"hook","payload":{"body":{...}}}'`.
Ad Copy in Three Registers
The same offer written plain, playful and premium. Register is usually the variable a team argues about, so produce all three and let the work settle it.
Audio To Image
Speak an image into existence: no keyboard needed. Whisper transcribes your audio, then FLUX renders the description as an image — the whole pipeline runs from a single voice note.
Blog Post to Social Thread
One long piece becomes a numbered thread. The constraint that each post stand alone is what stops the model producing a summary chopped into pieces.
Bullet Points to Press Release
Facts in, a structured release out — headline, dateline, body, boilerplate. Keeping the quote attributable to a named role stops the model inventing a spokesperson.
Chat With Your Documents
Retrieval-augmented Q&A over your own documents. Index a small knowledge base into a vector collection, pull the passages matching a search keyword, and get a Markdown answer that cites its sources and refuses to guess when the answer isn't in the docs. NodeTool's first RAG example. The answer step uses gpt-5-mini (OpenAI key); the collection is configured for Ollama nomic-embed-text embeddings.
Chunk a Transcript for Indexing
Split a long passage into overlapping windows the way a RAG ingest does, then count them. `length` and `overlap` are counted in WORDS, not characters — a 90 here would swallow this whole passage into one chunk. Overlap is the point: a boundary landing mid-sentence loses the claim that straddles it, so neighbouring chunks share a tail. Counting needs Collection first, because Count consumes a stream and a list handed to it arrives as a single item.
Conditional Logic Engine
Teaching example for control flow: one number drives two independent decision structures built entirely from If nodes — there is no dedicated numeric-compare or boolean-logic node in NodeTool, so this shows the actual pattern: PadText + Compare + Equals turn the number into a boolean, then pairs of If nodes sharing one condition (each holding its own value, taking the opposite branch) act as the ternary select and OR you'd otherwise reach for. No LLM calls.
Count and Measure
An integer and a float constant side by side — the pinned numbers a workflow reads as settings: how many, and how much.
Does This Text Mention the Deadline
A containment check returning a boolean — the branch condition for a workflow that routes on what a document says.
Draft Answers for an FAQ
Questions in, answers out, each short enough to survive being pasted into a help centre without editing.
Drop the First Few
Skip a fixed number of items off the front of a stream — the header rows of a feed, or a warm-up you do not want to pay to process.
Every Combination
Cross product of two streams — every left item against every right one. The sweep you build before a batch of paid renders, so you can see the count before you pay for it.
Executive Summary of a Long Document
One page for someone who will not read twelve. Leading with the decision required is what makes it a briefing rather than a précis.
Extract the Claims Worth Checking
Separates the factual claims from the opinions, and rates how checkable each one is — the triage step before any verification work.
Find Every Number in a Sentence
FindAllRegex returns each match rather than the first, which is what you want when pulling figures out of a report.
Five Headlines for a Landing Page
Headline variants for a test. Asking for a stated angle per line makes the set genuinely different rather than five rewordings of the first idea.
How Long Is This String
Character length as a first-class value, so downstream nodes can branch on size without a code node.
Image To Audio Story
Upload any photo and a vision agent narrates a spoken story about it — one image in, one audio clip out
Keep Only the Matches
Equality filter over a stream. `invert` turns it into a reject list without a second node.
Last One Wins
Collapse a stream to its final item. The natural end of a loop that refines a value rather than accumulating one.
Localise a Product Listing
Currency, units and address format are where listings actually break in a new market — more often than the prose does.
One Tagline, Six Markets
A tagline in six languages with a back-translation for each, so someone who reads none of them can still see what was actually said.
Pokemon Maker
Turn any mix of real animals into a gallery of original collectible creatures. A style dropdown restyles the whole batch, so one Run yields four cohesive variant designs instead of a single image.
Private Assistant
Ask questions about your own notes and documents — fully local, no API keys. Runs end-to-end on a local Ollama model, so the text never leaves your machine. Requires Ollama running with a model pulled (default: llama3.2 — run `ollama pull llama3.2`).
Prompt Template
The starter pattern behind almost every NodeTool workflow: typed inputs fill a reusable prompt template, an LLM answers it, the output renders. Explains a topic for any audience — swap the prompt to reuse the pattern for anything.
Redact Email Addresses
A regex replace standing in for the everyday cleanup step — strip personal data out of text before it reaches a model or a log.
Redact and Tidy a Log Line
Two regex passes and a whitespace collapse, in the order that matters: redact before you normalise, or the pattern you are matching may already have been reshaped.
Rewrite This So a Customer Understands It
Jargon in, plain language out, at a stated reading level. The most common editing job there is, and the one most worth a repeatable workflow.
SEO Title and Meta Description
The two fields every CMS demands, written to their real limits — 60 and 155 characters — so nothing is truncated in the results page.
Split a Log into Records
Regex split turns one blob into a list. The pattern is the record boundary, which is often more reliable than a fixed delimiter.
Strip Accents for a Search Key
Fold accented characters down to ASCII so a lookup key matches regardless of how the name was typed.
Subject Lines Worth Testing
Eight subject lines split between curiosity and clarity — the two strategies that behave differently enough to be worth an A/B, unlike eight variations on one.
Take While the Numbers Are Small
TakeWhile stops at the first item that fails the predicate, unlike a filter, which would keep testing the rest. That difference is the reason to reach for it: it caps work rather than selecting from it. The expression binds each item as `item`.
Themes Across Customer Feedback
Raw feedback becomes named themes with counts and a representative verbatim each. The verbatim is what makes the theme arguable rather than asserted.
Tidy Up Messy Text
Three cleanups in a row — collapse runs of whitespace, strip punctuation, then lowercase. The order matters, which is the point of showing it as a chain rather than one node.
Title Case a Heading
Casing helpers, applied to a heading. Small, but these are the nodes you reach for constantly when formatting model output for display.
Translate Marketing Copy to German
Marketing copy translated for effect rather than word-for-word, with the formal/informal choice stated. That decision is the one that most often gets a translation rejected.
Trim a Blurb to Length
Cap text at a character budget with an ellipsis. The everyday fix for a card or preview that must not overflow.
Turn Specs into Product Copy
Paste a spec sheet, get copy. The system prompt forbids inventing anything not in the input, which is the difference between usable product text and a liability.
Turn a Changelog into Release Notes
Commit messages are written for engineers; release notes are read by customers. Grouping by what changed for the user is the whole translation.
Turn a Support Thread into a Bug Report
A frustrated thread becomes something an engineer can act on: steps, expected, actual, environment — with the missing pieces named as missing.
Validate a Postcode Shape
RegexValidate answers whether text matches a pattern — a guard to run before you trust user input or model output as structured data.
Wrap a Value in Quotes
SurroundWith builds a fragment from a value — the small assembly step between a model's answer and a template that expects delimiters.
Build any of these on the canvas
Every idea here ships as an example workflow. Download Studio and open it in one click.