Fifty-two integrations, one conversation, zero dashboards to babysit

<!-- AI-DRAFTED: review before publish -->

Integrations are supposed to save you time, but most of them just move the work around. You wire your inbox to your project tracker, your calendar to a notification app, your notes to a spreadsheet, and now you maintain a web of triggers that break when a field name changes. You became the ops person for your own automations. That is backwards.

I connect to your apps and then I use them. The difference matters. A trigger fires blindly. I read your calendar, notice the conflict, check who the meeting is with, pull the relevant thread from Gmail, and ask whether you want me to reschedule. Same underlying connections, completely different relationship to your day. You talk to me in one place, and I reach into whatever tool the task needs.

Right now that catalog sits at more than 50 connectors, and it grows most weeks. But the number is not the point. A pile of integrations you have to assemble yourself is a liability. What matters is that the connections feed one assistant with real memory, so the app you connected on Tuesday still knows who "Sam from the Denver account" is on Friday.

What "connected" actually buys you

Let me make this concrete with a normal Wednesday.

You get a message on WhatsApp from a client asking to move your Thursday call to Friday afternoon. You forward it to me. I check Google Calendar, see that Friday afternoon has a soft hold you told me last week was flexible, confirm there is no travel conflict, and draft the reply. I ask before I send it, because rescheduling a client is a consequential action and I do not make those calls silently. You say go. I send it, update the calendar, and log the change.

None of that required you to open five tabs. It also did not require you to build a rule that says "when a message contains the word reschedule, do X." I read the intent and acted on it. That is the gap between an automation platform and an assistant. Platforms like Zapier and Make are genuinely good at deterministic, high-volume plumbing, moving a new lead from a form into a spreadsheet ten thousand times without complaint. That is real and useful work. I am aimed somewhere else: the messy, judgment-heavy tasks that do not fit a clean if-this-then-that shape.

The core connectors most people live in are Gmail, Google Calendar, Drive, Docs, and Sheets. Around those sit the rest of the catalog, and when a service has no clean way to connect, I can drive a browser directly and do the task the way you would, by clicking through the site.

The connections that matter more than you'd think

Two integrations do more work than their names suggest.

The first is Sheets. A spreadsheet is where a lot of people keep the truth about their business, and treating it as a live source I can read and write means I can update a pipeline, pull a number for your evening brief, or append a row when a meeting produces a follow-up. It is boring on paper and quietly central in practice.

The second is Drive, once you turn on the Life Index. This is opt-in, and I want to be clear about what it does before you flip it on. You let me index your Gmail, Calendar, Docs, Sheets, and Drive into memory. After that, when you ask "what did we agree on pricing with the Portland vendor," I retrieve it by meaning, not by making you remember the file name. You stay in control of every piece of it. You can view what I know, edit it, delete a single fact, or wipe the whole thing. Superseded facts get versioned rather than overwritten, so if the vendor changed their quote in March, I know both numbers and which one is current.

That last detail is where integrations and memory stop being separate features. A connector without memory is a straw. Every task starts from nothing and you re-explain your world each time. The catalog is only worth anything because everything it pulls in lands in a structure I can reason over later.

Why I ask before I act

Connecting your apps means I can spend money, send messages, and book things on your behalf. That is exactly why I do not do those silently. The line I hold is simple: routine work I handle and report, consequential work I ask about first. Archiving a newsletter, tagging an email, pulling a summary, those I just do. Sending a message to your biggest client, moving money, booking a $600 flight, those get a quick approval from you in whatever channel we are talking on.

I would rather ask one extra time than send the wrong email once. You can read more about how that oversight works, but the short version is that a connected assistant with no restraint is a hazard, and I was built to be useful without being reckless.

One conversation, five doors

The other half of integrations is where you talk to me. I connect to your tools, but I also meet you where you already are. Web app, WhatsApp on my own number with no setup, Telegram, Discord, and voice including actual phone calls. So the client reschedule I described earlier can start on WhatsApp, continue by voice on your commute, and end with me updating a Google Doc, all one continuous thread. The apps on the back end and the channels on the front end are the same idea pointed in two directions: fewer places for you to check, fewer contexts for you to hold in your head.

If you want the whole thing to run on your own model keys, you can bring them. BYOK is there for people who care about that, and I think more of you should.

The honest limits

A catalog of 50-plus connectors is not "every app you own," and I am not going to pretend otherwise. Some tools do not exist in the catalog yet, and for those I lean on the browser, which is slower and occasionally clumsier than a real API. If a service you depend on is missing, tell me, because the list grows based on what people actually ask for. I would rather add the ten connectors twelve people need than sit at a bigger number full of things nobody touches.

The trial is 15 days, Standard is $49 a month, Pro is $99. Connect your calendar and inbox first, live with it for a week, and see whether being able to run your apps from one conversation is worth more than the tab-switching you do now. For most people I think it is, but you should decide that with your own week, not my say-so.

FAQ

How many integrations does Niyra have? More than 50 in the catalog today, and it grows most weeks. The core five are Gmail, Google Calendar, Drive, Docs, and Sheets. For services without a connector, I can drive a browser to complete the task.

Do I have to build the automations myself? No. This is the main difference from tools like Zapier or Make. You do not assemble triggers and maintain them. You tell me what you want in plain language and I use the connected apps to do it, asking before anything consequential.

Is it safe to let Niyra into my Gmail and Drive? The deep indexing (Life Index) is opt-in, and you control all of it. You can view, edit, or delete anything I know, or wipe it entirely. Facts that change get versioned, not silently overwritten, so nothing gets quietly lost.

What if my tool isn't in the catalog? I can often work with it through the browser, clicking through the site the way you would. It is slower than a native connection. Tell me what is missing, since the catalog grows based on what people request.

Can I use my own model keys? Yes. BYOK lets you bring your own model API keys, so the assistant runs on the models you choose while still using every connected app and channel.