Connect a mailbox

Who can do this

Mailboxes are Admin only. Connecting, reconnecting and disconnecting a mailbox requires Admin, and so does reading, replying to, or triaging a connected mailbox in a conversation with Ronja — a shared inbox is full of other people’s mail, so it is not general-readership data. What an Admin can do for everyone else is attach a mailbox to a Saved Agent or an Automation, which then works the mailbox without an Admin in the loop — see Let an automation work a mailbox — or let a workflow send mail as the mailbox, see Sending mail from a workflow.

A connected mailbox is an email account Ronja reads, replies from, and sends new mail from — all as that address. When someone writes to support@yourcompany.com, Ronja can read the message, answer it in the same thread, and label it as handled; she can also start a brand-new email conversation from that address. The person on the other end sees mail from support@yourcompany.com — not from Ronja, and not from a Ronja address.

Mailboxes are managed on the Mailboxes page in the admin sidebar (under Integrations). You can connect Gmail and Outlook mailboxes.

Caution

This is not the page for Ronja’s outbound notifications, and not the address that triggers automations. Three different things share the word “email” — see What’s the difference?.

What you can connect

A real mailbox — the one you sign in as. There is nothing to type in first. Whichever account you sign in as becomes the connected mailbox, and the card then shows exactly which address that is, so you can always see what Ronja connected. Sign in as the mailbox itself — support@yourcompany.com, not your own account.

One case is refused outright:

• A Google Group cannot be connected. A Group is a forwarding list — it has no inbox of its own and no login, so there is nothing for Ronja to read. A Group has no login to sign in with, so “connect the group address” isn’t possible; if support@ is a Group today, convert it to a shared mailbox (a Google Workspace user with Gmail turned on) and connect that.
• A Microsoft shared mailbox cannot be connected. In Microsoft 365, an address like support@ is often a shared mailbox — which by design has no password of its own, so there is nothing to sign in as. Connect a licensed user mailbox instead. (If your support@ is a shared mailbox, one option is to give a licensed account that address and connect that account.)

Because the connected mailbox is simply whoever you sign in as, sign in as the mailbox, not as yourself — if you sign in as your own account by mistake, Ronja would read your inbox. The card names the connected address plainly (“Ronja reads and replies as this address”), so if it’s the wrong one, Disconnect and reconnect as the right mailbox.

Connect a mailbox

1. Open Mailboxes and click Connect a mailbox.
2. In the step that opens, choose Gmail or Outlook, then click Connect Gmail / Connect Outlook. A popup runs that provider’s sign-in.
3. Sign in as the mailbox itself, not as your own account. Use a private window if you are already signed in as someone else.

That’s it — connecting is pick a provider, sign in, done. When the sign-in finishes, the mailbox appears on the page showing the address it connected. You don’t type an address or pick a label up front; the address is read from the sign-in, and the watched label is a setting on the card (see Watched label).

You don’t set a “handled” label either. When Ronja has dealt with a message she marks it read and files it under a Ronja-managed label automatically — there is nothing to configure. She uses one other label of her own: when she emails a colleague a question from this mailbox, she files that thread under a second Ronja-managed label and leaves it unread, so you can see she asked — see Questions Ronja asks from this mailbox. Ronja won’t add or remove either of her own labels on your instruction; ask her to use a label of your own instead.

If Ronja can’t read a mailbox from the account you signed in as (for example a Google Group, or a Microsoft account with no mailbox of its own), the card explains what happened and what to do — see When a mailbox isn’t connected.

Letting others use a mailbox

Mailboxes are Admin only to use in a conversation. Someone who isn’t an Admin can’t read, reply to, or triage a connected mailbox in a chat, and the Mailboxes page shows them an admin-only notice rather than a list.

The way a non-Admin’s work reaches a mailbox is through an Automation, a Saved Agent, or a Workflow: an Admin attaches the mailbox to it, and it then works the mailbox on its own — see Answering mail unattended and Sending mail from a workflow. Attaching a mailbox is itself Admin only, so the Admin is vouching for what that automation, agent, or workflow may do with the inbox.

Cutting off a mailbox

A connected mailbox surfaces other people’s mail into conversations and into whatever automations reference it, and those conversations can be shared. Removing a mailbox from an automation, Saved Agent, or workflow stops future runs from reaching it, but it does not claw back anything already read. To fully cut a mailbox off, Disconnect it (below) rather than only detaching references.

