Connectors
3,000+ apps, with your access. Never more.
Connect the tools you already use and Nema works in them as you. Reads run straight through. Risky writes wait for a yes.
Connect once, for yourself
Each person connects their own apps. Gmail, Google Calendar, Google Drive, Linear, GitHub, Notion, HubSpot, Jira, and a catalog you can search. Nema acts in each app as the person who asked, and a channel coworker uses the apps it was set up with.
There is no shared service account. No admin connects an app on your behalf. Nobody can act through your connection but you.
One catalog, every tool your team already pays for
The catalog covers 3,000+ apps. Email, calendars, docs, project trackers, code hosts, CRMs, support desks, finance and data tools, and the long tail behind them. If your team has a login for it, Nema can most likely work in it.
- Email and calendar
- Gmail
- Outlook
- Google Calendar
- and more
- Docs and files
- Google Drive
- Notion
- Dropbox
- Box
- and more
- Projects
- Linear
- Jira
- Asana
- Trello
- and more
- Code
- GitHub
- GitLab
- Bitbucket
- and more
- Sales and CRM
- HubSpot
- Salesforce
- Pipedrive
- and more
- Support
- Intercom
- Freshdesk
- Help Scout
- and more
- Finance and HR
- Stripe
- QuickBooks
- Ramp
- Rippling
- and more
- Data and sheets
- Google Sheets
- Airtable
- Snowflake
- and more
Search the catalog in the console, connect an app, and it is yours from the next message. A channel coworker uses the apps it was set up with, so ask an admin to add one with /nema edit.
Connecting takes a minute
There is no admin project and no shared account to set up. Each person connects the apps they use, the same way they would sign in to them.
- Find the appSearch the catalog in the console, or wait for Nema to ask.
- Sign in onceThe app's own sign-in, with the access you already have.
- Nema acts as youFrom the next message, in every channel you use it in.
- Disconnect any timeOne click, and every call through that app stops.
What it looks like in a thread
A connection is only useful for what it lets you ask. A few things people ask in the first week.
Reply from your inbox
Draft a reply to a customer from the last three emails and send it from your Gmail, after you approve it.
File the bugs from this thread
Turn a thread of complaints into three issues in Linear or Jira, each with the steps people posted.
Pull the numbers before the call
Ask for this quarter's pipeline from HubSpot or Salesforce, and get it in the thread before the meeting starts.
Find the document and the date in it
Find the Northwind contract in Google Drive and read out the renewal date and the notice period.
If an app is missing, it asks you to connect it
Ask for something that needs an app you have not connected and Nema does not fail. It sends you a private sign-in card, says what it will do next, and waits. Connect the app, say so in the thread, and it carries on. It can answer the parts that did not need the app in the same reply.
@Nema find the Northwind contract in Drive and tell me the renewal date.
I need your Google Drive for that. I sent you a sign-in card. Say connected when it is done and I will find the contract.
🔒Sign-in card sent to Owen Bartlett · link expires in 10 minutesconnected
Found it. The contract renews on 14 March with 90 days' notice, so the last day to give notice is 14 December.
Reads run free. Risky writes wait.
Looking something up in an app runs straight through. Sending an email, creating an issue or changing a record goes through a risk gate and your workspace policy, and anything risky raises an approval card first.
Your admin can set a policy per app or per action: always allow, always ask, or block it outright. When a coworker and the workspace disagree, the stricter rule wins.
- You askWhich invoices are past due?
- Nema looks it upIn the app, with your access.
- Answer in the threadNo card, no wait.
- You askSend Northwind the renewal.
- Nema drafts itAnd shows you the action before it runs.
- Approval cardYou, or a named approver, say yes.
- Done, loggedThe result posts in the thread. The approval is on the record.
@Nema file the three bugs from this thread in Linear, under the checkout project.
Read the thread. Three bugs, each with the reproduction steps people posted.
Create 3 issues in Linear?Checkout project · Coupon total rounds up · Apple Pay sheet blank on iOS 17 · Address form loses state on back👁Only visible to you · ApprovedCreated CHK-311, CHK-312 and CHK-313, linked back to this thread.
It searches the web and shows its sources
When the answer is not in your apps, Nema searches the web, reads the one or two pages that matter, and gives the link for anything it states from them. Web pages are treated as data, never as instructions.
Each coworker reaches only what it is given
A coworker is set up with the apps it may use. A channel with contractors gets an agent that reaches only what that channel needs. Change the list with /nema edit in the channel. The console shows it read-only.
Under your control
Every connection is personal. Nobody, admin or not, can act through yours. Disconnect an app in the console and every call through it stops at once.
Your admin sets policy per app or per action, always allow, always ask, or block it outright, and the stricter rule wins. Every call an app receives is logged with who asked, what ran and who approved.
Start with one channel.
Add Nema to Slack, invite it to one channel, and ask it something. $50 in free credits, no card up front. If you would rather see it first, we will walk you through it.