Keep your tools.
Agents work in them.

Connect Google Workspace, Microsoft 365, Slack, HubSpot, and the rest of your stack. Your agents read what they need and ask before anything gets sent, posted, or changed.

Start for free See it work

Connections at work

Each agent, its own accounts.

Waiting for your OK

Who's connected to what

Chief of StaffPersonal

Dana's personal agent

Gmail[email protected]Connected
Google Calendar[email protected]Connected

CloserShared

Shared with the sales team

HubSpotLarkspur portalConnected
SlackLarkspur workspaceConnected
Gmail[email protected]Connected

Closer, in your tools

Check our quiet HubSpot deals against the latest Gmail threads and move the ones that progressed.

Read 6 HubSpot deals with no activity in 14 days
Read the last Gmail thread with each contact

Update Deal

Use HubSpot

Modifies data

Deal: Fieldstone renewal
Stage: Proposal → Negotiation
Next step: Call Robin on Thursday

AllowDenyRequest editAlways allow this

Reads run on their own. Anything sent, posted, or changed in a connected tool waits for your OK.

Google or Microsoft. Either works.

Opser's Email, Calendar, and Drive work with the accounts and files your team already has.

Email. Every Gmail and Outlook mailbox, personal and team, in one inbox.
Calendar. Google and Outlook calendars side by side, synced both ways.
Drive. Preview Word, Excel, and PowerPoint files and open an editable copy.

Gmail — Your suite, in Opser's appsGoogle Workspace, Microsoft 365, or both

Your stack is already here.

Search the catalog, sign in with the tool's own login, and choose which agent uses it.

The tools you run on. Slack, Notion, HubSpot, Salesforce, Stripe, QuickBooks, and many more.
Sign in the usual way. The tool's own login, or an API key on a secure connect page. Never in the chat.
Or ask your agent. It shows a connect card in chat. Click it, sign in, and it carries on.

Not in the catalog? Bring it in.

Import the data from an export, or have your agent build the app you're missing.

Import the export. Attach a CSV or Excel file. The agent cleans it up and adds the records to the right app.
Build the app. Describe the tool and the agent builds it as an app in your workspace, with a preview first.
Research the rest. The agent reads public websites in a browser and links its sources.

How building an app works

CSV

old-crm-export.csv

1,401 rows, attached in chat

Added to Customers

Cleaned up and matched to the records you already had.

Organizations: 312
People: 1,048
Duplicates skipped: 41

Our shift scheduler isn't in the catalog. Build us a Shifts app with a weekly view.

Shifts

Preview ready, with sample data

Install

Reads run.
Writes wait.

Every send, post, and edit in a connected tool waits on a card, from the account you choose.

How security works

A card for every write

It shows the action, the details, and the account. Allow it, deny it, or ask for an edit.

Always allow the routine

Approve once and always allow that action, so routine updates stop asking.

Several accounts per tool

Connect a second Gmail or a client's Slack and tell the agent which one to act as.

Send as the right address

Pick the From address on the approval card from the mailbox's send-as list.

Something happens. Work starts.

An event in a connected tool can start an automation, so the job begins the moment it lands.

Pick the event

Choose a connected account and one of its events, like a new Gmail message.

Describe the job once

The agent gets the event's details and does what you wrote, every time.

See every run

Each run posts in the automation's own chat, with history and alerts.

How automations work

Customer requestsAn automation on a shared agent

When · Slack
New message in #customer-requests
Operator
Files a task with an owner, then replies in the thread with the link
Tasks
Fix CSV export for Fieldstone
Theo · Due Friday

You agree on these steps when you create the automation, so each run does them without stopping to ask.

A few more answers.

What teams ask before they connect their tools.

Do we have to move off HubSpot, Slack, or Google Workspace?

No. Connect them and keep working in them. Your agents read and act in those tools, and you move a job into an Opser app only when it earns its place.

How do connections sign in?

With the tool's own login, or with an API key entered on a secure connect page. Nobody pastes a password or a key into the chat, and you can disconnect an account from Integrations at any time.

Can the agent send or change things without asking?

Reading runs on its own. Sending, posting, and editing show an approval card first, and when you approve you can choose to always allow that action so routine work stops asking. Automations run the steps you agreed on when you created them.

What if a tool isn't in the catalog?

Describe what you need and the agent builds it as an app in your workspace, with a preview on sample data before anything is installed. Bring the old tool's data over from a CSV or Excel export. For research, the agent also reads public websites in a browser.

Can we bring data over from a spreadsheet?

Yes. Attach a CSV or Excel export to a chat. The agent cleans it up and adds the records to the right app, and if you ask to see the plan first, it waits for your go-ahead. Sales imports lead lists from a CSV directly.

Can our agents use our ChatGPT plan?

Yes. Connect your ChatGPT account in your profile and pick a model tagged Subscription. That work runs on your ChatGPT plan instead of Opser credits; voice and dictation still use credits.

Bring your tools along.

Connect the tools you already use and give your agent its first job.

Start for free Book a demo