Flow Builder
Use the Flow Builder skill to turn your own transaction data into Fynapse Business Events with a Flow.
The skill maps your transaction entity to Business Events, adds a script or routing step only where one is needed, previews the Flow with Fynapse until it is valid, and publishes it only when you confirm.
Example prompts
Once installed, describe the transactions you have and what they should post as.
Map transactions to Business Events
Get our supplier invoices posting as Business Events.
Create a schedule
Spread each prepayment over its term as monthly amortisation events.
Route by type
Use a different event type for credit notes than for invoices.
Troubleshoot a Flow
Why isn’t my billing Flow producing any Journal s?
You can name the transaction entity, the event types, and any values that need to be derived, such as dates, amounts or codes.
Install
Install the Flow Builder skill from the Fynapse skill collection:
The Fynapse MCP Server must also be connected to your AI client. The skill uses the MCP Server to read your entities and configuration and to save, preview and publish the Flow.
What you’ll get
The skill builds the Flow with you in your conversation and gives you:
- A mapping table showing each Business Event attribute, its source and any transformation
- The Flow, explained step by step and laid out ready to view on the canvas in the Fynapse UI
- Preview results from Fynapse, with every problem fixed before you are asked to publish
- A saved draft, and a published Flow only after you confirm
- The Business Events and Journal s to expect from a test transaction, and a check against what actually posted
The skill uses the fewest steps that work: an Input, a Script only where a value has to be derived, a Condition only where records must take different routes, and the Accounting Engine and Journal Processor steps that turn events into Journal s.
A published Flow runs for every new record of its input entity. Review the mapping and the preview results before you confirm, and test with one transaction before loading a full file.
Scripts
Where values have to be derived, the skill writes a Python script step. Typical uses include:
- Building several Business Events from one transaction, such as an amortisation or instalment schedule, with any rounding difference placed on the final period
- Calculating dates, such as month ends or a number of months after a start date
- Choosing an event type from the transaction’s data
- Looking up values in your reference data
- Rejecting a transaction with a clear message when it is incomplete or invalid
Safe publishing
The skill previews every Flow before saving it and asks before publishing or archiving. If another published Flow already runs on the same transaction entity, it stops and asks how you want to proceed, because two Flows on one entity post every transaction twice.
Things to know
Flows must be turned on for your tenant in the Fynapse UI under Feature Flags. The skill cannot turn them on for you.
Business events post only when they pass through the Accounting Engine and Journal Processor steps. The skill does not write Business Events with a Target step, because those events are stored but never posted, unless you confirm that is what you want.
Preview checks the structure of a Flow but does not run its scripts. The first real transaction is the test of a script, which is why the skill recommends testing with one transaction after publishing.
The event types your Flow produces must already exist with posting rules behind them. If they do not, the skill tells you before publishing; use the Subledger Configuration skill to add them.
CSV files for a transaction entity use the attribute labels in the header row, not the attribute names, and need a unique value in the ID column.
A Flow cannot be renamed after it is created.