Automate routine work with scenarios
A scenario is a standing instruction: “every morning, check what is running low” or “when a sales report arrives, import it”. It runs as you, with your current permissions, and it leaves drafts and proposals. It never changes your data without a person.
Create a scenario
Section titled “Create a scenario”- Open Overview → Skipper and switch to Scenarios. (If you don’t see it, your plan or role doesn’t include automations.)
- Click New scenario.
- Give it a Name and choose When it runs:
- On a schedule: Daily at a time on your workspace’s clock, or Every few hours (from 1 to 168).
- When a file lands: a file arriving in the Inbox. You can limit it by how the file arrived (upload, chat, email, Telegram, Slack), the sender, the file type and extension, words in the file name or subject, and, for a spreadsheet, the columns it has. Unless lists exceptions that leave a file alone.
- Choose What it does:
- Import a sales report into a sales feed channel. Lines Keelvy can’t match go to the feed’s review queue.
- Send a sales digest: totals, best sellers and the change against the previous import, in your notifications.
- Plan work for low stock: a bought material gets a draft purchase order, a made one a planned production run plus drafts for what it lacks. Nothing is confirmed, started or sent.
- Ask the assistant: Skipper follows your instruction in the rule’s own chat. Anything it wants to change waits there as a proposal.
- Click Save rule.
Before you rely on a file rule, use Test on a file: pick a file in the Inbox and see which conditions it meets. Nothing is saved and nothing runs.
Run it and read the result
Section titled “Run it and read the result”Run now queues a run. A file rule runs when a matching file lands. Run history shows each run with its outcome (Succeeded, Failed, Skipped) and what it produced, such as “Draft purchase order 1” or “Imported 40 new lines, 3 already seen”. A run that makes drafts also notifies you.
Who the rule runs as
Section titled “Who the rule runs as”A rule runs as its owner, under the owner’s roles at that moment. The owner is whoever last changed when the rule runs or what it does. If the owner loses a permission, the next run fails and says which one. A rename, the on-off switch or Run now doesn’t change the owner.
Turn a rule off
Section titled “Turn a rule off”Switch On off to pause it, or archive it; an archived rule can be restored. Nothing is deleted.