How Revnu Works

Revnu is a growth agent. It finds buyers, writes and sends outreach, runs ads and writes the pages that get a business found in search and AI answers. The API does not give you those tools directly. It gives you the same controls a customer has in the dashboard: see what the agent wants to do, say yes or no, tell it what to do next, and read what happened. There is no lead-search, enrichment or sending route of your own. If you are weighing Revnu against building your own agent, what the API exposes and what it doesn't is the honest list. New to the API? Start at Developers.

Review cards

Anything that needs your say-so becomes a card in the review queue: an email draft, a blog post, a budget change, a question. A card has a kind, a sourceType naming the work, and a status of pending or needs_revision. The kinds that ask you to decide are approval (ship this), question (often with textInput) and choice (pick one of options). The others record the agent's own work: review (a judgment worth a second look), follow_up, setup, and update (a result with nothing to decide). Expect new kinds over time.

Each card lists the verbs it accepts right now in actions, and the label the dashboard would put on its main button in primaryLabel. Build your UI from those two fields rather than from sourceType, and new kinds of work render correctly without a code change. The verbs:

What ships on its own

Whether work waits for a person is set per kind of work in Settings → Agent → What Needs Your Approval. Each of six settings is Ask Me First or Just Do It: Blog Posts, Start Sequences, One-Off Emails, LinkedIn connection requests, LinkedIn messages and Ad Tests. The API follows the same settings as the dashboard.

Your first sequence always waits for your yes. After that, the settings decide what asks first. Replies to prospects, spend, budgets, booking links, new inboxes and Reddit comments always wait, whatever the settings say. Once you approve a sequence, its later email and LinkedIn steps send without asking each time.

Blog posts, blog edits and one-off emails set to Just Do It still appear as cards, with autoResolveAt set: the time they ship unless you act first. That is at least four hours ahead for an email and a day for a blog post or edit, landing at 09:00 on a weekday in your time zone. Snoozing a card cancels its deadline.

Approval and review cards that wait seven days expire, so the queue never turns into a backlog. Questions, choices, follow-ups, setup cards and blog cards don't expire, and update cards close after two days because there is nothing to decide.

The agent

The agent runs in its own sandbox and wakes on a schedule, on new mail and replies, and when you message it. Send it a message the way you would in the dashboard chat, then wait for the reply inline or poll. Agent status says whether it is up, busy, and when it next wakes.

Workflows

A workflow is a recurring job written in plain words: a schedule such as "every weekday at 09:00 Europe/London" and a list of steps. A step can carry a gate, which makes it wait for a person before it acts. The agent reads the steps on every run, so volume ("five per day") is an instruction in a step, not a numeric field. See Create a workflow.

Results

Results is the scoreboard the agent reads when it wakes: one section per channel, each either available with numbers or unavailable with a reason. A channel that is not connected says so rather than reporting zero.

Leads

A lead is a company the agent has researched, with a status, a score, contacts, your own columns, and the draft it would send. You can read leads, set their labels, and keep a block list of companies, mailboxes and LinkedIn profiles that outreach must never touch.