What Ronja can do with a connected mailbox

Ask her in a conversation, or have an automation do it unattended:

• Read it. Search the mailbox and read the matching messages — by query, or one thread in full.
• Reply in-thread. Answer as the mailbox address, in the existing conversation, so the thread stays intact for the recipient. Any formatting Ronja writes (bold, lists, links) is sent as HTML, with a plain-text version alongside for mail clients that prefer it.
• Send new email. Start a new conversation as the mailbox address — a first outbound message to someone, not a reply to something that arrived. You can ask her to copy people in (Cc) as well — see Copying people in. New emails carry the same formatting (HTML with a plain-text fallback), and who Ronja can send them to is governed by the Compose recipients setting below. She can also attach files — a report she just built, an export, anything you uploaded: up to 10 files and 25 MB in total from a Gmail mailbox. From an Outlook mailbox the ceiling is about 3 MB per message, which is Microsoft’s limit rather than Ronja’s; an email over it is refused before it is sent, and the refusal names the real limit so you can send fewer files or share a link instead.
• Triage. Mark a message read and add or remove labels — the way she sets aside anything she shouldn’t answer herself (for example labelling it for a human).
• Ask a colleague a question from it — Gmail mailboxes only. An unattended run that hits a judgment call can email a specific colleague from this address, pause, and pick up where it left off once they reply in the thread. This is Ronja’s preferred way to ask once the mailbox is attached to the Agent or automation doing the asking — it reaches the person from an address they recognize, and their answer lands in this inbox with the rest of the conversation. Because it is a real email thread, the exchange can carry on in the same thread: a follow-up question, or a short reply that needs no answer, arrives as a reply to the message the person already answered rather than as unrelated new mail. (Asking from Ronja’s own address can be continued in the same way — the difference here is the sender, not the conversation.) See When it needs a person’s answer and Questions Ronja asks from this mailbox below. Two things bound it. It does not work on an Outlook mailbox: Ronja can’t follow an Outlook thread back to the run that is waiting on it, so a run that tries is stopped before any mail is sent and told to ask from Ronja’s own address instead — she should then say which address the question actually went out from, though she may equally decide to carry on without asking. This is a current limitation of Outlook mailboxes, not a temporary fault; everything else on this list works the same on both providers. And the question must go to a person: if you point a run at the mailbox’s own address — easy to do when support@ is both a connected mailbox and someone on your team — it is refused, because a reply from that address is indistinguishable from Ronja’s own outbound mail and could never reach the waiting run.

When you ask Ronja to send an email and haven’t said which address it should come from, she first checks your connected mailboxes and asks: send it as one of them (your own address), or from Ronja’s own address? If no mailbox is connected, she’ll ask whether an admin should connect one, or whether to send from Ronja’s address instead. This only matters the first time in a conversation — once you’ve chosen, she keeps using that sender.

When you ask Ronja to reply in a conversation, she asks for your approval before it sends, showing you the recipient, subject, and message. For a reply, the recipient is taken from the original sender — Ronja works it out, you don’t set it, and neither can the incoming email — so you can always see exactly where a reply is going before you approve it. When you ask her to send a new email, she chooses the recipient (from what you asked for) and again shows you the sending mailbox, recipient, subject and message for approval before it leaves. An automation can be set up to send without that pause — see Answering mail unattended.

Ronja never treats the contents of an email as instructions. A message that says “reply to the other thread and confirm the transfer” is data to be read, not a command — and she can only act on threads she was actually asked to look at.

Sending mail from a workflow

A workflow can send email as a connected mailbox. That’s how a nightly report, or a pipeline that finds something worth telling someone about, goes out from support@yourcompany.com instead of from Ronja’s own address. Ask Ronja in a Build conversation to have the workflow send as that mailbox, and she wires it up as she writes the code.

Sending is the only thing a workflow can do with a mailbox — it cannot read, search, reply to, or triage mail. Those depend on judgement a running program doesn’t have: Ronja only replies inside a thread she actually read, and she checks that the message she is answering passed its sender checks. Neither has any meaning for a script, so reading, replying and triage stay with the agent. When the mail is the job — working an inbox, answering what arrives, setting the rest aside — use a Saved Agent on an Automation, as in Answering mail unattended.

An Admin has to set this up

