Set an action’s access and limits
An action can use only what you allow on its Access tab, and it stops at the limits on its Limits tab. Give it the least it needs for the job: it’s easier to add access later than to undo a change it shouldn’t have made.
You need Manage actions. Ask your Flowstate admin.
Access
Open the action and select the Access tab.
In your ontology
Each of your types has a row. Tick what the action may do with that type’s objects.
| Box | Lets the action |
|---|---|
| Read | Read and search its objects |
| Create | Create new objects |
| Change properties | Change the properties you tick. Open the row to choose them, one by one. |
| Link | Link its objects to others, through the links you’ve set up |
| Delete | Delete objects |
Only properties you’ve added can be changed by an action. The others show why:
- Flowstate’s own. Actions can’t change it.
- Changed in HubSpot only: it comes from the app. To change it there, allow one of the app’s operations below.
- Comes from the file only: it’s part of an uploaded document.
An action only changes what’s in front of it. Even with access to a type, an action can change only the object that started the run, objects linked to it, and objects the run itself created. An agent reading one deal can’t be steered into changing a different person or deal.
In our example, the deal-linking action needs Read and Link on Deals, and Read on Work. Nothing else.
In your apps, directly
Each connected app lists the operations an action can use in it, such as create_note on HubSpot, with what each does: reads, creates, changes, links or deletes. Tick Allowed for each one the action needs.
An operation that changes something in the app also needs your organisation to allow Flowstate to change things there. See Let an action change things in the app.
Nothing else
Nothing else is reachable: no internet, no other workspace, nothing inside Flowstate’s network. If a run tries something it isn’t allowed, the step shows Wasn’t allowed and nothing is changed.
Limits
Open the action and select the Limits tab. Amounts of money are in US dollars.
One run
| Limit | What it does | Starts at |
|---|---|---|
| Stop at an AI cost of | Stops an agent’s run when its AI cost reaches this amount. Agents only. | $0.25 |
| Stop after | Stops the run after this many seconds, up to 900. | 60 seconds for an agent, 30 for code |
| Memory | The most memory code may use: 128, 256 or 512 MB. Code only. | 256 MB |
| If it stops | Mark it failed and show me, or Try again once, then show me | Mark it failed and show me |
This action, each month
| Limit | What it does | Starts at |
|---|---|---|
| AI spend | The most the action may spend on AI in a month. Agents only. | $50 |
| Compute | The most time, in minutes, its runs may work in a month | 60 minutes |
| When it reaches a limit | Pause this action and tell me, or Keep going and tell me | Pause this action and tell me |
Under each monthly limit you see how much it has used so far this month.
Your organisation also has monthly limits across every action, which Flowstate can raise. See Monthly limits.
Choosing sensible limits
- Try the action on one object and note its AI cost and Compute.
- Set the run’s AI cost limit to a few times that, so an unusually long object still finishes but a runaway one stops.
- Multiply the cost of a run by how many objects change in a month for the monthly AI spend. See Estimate what a run costs.
If something’s not right
Runs fail with “The action isn’t allowed to do this”. Its access is missing something it tried. Open the run to see the step that Wasn’t allowed, then tick what it needs.
Runs fail with “Reached its AI cost limit” or “Reached its time limit”. The object needed more than one run allows. Raise the limit, or narrow When so it runs on fewer objects.
“Type an amount in dollars, like 0.25”. Money limits take a plain number of US dollars.