Build with AI

You can describe an automation in your own words and let the AI assistant build it. The assistant uses the same triggers, steps and actions as the builder, so anything it makes can be opened and edited as a flow chart afterwards.

Two places to ask

Where	How
The automation page	Workspace → Automation → Add → write what you want → Draft with AI.
The AI assistant	Open the assistant anywhere in the dashboard and describe a standing rule, for example "whenever a payment over 100,000 comes in, text me".

Only admins can have the assistant create, change, run or delete automations. For anyone else, the assistant says so.

What the assistant does

1. Reads the catalogue. It looks up the triggers, the values each provides, and the actions available. It does not invent a trigger or a value.
2. Gathers what it needs. For example the user to notify when you say "email me", or the exact inputs of a Cashfin action it plans to use.
3. Drafts the flow chart. One trigger, then the steps, with a Filter, If / else or Switch where your words imply a condition.
4. Tests the draft. It runs a test with realistic sample values and shows the result in the chat as a flow chart with the path taken. Nothing is sent or changed.
5. Asks you to approve. A card shows the flow chart it wants to create, with Approve and Deny. Nothing is saved until you approve.

After you approve, the automation appears under Workspace → Automation, where you can open it in the builder.

Read the card before you approve

The approval card is your chance to check the automation. Look at:

• The trigger and any filter: is it limited to the records you meant?
• Who gets messaged: your team, or customers?
• The wording of each message.
• Whether it will be switched on. Ask the assistant to create it switched off if you want to review it in the builder first.

If something is wrong, click Deny and tell the assistant what to change.

Write a good request

Say	Example
What starts it	"When an invoice goes overdue"
Any condition	"only if the balance is over 20,000"
What should happen, in order	"notify me, then create a task for the owner due tomorrow"
Who is involved	"email me", "the lead's owner", "everyone"
Exact wording, if it matters	"the SMS should say ..."

A request with all five gives a draft that needs no changes. If you leave something out, the assistant chooses a sensible default and tells you what it chose.

Examples

When a new lead comes in from Facebook with a budget over 50,000,
notify everyone and give the owner a task to call within a day.

If I get a payment of 100,000 or more, have AI look at the transaction
and text me what it found and anything risky about it.

Every Monday at 9am remind the team to review open deals and
overdue invoices.

When a customer leaves a product review, draft a reply for me to approve.

Change, pause and explain

The assistant can also work with automations that already exist. Ask it to:

Request	What happens
"Show my automations"	Lists them, with whether each is on.
"Show me the overdue invoice one"	Draws it as a flow chart.
"Change the reminder to go to the owner instead"	Proposes the change on an approval card.
"Pause the lead follow-up"	Switches it off.
"Run it now for invoice INV-0151"	Runs it once for real.
"Why didn't it fire yesterday?"	Reads the recent runs and explains what happened.
"Delete it"	Asks you to approve the deletion first.

Every create, change and delete waits for your approval on a card.

Things the assistant will not do

• Give a discount by recording a payment. That would book money the business never received. It uses a credit note instead, unless you ask for the invoice's discount field.
• Send an email with a subject and no body. Every email step gets a complete message.
• Use a value the trigger does not provide. If the draft needs information the trigger lacks, it adds a step to look it up.

After it is created

An automation the assistant built is an ordinary automation. Open it under Workspace → Automation to edit it in the builder, test it with different values, and read its runs. See Runs and history.