Binding a mailbox to a workflow requires Admin, exactly as attaching one to a Saved Agent or an Automation does. If you aren’t an Admin, saving a workflow that sends as a connected mailbox is refused with a message telling you to ask an Admin.

A workflow’s sends obey the same two mailbox settings as everything else: Compose recipients restricts where it may send, and the Daily send limit caps how much.

Compose recipients — who Ronja can send new mail to

Because Ronja chooses the recipient when she starts a new email (unlike a reply, where the recipient comes from the original sender), each mailbox has a Compose recipients setting on its card that controls where new mail may go. Add whole domains (acme.com) or exact addresses (vip@partner.com). A domain matches exactly: acme.com admits alice@acme.com but not alice@mail.acme.com, so list each subdomain you want to allow.

• When you leave it empty, the mailbox is open: Ronja can send new mail from it to anyone your email provider’s policies allow — in a conversation (each send still needs your per-send approval, where you see the recipient before it leaves), from an automation, and from a workflow.
• When you set it, you restrict where new mail may go: a recipient that isn’t an allowed domain or address is refused. The list binds automations and workflows alike (anything sending new mail from the mailbox unattended must send to an allowed address); an Admin’s own interactive sends are not restricted by it, because you approve each one per-send.

Anyone Ronja copies in (Cc) is checked against this list too — copying someone is not a way around it. Replies are always unaffected — a reply goes back to whoever wrote in, so the Compose recipients setting only governs Ronja’s new conversations, never her replies.

It also governs questions Ronja asks from this mailbox

A question to a colleague is a new email Ronja chooses the recipient for, so the Compose recipients list binds it too — and always as an automation would be bound, because a question is only ever asked by an unattended run with nobody to approve it.

That is easy to be caught by: if you narrowed the list to your customers’ domains, a run that tries to ask your own colleague is refused. The person must also pass your organization’s Agent email policy (Organization → Governance), which is the separate, organization-wide setting for who Ronja may email at all — people in your organization always pass it, and whether an outside address does depends on which of Members only, Members + allowed domains or Anyone is set there. Both have to allow the address: the narrower one wins. If you want unattended runs to be able to ask someone outside, allow them in both places.

Leaving the list empty keeps this mailbox open, and questions can reach anyone your organization’s email policy allows.

Copying people in (Cc)

When you ask Ronja to send a new email — from a connected mailbox or from her own address — you can ask her to copy someone in: a manager who should see it, a shared team address that keeps a record. Everyone on the email sees who else got it.

• The people copied in follow the same rules as the main recipients. They go through your organization’s email policy (so an address your organization doesn’t allow is refused), and they count toward the daily budget the mail draws on like anyone else — the mailbox’s Daily send limit when it comes from a connected mailbox, the organization-wide cap when it comes from Ronja’s own address. See Limits and retention. When the mail comes from a connected mailbox, they are checked against that mailbox’s Compose recipients list too.
• One email can reach at most 20 people, counting the main recipients and the copied-in ones together — not 20 of each.
• If everyone you asked to copy in is refused, the email still goes to its main recipients and Ronja tells you the copies were dropped. If the main recipients are refused, nothing is sent.
• There is no Bcc. Ronja can only copy people in visibly — everyone on an email can see everyone else it went to.
• Replies are never copied to anyone new. A reply goes back to whoever wrote in, so there is nothing to copy in.

Before an email leaves in a conversation, the approval you give shows everyone it is going to, copied-in people included.

Daily send limit — how much mail a mailbox may send

Each mailbox also has a Daily send limit on its card: the most recipients it may email in a rolling 24 hours. It counts recipients rather than messages, so one email to ten people counts as ten.

• Leave it empty and the mailbox uses Ronja’s default of 500 recipients per 24 hours.
• Set a number to raise or lower that, up to a maximum of 10,000. A deliberately low limit is a useful blast radius on a mailbox that something works unattended: whatever goes wrong, it stops at the number you chose.

The limit covers all mail sent as that mailbox, whoever or whatever asked for it: an Admin’s replies and new emails in a conversation, a Saved Agent’s, an automation’s, a workflow’s, and the questions Ronja emails from the mailbox — all drawing on the same daily budget. It is a separate budget from the organization-wide cap on mail Ronja sends from her own address, and each connected mailbox has its own; see Limits and retention.

Watched label — which mail Ronja looks at

