Skip to content
NagentNagent
Log inSign upHire your AI Growth Team
NagentNagent
Log inSign up
All documentation

Workflows in a room

The prebuilt workflows a team room carries, how to run one now or as a free test, keep it on its schedule, and follow each step as it runs.

Browse documentation

A room arrives knowing some of its work

A workflow is a run of steps that ends in something you can use: a week of posts drafted, ten accounts with a first email each, an audit with its fixes in order. Nine of the rooms you can add come with workflows already built for their team, so the first useful run is one press away.

RoomPrebuilt workflows
DRIS team6
HOOK team5
Echo team5
NORA team6
Content5
Sales5
Marketing5
CRM team5
NIA team5

Each one is published in your workspace when the room is added, belongs to that room, and also appears in the Workflows list on the Agent Workbench. Nothing runs until a person picks it. Each step is done by one of the agents the room always has, most often its lead, using what the workspace knows about your brand, offering and audience. Change your copy in the workflow editor and it stays yours: a later install never overwrites it.

Where the workflows are

Open the room from Teams and choose its Workflows tab, next to Spotlights. The cards are at the top: "Pick one to run now. Each one can keep running on its schedule." Under them is the room's list of the workflows it can run, where someone who can set up the room adds or removes one, and Build a new one for this team. The same cards and list are on the Automations tab of the member list, which opens when you press the faces at the top of the room.

Each card shows the workflow's name and what it makes. The ones that suit a first hour carry Good first run and are listed first. A room with none installed says No workflows are set up for this room yet.

Each card has three controls:

ControlWhat it does
Run nowStarts a real run, with every tool its steps are allowed
Test run, free modelRuns the same steps on a free model, at no cost to you
Keep runningA switch that runs it on its schedule or event, for example Keep running: Mondays at 09:00

A workflow with no schedule or event for this room says Runs when you ask in place of the switch. While a schedule is on, the card says when it runs next under the switch, for example Next run Mon 12 Oct, 09:00 IST. A workflow on the room's list that is not published yet shows "Not published yet, so it cannot run. Whoever can change it publishes it on the workflow page." and no run buttons.

A workflow the lead adds from a meeting's minutes is one of the room's workflows too, with its own card. It can be started, test run and scheduled the same way. See huddles.

Run now

The card answers under its buttons: "Started Weekly pipeline review. Its steps show in Messages as they finish, and the result posts there." with an Open the run link. The room's Messages are told at once too: "Started Weekly pipeline review. Each step shows below as it finishes, and the result posts in this room when the run ends."

Open the run opens the workflow's page with that run picked in the run panel, so you can follow each step and read the result. If you cannot change the workflow, the page is read-only and the run panel shows the run without its buttons. If you read it only through this room, the page shows the runs started in this room and the run you opened, and not the workflow's steps.

A start goes through the same checks as any work in the room, so a workflow can be held for a person. The card then says Waiting for approval before it starts. and the run waits in approvals and the Inbox. A start that is refused says why under the card, in plain words.

Test run, free model

A test run proves the plumbing: the steps run in order, the card fills in the room and the result posts where it should. It runs on a free model and may only read your workspace's own records, such as the Knowledge Hub, your brand voice, your leads and your visibility findings. It does not search the web or call a connected tool, so expect a thinner result than a real run. The room's start line says it was started "as a test run on a free model".

Only workflows whose steps each run one agent can be test run. Every prebuilt workflow can. A workflow you build with other kinds of step is refused with the reason.

Keep running

Switch it on and the workflow runs on its schedule, or when its event happens, and posts each result in the room. Switch it off and it runs only when someone asks. Switching on at 09:03 does not run the 09:00 it just missed: the first run is the next one shown on the card.

Every prebuilt schedule starts switched off, in your workspace's time zone. That is the zone of the workspace's longest serving admin, the one their browser gave when they signed up, or India time (IST) when none is known. A schedule keeps its zone through daylight saving.

Only a published workflow can keep running. Turning on one that is not published is refused with "This workflow is not published yet, so its schedule stays off. Publish it, then turn the schedule on."

The switch acts on this room's own schedule only: the schedule or event that reports to this room. If the same workflow also runs on a schedule for another room, or one that reports nowhere, that one is not changed; it is switched on the workflow's own page, in its Triggers panel.

Who can press what:

  • Run now and Test run need permission to run the room's workflows, which every Member holds, as do the Chief of staff, Team lead and Organisation admin. Without it the buttons are not shown.
  • Keep running counts as changing the workflow, so it is for the Chief of staff or Team lead of the team the workflow belongs to, or an Organisation admin. For anyone else the switch is greyed out, and pointing at it says "Only someone who can change this workflow can turn its schedule on or off: its team's Chief of staff or Team lead, or an admin."

