Skip to main content

Documentation Index

Fetch the complete documentation index at: https://help.notis.ai/llms.txt

Use this file to discover all available pages before exploring further.

Some things only happen in a browser. Logging into a dashboard, accepting LinkedIn invites, finishing a checkout, copying a list off a page that no app makes easy to download. Notis can do all of that by driving a real Chrome window — same as a person would, just faster.

​
Two places it can run

  • In the Cloud Computer — the default. A clean Chrome opens inside Notis’s own private workspace in the cloud. Nothing touches your laptop. Best for most things: public sites, repeating tasks, screenshots, anywhere you can give Notis its own login.
  • On your computer, via the Local Shell — only when the task really needs to happen on your machine. For example, a site that only trusts your home network, or work that has to sit next to other files on your laptop.
Notis picks the cloud whenever it can — it’s faster and doesn’t get in your way.

​
What you can ask for

  • “Accept all my pending LinkedIn invitations.”
  • “Open my Stripe dashboard and pull last week’s refunds into a sheet.”
  • “Walk through this signup flow and take a screenshot of each step.”
  • “Log into the analytics dashboard, change the date range to last quarter, and download the report.”

​
Notis doesn’t drive your everyday Chrome

When Notis runs a browser task, it opens its own Chrome window — separate from the one you use every day. That’s on purpose:
  • Your real browsing stays yours. Notis won’t bump into your open tabs or change anything you’re in the middle of.
  • Some websites get suspicious when automation runs through your usual login. A clean separate browser avoids that.
  • It’s safer: Notis only ever sees the sites you ask it to use.

​
You only sign in once

The first time Notis needs to log into a site, a Chrome window pops up and you sign in like you normally would. After that, Notis remembers:
  • Next time it visits the same site, you’re already logged in — no second login.
  • It saves your sign-in at the end of every task, so it sticks around even if the window closes or your laptop restarts.
  • Signing in on your laptop and signing in for the cloud are separate. Logging in once on your computer covers tasks that run there; for cloud tasks, see 1Password below.

​
Sign in everywhere at once with 1Password

If you don’t want to log in interactively every time, or if you want the same site to work in the cloud and on your laptop, connect 1Password. Notis will then pull a password from 1Password the moment it’s needed — without showing it in chat or storing it anywhere on its side. You stay in control of which logins Notis can see. The setup is two steps:

​
1. Create a Notis vault and a service account in 1Password

Inside 1Password, make a new vault called “Notis” and put just the logins you want Notis to use into it. Anything you don’t move into this vault stays invisible to Notis. Then create a service account and grant it access only to the Notis vault. A service account is a special, password-free key that apps like Notis use to read items — different from your personal 1Password login. Step-by-step instructions from 1Password: Get started with 1Password Service Accounts. At the end you’ll get a token — a long string of characters. Copy it.

​
2. Connect 1Password to Notis

Open Notis → Settings → Integrations, find 1Password, and paste in:
  • The token from step 1.
  • Your 1Password sign-in address — it looks like yourcompany.1password.com. You can find it the same way you log into 1Password on the web: it’s the address that appears in your browser bar after you sign in. If you use the 1Password desktop app, you can also see it under Settings → Accounts → your account name → Sign-in address.
That’s it. From then on, whenever a browser task needs a saved login, Notis fetches it from the Notis vault automatically — whether the task runs in the cloud or on your computer. Add or remove logins by moving items into or out of the Notis vault.

​
When Notis uses it

Whenever the task is really a “go open a website and do something” job, and one of your connected apps can’t already do it directly. If a proper integration exists, Notis uses that first. The browser is the fallback for the rest of the web.