Each connected mailbox has a Watched label setting on its card that scopes what Ronja polls. Leave it empty and Ronja watches all incoming mail. Set a name and Ronja only looks at mail filed under it — useful when a single inbox carries more than you want Ronja handling. On Gmail that name is a label; on Outlook, Ronja matches it against your folders first and then your categories, so either works. Edit it any time from the card; the change applies to future mail, and doesn’t reach back over mail already seen.

A label that no longer exists widens the scope rather than closing it

The name is saved as you type it — Ronja doesn’t check that the label exists when you save. If the label is later renamed or deleted, or the name has a typo, Ronja can’t match it and falls back to watching the whole mailbox. Nothing on the card turns red, so the first sign is usually an automation that starts firing on mail you expected it to skip. If that happens, check the label name here first.

Answering mail unattended

To have Ronja work the mailbox unattended, pair it with an Automation on a Mailbox trigger that runs a Saved Agent. A mailbox trigger fires when new mail arrives in this mailbox — one run per message, seeded with that message — so the agent answers what it can confidently answer and labels anything else for a human, minutes after the mail lands rather than on the next sweep.

1. Ask Ronja for the automation in an exploration, the way you would any other — see Schedule an automation.
2. Choose the Mailbox trigger and pick this mailbox as the Watched mailbox. Binding a mailbox is Admin only, like connecting one.
3. Optionally narrow what fires it under Filters (optional): sender domains, sender addresses, subject terms, attachments only. Leave them blank to run on every new message — the usual setup for a support inbox. Sender domains match exactly, so acme.com does not cover mail.acme.com.
4. Give the automation’s Saved Agent this mailbox as a reference so the run can actually reach it, and pre-approve the reply action if you want it to send without a person in the loop — see References and pre-approved actions. Ronja warns you when you create or edit an automation whose Saved Agent is missing that reference: the automation still runs and is still seeded with each message, but it cannot read, reply to, or triage the mailbox — so it answers nothing.

The mailbox’s Watched label comes first. If one is set, only mail filed under it reaches any automation on this mailbox — the label scopes the mailbox, the filters then narrow one automation within that. Leave the label empty and the trigger sees all incoming mail. Treat the label as a convenience, not a wall: a label that has been renamed or deleted can’t be matched, and Ronja falls back to watching the whole mailbox — so an automation with no filters of its own starts running on everything.

Two things to expect. Only mail that arrives after you enable the automation fires it — turning it on does not work through what is already in the inbox, and neither does turning it back on after a pause. And checking is not instant: Ronja looks roughly every couple of minutes while mail is arriving and less often as the mailbox goes quiet, so first response is minutes, not seconds. That pace follows how busy the mailbox is, not how often your filters match — a narrowly-filtered automation on a busy shared inbox still gets the fast pace.

If this mailbox stops working, its automations go quiet without saying so

An automation is switched off, loudly, when you Disconnect the mailbox — and getting it running again means pointing it at a newly connected mailbox, not just switching it back on (see Disconnect a mailbox).

A mailbox that merely stops working is the quiet case: the authorization expired and it needs reconnecting, or a check failed. Nothing is switched off and nothing is marked — the automations keep reading Active, and nothing new fires. If a mailbox automation has gone quiet, look at the mailbox card here before you look at the automation. Here Reconnect genuinely resumes it: the mailbox is the same one, so there is nothing to re-point and nothing to re-enable.

A mailbox trigger can also send new email (not just reply). If you want to limit where it can send, set the mailbox’s Compose recipients first — the automation is then refused if it tries to send new mail to an address that isn’t on that list. That list is what bounds a triggered run’s outbound mail whichever address it leaves from: new mail sent as this mailbox, questions Ronja emails from it, and mail the run sends from Ronja’s own address. With no list set, the mailbox is open and the automation can send new mail to anyone your email provider’s policies allow, so set the list if that isn’t what you want. Replies are never restricted by it — a reply always goes back to whoever wrote in.

One sending automation per inbox

Pick one thing that answers. A Mailbox trigger never fires the same automation twice for the same message — but that is all it guarantees. Two mailbox automations on one inbox both fire on the same message, and a Schedule automation you write yourself that searches the same inbox will find mail the trigger is already handling. Any of those combinations can answer the same customer, from the same address, minutes apart.

So: one automation that answers from a given mailbox. If you want different mail handled differently, either give that one automation the instructions for both cases, or use Filters (optional) to give each automation a slice that cannot overlap the other’s — different sender domains, say. Keep any further automation on this mailbox to work it does not send from: a daily summary, a report of what was handled.

