This article explains what an automation is and how to create, change and undo one.
What an automation is
An automation is a job you hand to Tensor Autonomous. A run is one time it does that job.
For example, "reply to booking requests" is an automation. Each booking request it handles is one run.
Create an automation
You have three ways to start.
Describe it
- Write the job in plain words.
- Say what comes in, what should happen, and what a finished result looks like.
- Run one example and read the receipt.
Show it once
- Do the job once in your own browser. There is nothing to install.
- Go through it the way you normally do, start to finish.
- Tensor repeats the steps you showed. Run one example to confirm.
Start from the Library
- Open the Library and find a ready-made automation for your industry.
- Start it with one click.
- Run one example and correct anything that does not fit your business.
How work reaches an automation
- By email. Forward an email to your workspace, including the notification emails a website form sends.
- By request. Type a request in the app.
What happens during a run
- Tensor reads what came in and prepares the work.
- Before it writes or sends anything, it asks you. A reply or message it writes always waits for approval.
- You approve, decline, or correct.
- The run finishes and leaves a receipt: what came in, each step, what you approved, and the result.
If information is missing or conflicts, Tensor stops instead of guessing.
Change an automation
The simplest way to change an automation is to correct a run. The correction updates the instructions as a new version, and later runs follow it.
Versions and rollback
Each automation keeps versions. If a change makes results worse, roll back to an earlier version.
How many you can have
Your plan sets two numbers:
- Automations running at once: 3 on Starter, 10 on Operator, 30 on Operations Team.
- New automations a month: up to 20, 60 or 150. Repairs and changes to existing ones do not count.
Your plan includes new automations each month; each one beyond that is 5 credits. Fixing or changing an automation is always free. Finished runs use your plan's credits, one credit each. See Billing in credits.
Tips for a good automation
- Keep it to one job with a clear start and a clear finish.
- Say what should happen when a detail is missing.
- Test with real examples, including an awkward one.
- Leave approvals on until results are steady, then set limits for the routine steps.
Need help
See Troubleshooting or email support@tensorautonomous.com.