Skip to main content
Agent Flows are Klove’s automation layer. A Flow is a sequence of AI-powered steps — called Moves — that run on a schedule or fire in response to a platform event, without you having to manually initiate each action. Flows connect your monitoring data to the work that improves visibility: analysing gaps, creating content, updating agentic pages, and reaching out to the sources AI already trusts.

​
What Moves are

Every step inside a Flow is a Move. Moves are the individual actions an AI agent executes on your behalf. They come in four categories:

Prompt analysis

Analyse prompt data to identify visibility gaps, sentiment shifts, and competitive position changes. Produces a structured insight report or feeds downstream Moves.

Content creation

Write blog posts, FAQ blocks, comparison guides, listicles, or landing page copy — calibrated against the citation patterns Klove has observed in AI responses for your category.

Page optimisation

Generate or update an agentic page based on current monitoring data, new competitor sources, or prompt performance. Publishes directly to the edge when approved.

Outreach

Source the contact details for an editor or site owner, draft a personalised outreach email, and stage it for your review before sending — targeting the publications AI already cites in your category.

​
Trigger types

Every Flow starts with a trigger. You can choose from two types: Schedule-based triggers run the Flow at a fixed cadence — daily, weekly, or monthly. Use these for routine workflows like weekly content gap analysis or monthly competitive benchmarking. Event-based triggers fire when Klove detects a change in your monitoring data. Supported events include:
  • Visibility score drops below a threshold
  • Sentiment shifts from positive to negative for a tracked prompt
  • A competitor enters the top position on a prompt where you previously ranked first
  • A new source appears in AI citations for your category
Event-based triggers let you respond to changes in AI behaviour as they happen, not when you next log in.

​
Agent credits

Each Move in a Flow consumes agent credits. Credits are consumed when Klove runs an AI-powered step — a content generation call, a web scrape, an outreach draft, a page publish.
Credits are consumed per Move execution, not per Flow run. A Flow with three Moves consumes three times the credits of a single-Move Flow. Monitor your credit usage in Settings → Usage to avoid hitting your plan limit mid-month. Unused credits do not roll over between billing periods.

​
How to create a Flow

1

Open Agent Flows

Navigate to Agent Flows in the left sidebar of your Klove workspace and click New Flow.
2

Name your Flow

Give the Flow a descriptive name — for example, “Weekly content gap analysis” or “Sentiment drop — agentic page update”. This name appears in the Flows dashboard and in activity logs.
3

Set the trigger

Choose Schedule and set the frequency, or choose Event and select the monitoring event that should fire the Flow. For event triggers, configure the threshold (for example, “visibility score drops below 40%”).
4

Add Moves

Click Add Move and select the type of action. Configure each Move’s inputs — for a content creation Move, specify the target prompt, intended format, and any brand guidelines. For an outreach Move, specify the target publication or domain.
5

Set approval rules

Choose whether each Move executes automatically or requires your approval before taking action. Content creation and outreach Moves default to requiring approval; page publishes can be set to auto-deploy if you prefer fully automated operation.
6

Activate the Flow

Toggle the Flow to Active. Klove will execute it on the next trigger event. You can pause or edit a Flow at any time without deleting it.

​
Example use cases

​
Auto-update agentic pages on sentiment drop

Trigger: Visibility score for “best CRM for startups” drops below 35% on ChatGPT. Moves:
  1. Prompt analysis — identify which sources AI is currently citing for this prompt and compare against your current agentic page content.
  2. Page optimisation — regenerate the agentic homepage with updated FAQ content targeting the gap, incorporating the cited sources’ structure and terminology.
  3. (Optional) Outreach — draft an email to the editor of the top-cited third-party guide, requesting inclusion.
This Flow detects a visibility drop the same day it happens and queues a page update for your approval, rather than waiting for a weekly review.

​
Weekly content gap analysis

Trigger: Every Monday at 08:00. Moves:
  1. Prompt analysis — compare your share of voice against the top two competitors across all tracked prompts for the past seven days.
  2. Content creation — generate a brief (300-word summary) identifying the three prompts with the largest competitor advantage and one recommended content action per prompt.
The summary lands in your activity feed every Monday morning, giving your content team a prioritised brief without any manual reporting.

​
New competitor source alert

Trigger: A new domain appears in AI citations for your category (not previously seen in the last 30 days). Moves:
  1. Prompt analysis — identify which prompts cite the new source and what content on that domain AI is referencing.
  2. Outreach — source the site owner’s contact details and draft a pitch for inclusion in the cited article or guide.
Start with a simple two-Move scheduled Flow before building event-triggered automation. A weekly prompt analysis → content brief Flow gives you immediate value with predictable credit usage, and builds familiarity with how Moves chain together before you automate responses to live monitoring events.

​
Reviewing Flow activity

Every Flow run is logged in the Activity tab of Agent Flows. You can see which trigger fired, which Moves executed, how many credits were consumed, and the output of each step. Moves waiting for approval appear in your Review queue with a preview of the proposed action.

Prompt Monitoring

The data source that powers event-based Flow triggers

Agentic Pages

The pages that page-optimisation Moves publish to