Lesson 6 · 18 min
A flow is a task with several stages, with the state saved at each one. The gate is the stage that ends and pauses: the bot shows you what it did and waits for you. Approving, correcting, or rejecting is when you manage the work instead of doing it yourself.
Start lesson
Goal: put the gate in the right place in a flow and decide whether to approve, reject with a correction, or cancel.
The domain flow running in production in inemaccbot.
Scroll down: each step below lights up its part of the diagram.
The command creates a numbered flow (A#9) and a list of stages. Each stage has its own state; /status shows each stage and each audience.
The agent writes a script for each audience (young people, women…). You don’t want to lose this work if a later stage fails, which is why this is a flow, not a skill.
The phase ends, and the bot sends what it declared to show in the chat, then STOPS. You read it, make corrections, and save the avatars. The flow continues only with /pronto (or /aprovar, /ok).
After the gate come the costly phases or those with consequences: downloading the avatar video, assembling the reel, and delivering it to the channel. If one fails, /refazer resumes from that phase without redoing the text.
After what needs your eyes, before what is costly or public. A gate at the start has nothing to show; a gate at the end comes too late.
Click each block. The gate goes after the work you need to review and before anything that costs money or goes public.
Run the flow, read the text that stopped at the gate, and decide.
Illustrative browser simulation: nothing is generated or published. The text with the error is intentional.
Each command does something different. Mixing them up costs work.
/pronto A#9 releases the gate. /aprovar, /aprovado, and /ok are synonyms, and A#9, a9, and A9 refer to the same item.
Without a reference, /pronto releases the flow when only one is waiting; with several, it lists them.
When the flow declares gate responses, you can reply with more than "yes": enter a word, such as reprova, followed by what to correct. The bot runs the domain command, and the phase REOPENS with the new material.
It's the "redo it and show it to me until I approve" process. Each flow declares which responses it accepts; /ajuda <fluxo> shows which ones.
/refazer A#9 [público] resumes from the phase that FAILED, without redoing earlier phases.
This doesn't work for a phase stopped at the gate: it hasn't failed; it's waiting for you. To continue, approve it or reject it with a correction.
/cancelar A#9 stops the entire flow and removes it from /status. Use it as a last resort: if you want to change one text, you lose every phase.
To permanently delete the flow's files, use /limpar A#9. It only shows what would be deleted until you type confirmar.
Practice with | sombra before spending anything.
/promoavatar Don’t start by learning tools | shadow # shows stage × audience × queue and does NOT enqueue anything /promoavatar Don’t start by learning tools --alvo=jovens /status /status A#9
/pronto A#9 # approves and continues /refazer A#9 jovens # resumes from the stage that failed /cancelar A#9 # stops the entire flow /limpar A#9 # shows what it would delete /limpar A#9 confirmar # actually deletes
{ "id": "plano", "kind": "function", "tarefa": "cli.rodar",
"comando": "bash {{repo}}/musicavideo.sh plano {{input}} --bruto",
"pausa_apos": true,
"portao": { "mostrar": ["{{artefato:plano}}"] } }The stage declares in portao.mostrar what goes to the chat: text goes in the message, audio and images go as files, and video goes as a link (a video lasting several minutes exceeds Telegram’s 50 MB limit).
Runs to the end without stopping for approval, but still sends to the chat what each gate would show. Use it only when you already trust that flow, and never before publishing something you haven’t read.
The project documentation records the risk: approving several flows at once without checking can trigger pointless waits (the stage that downloads the avatar waits up to 90 minutes before failing when the video hasn’t been recorded). Check before approving.
Use a flow with a gate. If /promoavatar isn’t configured yet, start with | shadow.
Run a flow with a gate (such as /promoavatar), first with | shadow to see the stages. When it stops, read what arrived in the chat, make corrections if needed, and only then send /pronto.
Done when: you rejected or corrected at least one text before approving.
Domain flows: promoavatar3 (active) and promoavatar (frozen).
The explanation appears after your answer.
Question 1 of 4
Where should the gate go in a video flow for social media?skill
Question 2 of 4
The flow stopped at the gate with incorrect text. You send /refazer A#9. What happens?
Question 3 of 4
What is | sombra for?
Question 4 of 4
In the simulation, what shows that you’re managing, not just using?
Choose an option. The explanation appears after you try.