Actions
An action is the unit of work in Flowra. Everything else in the product is either attached to one or created out of one.
Open in Flowra/actionsActions
StatusIn progressPriorityHighDueThuTime and reminder14:30 · 30 minutes beforeChecklist3 of 5Every change is written into this action's own history.
What this is wired to
My actions: everything by urgency
“My actions” shows work assigned to you, work you created, and personal work with no assignee. You don't set the order; it comes from each action's due date and priority, and the list groups itself.
At the top of the list there are two views, “List” and “Calendar”, the buttons “All”, “Personal”, “Workspace” and “Project”, and one button for each workspace. “CSV” exports the same list with the current filters, and “Connectors” opens the connections page. Press and hold a row to open its quick preview.
- Overdue
- Today
- In progress
- Blocked / waiting
- Review
- Inbox & planning
- No assignee (unowned team work), and at the end “Finished” with a “Report” link
Creating an action: one line or the full form
In the box at the top of “My actions”, just type the title; the action goes to the inbox and you complete it later. In the same box you can also set a due date, assignee and attachment before “Add task”. In a workspace, this box is “Quick task”.
The full “New action” form takes the workspace, company, project, title, starting status, priority, assignee, due date with time and reminder, repeat, description, attachment and finance context, and is saved with “Create task”.
List, board, timeline and workload
A workspace's actions have four views. The board shows the workflow columns: inbox, ready to start, in progress, blocked, review and done. The timeline shows six weeks, and the workload counts each member's open and overdue work and flags anyone over capacity; click a person to see only their work.
Company, project and member are filtered in the page address, so you can share a link to any filtered view. The workspace owner can create a “New board”; deleting a board doesn't erase the status of its actions, and they come back when you turn it on again in “Workflow”.
Planning assistant
When a project is selected, owners and editors see “Assistant” on actions. Write what work is ahead and name teammates with @. The assistant asks when it has to be finished, who is working on it and how high the overall priority is; with AI it may ask a few more questions.
The result is rows with a title, assignee, due date, priority, description and subtasks. Delete a row or hit “New row”, and with “Create and assign tasks” they are all created and assigned at once. Without an AI plan, the assistant works with ready-made questions and plans.
What an action is made of
A title, a description, an owner, a priority, a status, a due date, labels and a checklist. So far this is like any other tool. The difference starts where an action can reference a project, a meeting, a file, a contract and a transaction, and show each of them on its own page.
Each action's page also has a “Related docs” section: the Knowledge pages linked to this action, plus a button to create a new doc or attach an existing page.
Due date, time and reminder
The due date is optional, and so is the time. Next to the day there's a time picker that lists the day in 15-minute steps, with a box on top that understands any typed time: “9” means 9:00, “930” means 9:30 and “14:25” is just 14:25, with Persian or Latin digits. On a phone, the same list opens from the bottom of the screen.
The reminder is one of these: no reminder, at the due time, 10 or 30 minutes before, one hour before, or one day before. If you don't set a time, the reminder comes at 9 AM that day. Reminders arrive through the notification bell and, if Telegram is connected, through Telegram.
- Tap the due date and pick a day
- Pick a time from the list or type it
- Tap one of the reminder options
- Any later change to the day or time recalculates the reminder
Status and priority
The status shows where the work is, and the board is columned by it. Priority is separate from status, because «urgent but not started» and «low priority but in progress» both exist, and collapsing them into one field destroys information.
An action with a due date goes on the calendar, and if an external calendar connection is set up, it goes there too. An action without a due date has no place on the calendar and is deliberately not synced.
Action story
Every change to an action - a status moving, an owner being added, a checklist item closing, a comment being posted - is written into that action's own history. Opening the detail page is recorded as a view too.
That history is read at /actions/[id]/story and exists to reconstruct «who did what, when», not to count things. Which is why no branch that changes an action is allowed to skip writing to it.
Assigning work to others
When you assign an action to someone, an interactive card lands in your direct chat with them and a notification goes out. A timed action assigned to someone else must fall within their working hours, if they've set working hours in their calendar settings; otherwise the server tells you right away.
Who sees what
Access to an action follows its scope. A personal action is yours alone. An action inside a project is for whoever can see that project. A workspace-level action is for the members of that space, and a member's role decides whether they can view it or edit it.
That check happens on the server, not by hiding a button. If somebody sends a request for an action they have no right to, the answer is a refusal even if the interface never showed them the button.
Actions that create themselves
Some work should not depend on anybody remembering it. A payment past its due date, or an obligation that has come round, raises its own follow-up action. That creation is idempotent and keyed, so opening the page again does not make a duplicate: exactly one, not zero and not ten.
- A payment or an obligation passes its due date
- The engine raises a follow-up action keyed to that item
- The action appears on the board and the calendar like any other
- Closing it closes the loop, and running again creates nothing new
Teammates' working hours and leave
An action with a time can't be assigned to someone outside their working hours or on a day they're on leave; Flowra refuses it and suggests their free times in the form. An action without a time is accepted on a leave day but gets a warning. Assigning work to yourself is never restricted.
Subtasks, attachments, repeat and finance context
Every subtask is a full action of its own, with an assignee and a due date. Upload an attachment, pick one from My Files or record a voice note; every attachment is saved in My Files too. Repeat can be weekly, monthly, quarterly or every few days, and when one round is done, the next one is created automatically.
The finance context connects an action to money: a payment with a due date, expected income, a required expense, needs approval, transaction review or invoice follow-up, with any account and transaction you choose.
Chat and mentions
“This action's own thread” takes text, voice notes and files. Type @ and a person's username; suggestions show members of the same workspace first, then people you share work with. Only people who can see the action get notified, so a mention never shows work to someone who shouldn't see it.
Action connectors
In “Action connectors”, Google Calendar and Telegram are available: Google Calendar keeps actions with a due date in a separate calendar, and Telegram sends each action as a card with done, start and postpone buttons. Jira, Trello, Asana, Linear and several other services are “Soon”; they don't connect anything yet, and “Notify me” only lets you know.
On phones
On your phone it's the same pages: quick add is at the top of “My actions”, views switch with buttons, and each action's page opens full screen so the bottom bar doesn't get in the way.