Running is checked at this room, and changing at the workflow's own team. A workflow made by another team but put on this room's list runs for this room's people and is still changed by its own team's leads.

Say it instead of pressing it

Each control can be typed in the room's Messages, as long as you name one of this room's workflows exactly, by its title. Typing needs permission to post in this room, which a Chief of staff and an Organisation admin hold. A Member, or a Team lead whose role is held at one team, does not, and presses Run now on the card instead.

  • "run Competitor social scan" starts it.
  • "keep running Competitor social scan" or "turn on the schedule for Competitor social scan" switches its schedule on.
  • "pause Competitor social scan" switches it off.

The room answers with what it did. A sentence that names no workflow of the room stays ordinary work for the lead.

Schedule it with a sentence

You can also give a workflow a new schedule in one sentence, with how often and, if you like, what time. In Prompt World's HOOK team room:

schedule Competitor ad scan every Friday at 4pm

The room's lead saves it and replies:

Scheduled: every Friday at 16:00 IST. Next run Fri 16 Oct.

When no next run can be worked out, the reply stops after the time: "Scheduled: every Monday at 09:00 IST."

What the sentence needs:

  • One of run, start, schedule or kick off, as in "run Newsletter issue every Monday".
  • How often: every day, every weekday, every week, or one named day such as "every Friday" or "on Tuesdays". Every week means Mondays.
  • A time, if you want one: "at 9", "9am", "9:30 pm", "17:30" or "noon". With no time it runs at 09:00.
  • The workflow's exact title, one of this room's workflows.

"Every day", "daily" and "nightly" mean all seven days, the same as the prebuilt Every day at 09:00 schedules. "Every weekday", "every business day" and "on weekdays" mean Monday to Friday, and the reply says which you got: "Scheduled: every weekday at 08:00 IST." A monthly schedule cannot be set in a sentence; change it on the workflow's page in the Agent Workbench.

The time is read in your own time zone, or India time (IST) when none is known. Saving replaces the workflow's schedule for this room, or adds one if it had none here, switches it on and sends each result to this room. A schedule that reports to another room is never changed by it. The card's switch then reads, for example, Keep running: Competitor social scan, every Friday at 16:00.

Anyone who can type in the room's Messages can say it, which a Member cannot, but only someone who can change the workflow can save it, the same people as the switch. Without it the room says "Only someone who can change this workflow can turn its schedule on or off: its team's Chief of staff or Team lead, or an admin." The same rule holds for a sentence that switches a schedule on or off, and for one said in a Slack channel linked to the room. A workflow that is not published is refused with "This workflow is not published yet, so its schedule stays off. Publish it, then turn the schedule on."

The room does not read a schedule from a question, from a sentence that says don't, stop, pause or cancel, from a message over one line, or from one that could mean two workflows. A sentence that names none of the room's workflows gets an ordinary reply from the lead.

Start the next job when work is accepted (Beta)

A chain starts one agent or workflow when another's work is accepted. Say it in the room in one sentence:

when DRIS finishes, have HOOK draft the ads

after Competitor social scan is done, run Newsletter issue

The first name can be any agent you know by name, or one of this room's workflows. The second must be an agent on this room's team, since its job runs here, or one of this room's workflows. After an agent you say what its job is, as in "draft the ads". The lead replies with one card, for example "I can set this chain up: When DRIS's work is accepted, then HOOK: draft the ads, in this room. Approve the card to switch it on." Once it is approved, its result reads "Chain on:" and the chain.

Accepted means the lead approved an agent's room job at its review, or a person gave a workflow run a thumbs up on its run file. A job that fails, is rejected or only finishes starts nothing.

A chain runs at most 3 steps, and never runs the same trigger twice in one chain. At the limit the lead posts "This chain ended at its limit of 3 steps", names what was not started, and says to ask again in the room if you want it run.

Setting one up needs permission to set up the team, which a workspace admin holds. Without it the room says "Setting up a chain needs permission to set up this team, which a workspace admin holds." Like a schedule sentence, a chain is not read from a question, from a sentence that says don't, never, stop, pause or cancel, from a message over one line, or from one where a name could mean two agents or workflows.

An agent's chains are listed on its Triggers tab in the Agent Workbench, where each one can be switched off.

Each step shows as it runs

A card sits under the start line and follows the run. Its first line says Working while a step works, and Waiting for approval. when no step is working and at least one is waiting on a person. Under it is one line per step, with the step's name and its state: waiting, working, needs approval, done, failed or skipped. Once a step has written something, the start of it shows beneath the step, so you can read the work as it arrives.

A request that has waited a day gets one reminder in the room. See waiting for approval.

When the run ends, the card's first line becomes one of these:

The card saysWhat it means
Finished. The result is posted in this room.The result is in the room as its own message
Stopped before finishing.A step failed and the run ended early
Cancelled.Someone stopped the run
Expired: nobody answered in time.A step's request waited 7 days with no answer, or was gone before anyone answered, so the run ended

