Triggers
Start from an event such as an overdue invoice, or run the workflow manually.
Workflow Automation
Workflow Studio turns a repeatable finance process into connected blocks. Start from a trigger such as an overdue invoice, send the follow-up, wait, decide, and stop for a person where judgment is needed. Every run is recorded.
workflows.eigennwaiting
workflow run
6 steps
1 pause | The follow-up runs on its own and stops where a person decides.
01
Invoice went overdue
02
Reminder sent, then waited
03
Paused for a person before the late fee
Visual
Build on a canvas from a library of blocks
Paused
Human checkpoints stop a run until someone decides
Traced
Every run keeps its status, steps, and trigger data
Recurring finance work depends on someone remembering it
Follow-ups, escalations, and late fees run on calendars and memory. When the person who tracks them is busy, invoices age and nobody can say which step happened.
Manual
Every reminder and escalation is started by hand
Inconsistent
Two overdue accounts get two different treatments
Untracked
Nobody can show which step ran, and when
How workflow run works
Follow-ups, escalations, and late fees run on calendars and memory. When the person who tracks them is busy, invoices age and nobody can say which step happened.
01
Build on the canvas
Pick a trigger, then connect communications, finance actions, and flow control from the block library. Validation flags missing or unreachable blocks while you build.
02
Test, then deploy
Run the workflow manually on a safe path, read the execution console, then activate it.
03
Watch the runs
Executions show each run's status and steps. Pauses wait for a person, and Outcomes report invoices resolved and run health.
What a workflow can do
Blocks cover the steps a receivables process repeats every week.
Communications
Send an email or an SMS to the customer, or notify your team.
Finance actions
Apply a late fee or escalate an account as part of the sequence.
Flow control
Decisions, routers, loops, parallel branches, subflows, and waits shape the path a run takes.
Human checkpoints
A Pause block stops the run with a message until a person resumes or cancels it.
Copilot
Ask the copilot to explain a workflow or propose an edit. You accept or reject each proposal.
Run history
Every execution keeps its status, steps, trigger data, and result.
Where this shows up in the week
Overdue invoice follow-up
Send a reminder when an invoice goes overdue, wait, then escalate if it is still unpaid.
Late fees with a check
Pause for a person before a late fee applies to a key account.
Team alerts
Notify the owner of an account when a step needs their attention.
Put the recurring work on a canvas
Build the follow-up once, test it, and let it run with checkpoints where a person decides.