Documentation Get help

Add an action

An action runs each time one of your objects is created, changed or deleted, like reading a new HubSpot deal and linking it to its Work. You choose what starts it, who or what runs it, what it can reach and how far it can go.

You need Manage actions. Ask your Flowstate admin.

Choose who runs it

Run byWhat you setChoose it when
Ready-made agentA few settings and a line or two of your own. Flowstate writes its instructions and chooses its model.One of Flowstate’s agents does the job. It’s the quickest start.
Your own agentThe model, and what it should do in your own words.The job needs judgement, like reading a deal, and no ready-made agent fits.
CodeTypeScript you write in the editor.The rule is exact, like “if this is empty, ask, then set it”. Code uses no AI, so it has no AI spend, and it does the same thing every time.

Ready-made agents

AgentWhat it doesSettings
Common work attribution agentFinds the Work an object belongs to and links them. Asks when two fit.When two Work items fit, When no Work fits, Match on
Work resourcing requirements agentReads a record of upcoming work, such as a deal from your CRM, a statement of work or a planning page, and writes down the people it needs: roles, how many, and the profile values they must hold.How many people, Roles
Team profile population agentReads a document about a person, links it to them and fills in their profile. Asks when it is unsure who it is about or when the profile disagrees.When it is not clear who it is about, When the profile says something else, New values for a list

Most settings let you choose Ask me, so a person decides the cases the agent can’t.

An agent sends the object it’s working on, and what it reads through its access, to an AI model. Data sent to AI models is covered by Flowstate’s enterprise agreements with the model providers, and isn’t used to train their models.

Add the action

  1. Go to Organisation → Modules → Ontology platform, open the Actions tab and select Add action.
  2. On the Build tab, give it a Name that says what it does, such as “Link new deals to their Work”.
  3. Under Run by, choose Ready-made agent, Your own agent or Code.
  4. Under When, choose the type in One of these, such as Deals, and tick what starts it under Is: created, changed or deleted.
  5. To run it only for some objects, select Add condition under Only if. Choose a Property, how it’s Compared, and a Value. For example, only when Deal stage is contractsent. With no condition it runs Every time.
  6. Fill in what the runner needs. See below.
  7. Set what it can reach on the Access tab, and its Limits. See Set an action’s access and limits.
  8. Try it on one object.
  9. Select Save.

A new action is on from the moment you save it. To save it without it running, select Switch off, the power button, before Save.

For a ready-made agent

  1. Under Agent, choose one.
  2. Under How it behaves, choose each setting.
  3. In Anything else it should know, add a sentence or two about your data, up to 2,000 characters. For example: “Our deal names start with the client’s short code.” It’s added to the agent’s own instructions, which stay fixed.

Model shows the model Flowstate chose for the agent, and its rate.

For your own agent

  1. Under Model, choose Claude Sonnet 5.5, Gemini 3.8 Flash, Gemini 4 Carbon or Gemini 4 Argon. Each shows its price per million tokens, read and written. See Model rates. Some Anthropic models are turned on for each organisation separately. If you want one that isn’t on for yours yet, ask your Flowstate account manager to turn it on. Calls to AI models may be processed outside your organisation’s region.
  2. In What it should do, brief it the way you’d brief a new colleague, up to 20,000 characters. It already knows your types, what each property means and what it may change, so say what should happen, not how your data is laid out.
  3. Check What it can use. Select Change what it can reach to open the Access tab.

A brief that works well says what to do, when to ask a person and when to stop. For example: “Read the deal and find the Work it pays for. If two pieces of Work fit, ask which. If none fits, say so and change nothing. Then finish.”

For code

Write it in the editor on the Build tab. See Write a code action.

Try it on one object

Select Try on one object, the play button beside Save. You can try an action before you’ve saved it. Flowstate runs the action once on one of the type’s objects and shows each step it would take and what it would cost. Nothing is changed: a step that would change something shows as Would change, Would link or Would ask a person.

A try uses the model like a real run, so it costs AI spend. Tries show as Tries in the action editor on the Usage tab.

Switch it on or off

Select Switch on or Switch off, the power button beside Save, or use the action’s switch in the On column of the Actions tab. While it’s on, it runs each time one of its objects is created, changed or deleted as you set under When.

A run still waiting when you switch the action off is skipped, and shows Skipped: the action was switched off.

Delete an action

  1. Open the action.
  2. Select Delete action from the menu beside Save.
  3. Flowstate asks you to confirm. Select Delete.

The action stops running. Runs waiting to start or waiting for an answer are skipped. Past runs and what they cost stay.

See your actions

The Actions tab lists each action with When it runs, who it’s Run by, Runs today, AI spend this month, how many runs Need you, and whether it’s On. An action can also show:

StatusWhat it meansWhat to do
Paused at this action’s monthly limitIt reached a limit on its Limits tabRaise the limit, or wait for next month
Paused at the workspace’s monthly limitYour organisation reached its monthly limitSee Usage, billing and model rates
Waiting for access to an appIt’s allowed to change something in an app that hasn’t allowed Flowstate toSee Let an action change things in the app
Stopped: something it uses is goneA type, property, model or app connection it names was removedOpen it, fix what the message names, and save

Each saved change makes a new Version. A run keeps the version it started with.

If something’s not right

Save says what’s wrong. The message names the part, like Access: a property it names isn’t there any more. Fix that part and save again.

“Someone else changed this action”. Select Reload to see their version, then make your change again.

“The model has no price yet”. Choose another model. Flowstate only runs a model it has a price for.

Runs with an Anthropic model fail at once with “The model didn’t answer”. If a run fails at its first Asked the model step, the most likely cause is that the model hasn’t been turned on for your organisation yet. Contact your Flowstate account manager to turn it on, then select Run again on the failed runs.

The agent asks too often. Write clearer meanings for the properties it reads (see Say what a type and its properties mean), or add a sentence about your data under Anything else it should know.