What each room carries

The schedule is what Keep running turns on, at that time in your workspace's time zone. Workflows marked Good first run are listed first on the cards.

DRIS team

WorkflowKeep running
Weekly actions for your team leads (Good first run)Mondays at 09:00
AI visibility check (Good first run)Mondays at 09:00
Keyword gap against three competitorsFirst of the month at 09:00
Technical site auditFirst of the month at 09:00
Answer page for one buyer questionRuns when you ask
Weekly visibility reportMondays at 09:00

HOOK team

WorkflowKeep running
Ad hooks and angles (Good first run)Mondays at 09:00
Competitor ad scanMondays at 09:00
Creative brief for RUPARuns when you ask
Audit an uploaded ad fileRuns when you ask
Ad test planRuns when you ask

Echo team

WorkflowKeep running
Reputation scan (Good first run)Mondays at 09:00
What AI assistants say about youMondays at 09:00
Review reply draftsEvery day at 09:00
Reputation against competitorsFirst of the month at 09:00
Weekly mentions digestMondays at 09:00

NORA team

WorkflowKeep running
Your ICP from your website (Good first run)Runs when you ask
New ICPs and the segments most likely to convert (Good first run)First of the month at 09:00
Ten lookalike accounts with first-touch drafts (Good first run)Mondays at 09:00
Enrich and score a listRuns when you ask
Follow-up sequenceWhen a lead replies
Signals on a named accountWhen a signal is flagged

Nothing NORA's workflows draft is sent. Drafts wait for you.

Content

WorkflowKeep running
Content brief and blog draft (Good first run)Mondays at 09:00
A month's editorial calendarFirst of the month at 09:00
Refresh an old postRuns when you ask
Newsletter issueThe 1st and 15th at 09:00
Landing page draftRuns when you ask
Product shootRuns when you ask

Sales

WorkflowKeep running
Weekly pipeline review (Good first run)Mondays at 09:00
Follow-ups for deals gone quietMondays at 09:00
Account brief before a callRuns when you ask
Monthly sales forecastFirst of the month at 09:00
Win and loss reviewFirst of the month at 09:00

Marketing

WorkflowKeep running
Weekly marketing report (Good first run)Mondays at 09:00
Campaign brief from one goalRuns when you ask
Next month's marketing planFirst of the month at 09:00
Competitor watchThe 1st and 15th at 09:00
Message check against your buyersFirst of the month at 09:00

CRM team

WorkflowKeep running
This week's lead priorities (Good first run)Mondays at 09:00
Record health checkFirst of the month at 09:00
Customers at riskMondays at 09:00
Customers ready for moreFirst of the month at 09:00
Follow-ups from yesterday's meetingsEvery day at 09:00

NIA team

WorkflowKeep running
Weekly paid results review (Good first run)Mondays at 09:00
Budget shift proposalMondays at 09:00
Ad copy variants for one campaignRuns when you ask
Plan a new campaignRuns when you ask
Search terms to add and excludeThe 1st and 15th at 09:00

Nothing these workflows draft is sent, and NIA's proposals change no budget or campaign: each change waits for a named approver.

Asking several teammates at once

You can also start a run without a workflow, by naming two or more agents in one message:

@NORA find five companies that fit our ICP, @LIPI draft a follow-up to the leads who replied this week

The room splits the message by name, and each teammate works on the part addressed to it, side by side. Text before the first name goes to nobody; if a name has nothing after it, as in "@NORA @LIPI review the pipeline", every teammate gets the whole message. The room says who is working on what: "Each teammate you named is working on their part:", then one line each, then "When they finish I review what they did and post one answer here." The same step card follows each part.

At most six teammates start from one message. A teammate that is not on the team, is switched off, is over its budget, or has no tools or instructions to work from is left out, and the start line names it under Left out:. If fewer than two are left, the message goes to the one that is, as a single mention would.

The lead reads the work before you do

Nothing the parts produce reaches you until the room's lead has read it. The lead then does one of three things:

  • Writes the answer from what the parts produced, and posts it once.
  • Builds what was missing. If a part did not happen because the team lacked something, the lead can bring onto the team an agent the workspace already has, create a new agent reporting to it, write a skill, or build a workflow, and then run that part again. The room says "Before answering, I made what the work was missing:" with what was made. Each change is recorded under the lead's name.
  • Asks you for a connection. An agent never connects an account. If the work needs one, the room says "This needs a person to connect" the account, so connect it and ask again.

The lead builds and reruns once. If something is still missing after that, the room posts "This is as far as the team could take it." with what is still missing and what each part reported. If the budget will not cover the review, the room says so and posts what each part reported as it stands.

When a run ended without the lead answering the request, the card says so rather than claiming a result: Ended without an answer to the request.

Where to go next