Skip to main content

​
Let your AI agent browse the web for you

Your AI agent can visit other websites for you. It can check listings on booking sites, pull reports, and verify prices. Many of those sites need a login first. Connected accounts save a website login on one AI agent. That agent can then sign in when it needs to visit the site. Instead of copy-pasting data from Airbnb or Booking.com, tell the agent what you need. It signs in, finds the answer, and brings it back.

​
How it works

1

Add a website login

Open AI Hub and pick the agent. Open the Integrations tab and click Connect website.Enter:
  • The website (or pick a suggested site like Airbnb, Booking.com, Guesty, Breezeway, Hostaway, or Krossbooking).
  • Your email or username.
  • Your password.
2

Test the login

Click Verify to have the agent try the login. A secure browser opens and the agent signs in for you. You can watch it happen in a live view window.
3

Handle two-factor codes

Some sites ask for a code from your authenticator app. The agent pauses and waits for you to type the code.You can also save a two-factor setup key with the login. Then the agent handles the code on its own.
4

The agent signs in when it needs to

Once the login works, the agent reuses your saved sign-in when it visits the site. When the site allows it, the agent stays signed in so it does not have to log in every time.

​
Adding a login

From the agent’s Integrations tab, click Connect website to add a new login.
FieldDescription
WebsiteThe site to sign in to (for example, airbnb.com or booking.com). Pick from suggestions or type any site.
Email or usernameYour username for the site. If you enter an email address, the agent uses it for either field.
PasswordYour password for the site. It’s stored encrypted. The agent only uses it to sign in.
Two-factor setup keyOptional. A setup key from your authenticator app. When you add one, the agent handles two-factor codes on its own.
To find your two-factor setup key, look for a “setup key” or “secret key” when adding an account in your authenticator app (Google Authenticator, Authy, 1Password, and so on). It’s usually a long string of letters and numbers.

​
Login status

Each saved login shows a status so you can tell at a glance whether the agent can sign in.
StatusMeaning
ReadyThe login is confirmed and the agent can sign in.
Not connectedThe login has not been tested yet, or you just changed it. Click Verify to test it.
Needs codeThe site asks for a two-factor code the agent can’t create. Add a two-factor setup key to fix this.
FailedThe last sign-in failed. Update the login and test it again.
When the agent uses a login during a chat task, the status updates on its own based on whether the sign-in worked.

​
Two-factor codes

Many travel sites ask for a two-factor code when you sign in. Connected accounts handle this in two ways:
Add your two-factor setup key when you save the login. The agent creates the code on its own during sign-in. No extra step needed. This is best for sites you use often.
Your two-factor setup key is encrypted and locked to that single website. It is never shared with other sites or used outside sign-in.

​
Live browser view

When the agent opens a browser to sign in or do a task, you can watch it work in a live view window. This helps you:
  • Confirm a login works. Watch the agent fill in your sign-in and see it succeed.
  • Handle two-factor prompts. Type a code into the live browser when the agent pauses.
  • Track what the agent does. See exactly what it clicks and reads on the other site.
The live view opens on its own when you test a login and when the agent needs your input.

​
Browser sessions in chat

When you ask the agent to do something that needs a website (like “check my Airbnb listing for unit 4B” or “pull the latest payout report from Booking.com”), a browser session card appears in the chat. The session card shows:
  • Step-by-step progress. Each action the agent takes appears as a step with a timestamp.
  • Screenshots. The agent snaps screenshots as it works so you can see what it saw.
  • Live view. Click to watch the browser session in real time while it’s running.
  • Final result. When the task ends, the agent shares what it found in the chat.
If the agent hits a problem, like a popup or a page that looks different, it pauses. Take over through the live view to help it past the issue.

​
Suggested sites

When you add a login, Trellis suggests sites teams use often:
  • Airbnb
  • Booking.com
  • Guesty
  • Breezeway
  • Hostaway
  • Krossbooking
You can also type any website to connect the agent to a site that isn’t on the list.

​
Manage saved logins

From the agent’s Integrations tab, you can:
  • Edit a login to update the username, password, or two-factor setup key.
  • Test again after changes to confirm the agent can still sign in.
  • Delete a login to remove the agent’s access to that site.
If you update the email, username, or two-factor setup key, the status goes back to “Not connected.” Test the login again after any change.

​
FAQ

Passwords are encrypted and locked to one website. The agent only unlocks a password to sign in to that site. They’re never shared with other sites, other users, or other workspaces.
Yes. After a successful sign-in, the agent keeps the session so it does not have to sign in every time. This works like staying signed in on your own browser.
The login status turns to “Failed” the next time the agent tries to sign in. Update the password from the agent’s Integrations tab, then test it again.
Logins are tied to the AI agent, not to team members. Everyone in the workspace shares the same set of connected accounts for each agent.
The agent can sign in to most sites that use a standard email and password form. Sites with unusual sign-in steps (like bank-level security or hardware keys) may not work reliably.