A Schedule trigger is still the right tool when you want a periodic sweep rather than a reaction — “every morning, summarize what came in overnight”. It runs at most once an hour, so it is not a way to answer mail quickly.

Set Compose recipients when an automation reads untrusted mail

An automation that works an inbox is reading untrusted content — a crafted message could try to steer Ronja into emailing an attacker-chosen address. Ronja never treats an email’s contents as instructions, but Compose recipients is your hard backstop, and it starts open (empty = send anywhere). If the automation can compose new mail, set an allowed list of domains and addresses so a compose can only ever reach recipients you named — anyone copied in is checked against the same list. The mailbox’s Daily send limit bounds how much can go out on top of that, and it bounds the automation’s replies too, not just its new mail. Replies are unaffected by the recipient list itself — they always go back to whoever wrote in.

When Ronja is working a mailbox unattended, she won’t reply to a message that fails sender authentication — a sign it may be spoofed — and leaves it for a person to look at instead. (This guard applies only to automated replies; when you’re approving each reply yourself, you decide.)

Checking is not continuous, whichever trigger you use. With a Mailbox trigger, Ronja checks for new mail roughly every couple of minutes while mail is arriving, easing off to every five minutes and then every twenty as the mailbox goes quiet — the moment something arrives the quick pace resumes. Expect minutes, not seconds. She also looks back only a few hours, and mail that arrives and then ages past that window before a successful check is not picked up afterwards. A long service interruption is the obvious way that happens, but not the only one: the same applies while checks on this mailbox are repeatedly failing and Ronja is easing off, while its authorization needs reconnecting, and while your mail provider is rate-limiting the account. Treat a worked mailbox as first-line cover, not a live chat channel.

With a Schedule trigger, Ronja only looks at the mailbox when the automation runs, and a schedule runs at most once an hour — so expect up to an hour. This only matters if you have used Custom (cron) to run the automation more often than hourly: a mailbox that has found no mail for several hours is then checked a little less often — never less than every 45 minutes — until something arrives. On the hourly setting it changes nothing, because the schedule is already the slower of the two.

An unattended search looks back a week unless told otherwise. When an automation searches a mailbox without naming an age, Ronja looks at the last 7 days of mail — it would otherwise re-read the same untouched threads for as long as they sit there. (Searching a mailbox yourself in a conversation is not limited this way.) She is told each time that the limit was applied, so she can search further back when the task calls for it. If you want an automation to reach older mail every run, say so in its instructions (for example, “search the last 60 days”).

There is one narrow exception, and it is not inbox watching. When an unattended run needs a person’s decision, it can send the question from this mailbox and wait — and Ronja then checks that one email thread on her own until the person replies: every couple of minutes at first, less often as time passes. Nothing else in the mailbox is read on that schedule, and the checking stops as soon as the question is answered or gives up — and starts again for as long as a follow-up question in that same thread is waiting. This applies to Gmail mailboxes only — on an Outlook mailbox Ronja is told to ask from her own address instead, and nothing in the Outlook mailbox is polled. See When it needs a person’s answer.

Questions Ronja asks from this mailbox

A question Ronja emails a colleague from this mailbox becomes an ordinary thread in it, and their reply arrives as ordinary unread mail. That would collide with the unattended work above — an automation searching unread mail would find the colleague’s reply and could answer them as though they were a customer, or file it away before the waiting run ever reads it. A Mailbox trigger would have the same problem: the reply is new mail arriving.

So Ronja files every question thread under a Ronja-managed label of her own, and an automation searching this mailbox never sees those threads. A mailbox trigger stands down on them too — a reply on a thread where a run is still waiting for an answer goes to that run, and starts no new one. Two consequences worth knowing before you go looking:

• You still see them. The thread is left unread on purpose, so the mailbox owner can see that Ronja asked a colleague something on their behalf. It is only hidden from unattended searching, never from you, and never when you are reading the mailbox in a conversation yourself.
• Your automation’s own reports will not mention them. If you compare what is sitting in Gmail against what a scheduled automation reports it looked at, the question threads are the difference. That is the intended behaviour, not a missed message.
• A question thread can grow. Once the colleague has replied, the run may ask a follow-up in that same thread, or send a short reply that needs no answer — a thank-you, a correction, “never mind”. Each of those stays in the one thread, under the same Ronja-managed label, so a longer exchange never leaks into the automated drain either. See Carrying on the conversation for what bounds it.

