Coming Soon: Finance Workflow Automation Builder by Fuelfinance

‍Show the agent how your team does the work today. Get back workflows you can read, test, run, and change, all on one screen.

Today, getting a new process into Fuel means one of two things. Someone writes prompts for each agent, or you wait for one of our finance engineers to set it up. Workflow Builder removes both. You describe the process the way your team runs it, and the agent builds it: the workflows it needs and the agents inside each one. That’s what finance workflow automation should look like when the finance team does the setup itself.

Customers and partners have been asking us for this for a while. Register for the Finance Workflow Automation Builder webinar on December 3, 2026, at 10 am ET to be among the first ones to see and soon try it on one of your own processes.

What the Finance Workflow Automation Builder is

The workflow builder takes a description of how a finance process works today and turns it into a finance event that does the work and stops for your approval at the steps that need it. Everything it builds follows one structure:

• Event: the job your team does, like the month-end close or the morning bank reconciliation. An event runs on your schedule.
• Workflows: the parts that the job splits into. A close might become six workflows, from integrity checks and revenue recognition to the balance sheet and the close report.
• Agents: the steps inside each workflow. Every workflow is an agentic workflow: a chain of Fuel AI agents, each doing one step.

You give it what you already have: files, a written or spoken description, your company context. The agent lays out the event as a schema. You correct it on the schema, test it on a past period, and run it.

What comes out is a working AI agent workflow, not a mock-up. Every agent has its own prompt, code, connections, and rules, and the finished event lands in your account ready to run. As in every other Fuel workflow, calculations and matching run as code, and anything that would change your books still stops for your approval.

Already know which finance process you'd automate? Request a personal demo now

One screen to build and run

There’s no separate build page and run page. The chat and the schema stay on one screen, so you build, run, and answer the agent without switching views. When a run finds something no rule covers, say a large transfer with no matching entry, it stops at that step on the schema and asks you in the same chat.

How it works

You work with one agent in one chat per event, and that chat keeps the full context from start to finish.

1. ‍It starts with collection. You can upload inputs, outputs, process notes, diagrams, or agents you’ve already built. You can also describe the process in text or by voice, or pick a typical job from a list. The agent asks the questions that matter for that type of process. It turns Excel files, call transcripts, voice notes, and screenshots into one structured picture and comes back to you on anything still unclear. Nothing gets built until that picture is complete, so financial process automation here starts from how your team already works.‍
2. Then it lays out the flow. Before building anything, the agent walks you through the big picture: which workflows the event needs, how they connect, and which can run side by side. Then it goes through each workflow in detail: its agents, what each one does, and the rules it follows. You approve the flow or change something before the build starts.‍
3. Then it builds. The agent builds each workflow from that plan, one agent at a time. It only asks where it isn’t sure, and its best guess is already selected, so most answers take one click. If it hits a gap, say a data source you haven’t connected, it stops and asks, then picks up again once you answer.‍
4. Then you run it, and the chat stays open. Run the event now or on a schedule, like the 3rd of every month at 06:00. You can comment on a dry run, change a rule after a test, or send a correction from Slack. Only the affected steps are rebuilt, the version number goes up, and you get a list of what changed.

What you’ll be able to do with Finance Workflow Automation Builder

The objection we hear most about finance automation is the black box: nobody can say why the agent did what it did. Our workflow builder is designed so every decision has a rule and a source behind it, and every change is logged.

Before you build

The agent uses your company context to suggest which processes are worth automating, along with the problem each one solves. You can start from that list or from a typical job: AP, bank reconciliation, close, or cash application. You can also describe any other process yourself. Your team gets from nothing to a running event without waiting in a queue, and a finance engineer joins only if you want one.

While it builds

• The process appears as a schema, Inputs → Process → Output, and fills in as each agent is built. It stays with the event afterward for testing, monitoring, and handover.
• The schema flags what to look at: blockers, the agent’s assumptions, and its latest changes. A missing data source shows up on the exact input that needs it.
• Click any agent to see what it does, what data it uses, and the rules it follows. Change rules in plain language, and connect, swap, or remove data sources the same way.

Before you trust it

Pick the output (an Excel file, a report, a Slack message, or an email) and who gets it. You can preview a generated example before launch, or add another output just by describing it.

Then run the event on a month you’ve already closed and compare it line by line with your team’s own work, with the rule behind each decision shown. If you’d rather not switch over in one go, run it in shadow mode first.

After launch

• A log, one tab away from the chat, keeps every agent action and every change your team made.
• Save an unfinished setup and come back later, delete it, or duplicate a finished workflow for another entity.
• What the agent learns (sources, rules, your answers) carries into every event you build next, so the second one takes less explaining than the first.
• Agents and agentic workflows you already run in Claude, Zapier, or Excel macros can move into Fuel, where they get a schema, access controls, and the same log.

See Finance Workflow Automation Builder first

Our Finance Workflow Automation Builder is coming soon. Join the webinar to see it live.