Actions
Routine tasks done with the user, and the last click is theirs
Asked to do something, Skavelo doesn’t stop at explaining. It opens the right screen, fills in the details the user gave, and stops on the final button for them to check and click. With actions your team sets up, it can run a request for the user once they approve it.
Check the details, then click Send invoice.
HelpSend a reminder for INV-1042
Send invoice reminder
From “do it for me” to done
Step 1
The user asks, with details
For example: create an invoice for Harbor & Co for 500 EUR, due 30 November.
Step 2
It opens the right screen
Clicking the links, tabs and buttons on the way, like New invoice. Or it proposes an action your team set up.
Step 3
It fills in what they gave
Each detail goes in its field. Fields they gave nothing for stay empty. An action shows every value it will send.
Step 4
The user makes the last click
Nothing is saved or sent until they click your final button, or Run action.
Help that stays in the user’s hands
No setup for forms
Form filling works from the screens Skavelo learned, on every plan, with standard text, number, date, select and checkbox fields.
Never invents details
Fields the user gave nothing for are left for them. For an action, Skavelo asks for anything missing before it offers it.
Leaves the risky parts alone
It won’t click save, send, delete or pay on the way, and never touches passwords or file uploads. For deleting, cancelling or billing, it explains how instead.
Actions wait for approval
The user sees the action and every value first. The request is sent only when they click Run action; Cancel sends nothing.
The user’s own permissions
Actions go from the user’s browser to your app with their session, so they can only do what the user already can.
Off until you turn them on
New actions start switched off, only owners and admins can create them, and every outcome is recorded in Conversations.
Form filling or actions
When a switched on action does the task, Skavelo offers the action instead of filling in the form.
| Compared on | Form filling | Actions |
|---|---|---|
| Setup | None | Your team defines each action, or imports them from OpenAPI |
| How it works | On your own screens, so your app’s validation still applies | Calls your API from the user’s browser |
| The final step | The user clicks your button, like Send invoice | The user clicks Run action |
| Plans | Every plan | Your first one free, up to 5 on Starter, unlimited on Growth |
Questions
Set it up with Creating a skill in the help center.
- Does Skavelo click Save or Send for the user?
- No. It stops on the button that finishes the task and highlights it, and the user checks the details and clicks. On the way it won’t click anything that saves, sends, creates, deletes, pays or confirms.
- Which plans include this?
- Form filling works on every plan with no setup. Actions call your API: your first lookup or action is free, Starter has up to 5 switched on, and Growth and Enterprise are unlimited.
- Which fields can it fill?
- Standard form fields: text, numbers, dates, select dropdowns, checkboxes and text areas, in React, Vue and similar apps. Custom-built dropdowns and date pickers are highlighted for the user to choose.
- Can an action do more than the user could?
- No. Actions run from the user’s browser with their own session, only to paths on your app, so your API decides what they’re allowed to do.
- Can text on a page trick it into running something?
- No. Text Skavelo reads on a page, in a document or in data a lookup returned is treated as information, never as instructions. It offers an action only when the user asks for it.
See Skavelo fill in a form on your own product, before you add any code.
Start free