Act · Workflows
Automate the follow-up. Try it first. Nothing is sent.
nexibi has its own automation engine and visual flow designer, in the same product as your dashboards and your assistant. Your company's owner builds each flow there: pick how it starts, add steps, try it on your real data without sending a thing, and add a step where a person must say yes.
try it first: nothing is sent
The late orders are read from a sample web-API connection.
- 1Each step says what it does
- 2Try it first: nothing is sent
- 3Waits for a person's yes
Build it on a canvas.
A designer of our own
Steps are cards joined by wires, with undo and redo, Tidy up, a minimap, notes, and copy and paste.
A step panel
Search for a step, or pick from groups: AI, Action in an app, Change the data, Files, Decide and branch, Tell or ask a person. Your own connections show as apps, and likely next steps are suggested.
Plain settings
Each step's settings are a form with hints and examples; rarer options sit behind "Add an option". Drag a field from what came in onto a setting, or write a formula; a broken formula is refused with a sentence saying why.
It checks itself
Each step says what it does in one sentence on its card. Publish checks the whole flow and lists what to fix, step by step.
Start from a ready flow
Starter flows in four groups: notifications, sales, finance and operations. A copy is yours, starts switched off, and lists what you must choose before it runs. Save your own flow as a company template, with its connections and people taken out.
Who builds
Your company's owner builds and changes flows. Members can see a flow that is shared with them, and run it when it is shared with Edit. An owner can switch the Flows app off for the company: its pages say so, nothing is deleted, and flows on a schedule keep running.
Suggested next
From a connected system
To choose before it runs
- the connection
- who approves
- the mailbox it sends from
Company templates
- 1Starts switched off
How a flow starts.
- On a schedule: every day or week at a time you choose, or several times a day, down to every 5 minutes, by the clock of the city you pick. After an outage, a missed run runs once, is skipped, or catches up: you choose.
- When someone presses Run, and types the rows it needs, if any; they are checked first against what the flow takes.
- When another system calls its web address. The caller proves who it is with the address's token, plus a secret header, a username and password, or a signature on every post. It gets its answer at once, or when the flow finishes.
- 1A schedule, a button or a call
Steps that stick to the facts.
Read and decide. Read a list from a connected system with a web API or a ready-made connector, every page of it, or a page each run starting where the last one stopped. Then If, Switch, Keep, For each, Merge, Wait and Stop. Shape the rows: set and rename fields, split, count and add up, sort, take the first few, look values up in a small table, and let through only the rows it has not seen before.
Hello Sam, order SO-10482 for Quellmark Foods is 23 days past its promised date…
- 1Stops rather than guess
AI steps
- Draft with the model: a message for each row, from that row's own figures. It is told to invent nothing, and it stops rather than send a message that is missing a required field.
- Write from a template: your own words, no AI at all, so the same row always gives the same message.
- Sum it up: one paragraph for all the rows, such as a weekly digest.
- Sort into labels, with the reason for each label.
- Pull out fields from an e-mail, a text or a file, by rules first and AI second. A value from the AI must quote its source, or it is marked unchecked.
- Check the text for personal data, secrets and instructions aimed at an AI before it goes further.
- Switch by the model: let the AI choose the branch for each row, with an "Otherwise".
Choose the AI model for each step from the models your company has switched on, with a fallback.
For the technical
A Code step runs a few lines of JavaScript in a sealed sandbox.
Call any web address, signed in with a connection where needed, but only hosts your owner allows.
Run another flow as a step and carry on with what it gives back.
Documents in, documents out.
- Read a PDF or a scan on each row, as text, tables or named fields.
- Make a PDF, Excel, Word or CSV file from the rows, one per row or one for all, with money, dates and a total line.
- Fill your own Word or Excel template with each row's values. If a placeholder has no value, it stops and names it.
- Send it as an e-mail from your company's own Microsoft 365 mailbox when one is connected, or through our messaging service, with the files attached.
- Send to each row's owner and their team lead: one message per row, one digest per person, or a few messages and then a digest. Or prepare the message for a person to finish and send by hand.
- Files a run makes or receives are kept in your company's storage for 30 days by default, or 1 to 365 days if you choose.
Payment reminder.docx
One per row, as Word
Stop, and name it
30 days
- Customer
- Quellmark Foods
- Invoice
- INV-30418
- Amount
- $12,840
- Due
- 14 October
- 1Your own template, filled in
Try first, ask first, send once.
waits for a person's yes
- Try first. Try a flow first. Nothing is sent and nothing is changed. Each step that would leave the company says what it would have done.
- Test a part. Run one step, the steps before it, or from here, or step through one at a time. Pin sample rows on a step and build the rest without calling the system.
- Ask first. Add an "Ask someone first" step and the flow waits for a person's yes before it carries on. The approver reads each message as it will go out, and may rewrite only the fields the step allows. Name who decides: a person, a role or a team. A deadline never counts as a yes.
- Send once. Each item is sent or written once, even after a retry, a restart or the next day's run. A send that got no answer is marked "may have gone" and is not sent again on its own.
Hello Sam, order SO-10482 for Quellmark Foods is 23 days past its promised date.
- 1Waits for a person's yes
A brake on bursts
A step about to send or create more than 100 things in one run waits for a person's OK.
Only what your owner allowed
A flow writes to one of your systems only through the kinds of change your owner has allowed for that system, and every attempt is kept on record.
As a person
A flow runs as the person who owns it: it reaches only what that person may reach, and holds no passwords of its own.
A flow does what its steps say, so the assistant's asking does not cover it: it waits for a person at an "Ask someone first" step, or where a change to a system is set to need approval.
Runs you can read and fix.
| Order | Customer | Days late |
|---|---|---|
| SO-10482 | Quellmark Foods | 23 |
| SO-10495 | Fenwright Builders | 12 |
| SO-10511 | Lumora Hotels | 4 |
| Order | Customer | Days late |
|---|---|---|
| SO-10482 | Quellmark Foods | 23 |
| SO-10495 | Fenwright Builders | 12 |
| SO-10467 | Halvard Kitchens | 9 |
Runs Failed today · 1
- 1Retry from the step that failed
Each run has its own page: the flow drawn with how many rows went each way, and what went in and came out of each step.
See what each run did, step by step, and run a failed one again from where it stopped. Nothing it already sent goes out twice. Replay a run with the same starting rows, or cancel one that is running or waiting.
One page, called Waiting, shows everything waiting for you: approvals, questions and failed runs. Decide many at once, with one reason for the batch. Each request runs once even if two people press together, and nobody approves their own proposal.
When a run fails, gives up or needs a sign-in, the flow shows a notice and its owner gets one e-mail. The next run that ends well clears it.
Each step can be tried again 2 to 10 times, with a pause between tries. After the last try it can stop, skip the row, take an error path, or undo what the run wrote. A busy system is tried again later by itself. An error flow can run when a flow fails, and is told what went wrong.
Save a draft, or Publish. A draft never runs. Each publish is a numbered version with who and when; see what changed between versions and put an earlier one back.
Runs are carried out by background workers: if one stops, another carries the run on from its last finished step. A run can wait days for an approval or a set time, then carry on where it stopped.
Runs are kept for 30 days, and the newest 50 of each flow beyond that.
The Calendar shows when each flow runs next, beside your holidays and events.
It works with the other engines.
Analyses
Send one row of an analysis through a follow-up flow from its Act menu. Take into a flow the rows an analysis marked for action.
Analysis & predictionForecasts, predictions and plans as steps
A row per forecast point, per plan, or per record with its chance and reasons.
Analysis & predictionAI agents
One step, "Ask an agent", hands each row to one of your agents and carries on with its answer, or with the reason it could not finish.
AI AgentsThe assistant
Ask it to try a flow without sending, run it after you approve its card, or explain what a run did.
AI AssistantData connections
A flow reads and writes through the same connections, sign-ins and approvers as everything else.
Data connectionsCompany values
Keep values your flows read, such as a sales inbox or a tax rate, in one place.
Priced by runs, not rows.
A run is one time a flow runs, from its start to its end, however many rows it handles.
- Never a limit on how many flows you make. Test runs are listed apart, and never counted.
- Owners see runs, failures and AI use by flow and by day on the Usage page.
Who uses it.
Can it remind every customer with an invoice more than 30 days overdue, once I have approved the wording?Built with WorkflowsData connectionsFor finance Operations
What is waiting for my yes today?
One Waiting page holds the approvals, questions and failed runs from your flows.
Built with WorkflowsFor operations SalesCan each account manager get one morning digest of their own late orders?Built with WorkflowsData connectionsFor sales
What it does not do yet.
So you know before the demo.
- A flow cannot read a connected database today.It reads systems with a web API and the ready-made connectors.
- Starting a flow when mail arrives, when a form is sent or when a new file arrives is built, but not offered yet.
- Building or changing a flow by describing it in words is not offered yet.Flows are built in the designer.
- Reading Word, Excel and PowerPoint files in a flow is not offered yet; PDFs and scans are.
- Research on the web as a step is not offered yet.
- There is no catalogue of hundreds of ready app steps: flows reach your systems through your own connections.
- A run works for up to 5 minutes, or 60 seconds when pressed by hand.Time spent waiting for a person does not count.
- Code steps are JavaScript only, without packages.No text messages (SMS).
Bring the follow-up you still do by hand.
In the demo we connect one of your systems, and you ask the questions.