Ronja also won’t let anything add or remove that label, or her “handled” one, on instruction — including an instruction arriving inside an email. Adding it to a real conversation would hide that conversation from your own automation; removing it would put a question thread back in front of one.

When a mailbox isn’t connected

A mailbox that isn’t working stays on the page in a degraded state, with an amber note on its card explaining why and what to do. It never disappears silently, and it never starts reading mail you didn’t intend it to.

What the card says	What happened	What to do
That account has no mailbox	The account you signed in as has no inbox of its own. On Google that’s most likely a Google Group, or Gmail is off for it. On Microsoft it’s an account without a mailbox licence — or a shared mailbox, which can’t be signed into.	Sign in as a real user mailbox instead (a Workspace user with Gmail enabled, or a licensed Microsoft 365 user).
That mailbox is already connected	The account you signed in as is already connected as another mailbox here.	Disconnect this duplicate card to clear it — it won’t affect the mailbox that’s already connected, which stays connected and working. To re-authorize the original, use Reconnect on its own card.
Reconnected as a different account	You clicked Reconnect on a mailbox but signed in as a different account than the one it’s connected as.	Sign out (or use a private window) and reconnect as the same address the mailbox shows.
Ronja could not verify this mailbox	The verification check itself failed — usually temporary.	Click Reconnect and try again in a few minutes.
Connecting was never finished	The popup was closed or never completed.	Click Reconnect to finish, or Disconnect to clear it.
A reconnect was never finished	You started a Reconnect but closed the popup without finishing, so Ronja paused the mailbox to be safe — it may hold credentials for a different account until the reconnect is completed.	Click Reconnect and finish signing in as the same address the mailbox is connected as.

Note that connecting the wrong mailbox by signing in as your own account isn’t an error — it succeeds, and the card shows the address it connected. If that’s not the mailbox you meant, Disconnect it and connect again as the right one.

Reconnect re-runs the sign-in for that mailbox in place, and must sign in as the same address the mailbox is connected as — it never swaps a mailbox to a different account. It is offered on a working mailbox too — if the authorization expires, Ronja will tell you the mailbox needs reconnecting, and this is where you do it. Completing a reconnect on a healthy mailbox is safe and changes nothing — but if you start a Reconnect and close the popup without finishing, Ronja pauses the mailbox after about 15 minutes to be safe; click Reconnect again to finish. Pending means a connection was started but hasn’t come back yet.

Disconnect a mailbox

Click Disconnect on the mailbox card and confirm.

Disconnecting deletes the stored credential and withdraws Ronja’s access where the provider allows it. She stops reading and replying immediately. Mail she already sent stays sent, and nothing in the mailbox itself is deleted or changed. You can connect the same address again later.

Any automation on a Mailbox trigger watching this mailbox is switched off at the same time, rather than left on against a mailbox that no longer exists. Each one says why, and says what to do.

Connecting the address again does not bring those automations back on its own. A reconnected mailbox is a new mailbox as far as Ronja is concerned, even at the same address — so each automation has to be pointed at it before it can run again. Open the automation, pick the newly connected mailbox in its trigger, save, and switch it back on. Ronja refuses a plain re-enable while the automation still points at the mailbox you disconnected, rather than letting it read Active and quietly never fire.

Re-enabling starts it from that moment, so mail that arrived while it was off is not worked through.

For a Gmail mailbox, Ronja asks Google to withdraw its access. If Google doesn’t confirm, Ronja tells you so and shows the manual step — the credential is deleted from Ronja either way, but to be certain, remove Ronja from that account’s third-party access under Google Account → Security → Your connections to third-party apps & services.

For an Outlook mailbox, Microsoft offers no way for an app to withdraw its own access, so Ronja shows an optional tidy-up step instead. Ronja can no longer read or send from the mailbox the moment you disconnect — the stored credential is gone — but the authorization record stays in your Microsoft account until you remove it at myapplications.microsoft.com → Ronja → Revoke permissions.

Related

• Use Ronja in Slack and Microsoft Teams — the other way to bring Ronja to where people already talk.
• Schedule an automation — including the Mailbox trigger that answers this inbox, and the Email trigger, which is a different thing entirely.
• What’s the difference? — connected mailbox vs email notifications vs the email-trigger address.