Skip to content

Mailbox Triggers ​

Mailbox triggers turn an unattended mailbox into a source of runbook runs. Vendor notices, renewal reminders, invoices, and alert emails often land in a shared mailbox nobody reads. Connect that mailbox to Junto as a monitored mailbox, describe each kind of email worth acting on as a trigger, and attach runbooks to the trigger. When a new email matches, the attached runbooks start.

You describe a trigger in plain words, not with rules or filters. Junto checks every new email in the mailbox against your triggers and records why each one matched or was skipped.

How It Works ​

  1. Add a monitored mailbox under Settings > Integrations > Email Mailbox.
  2. Create a trigger that describes one kind of email, and test it against the mailbox's recent mail.
  3. Attach a runbook to the trigger from the runbook's page.
  4. Junto checks new mail every couple of minutes. A matching email starts every runbook attached to its trigger.

A monitored mailbox never files tickets. Unlike a forwarded email mailbox, its only job is to start runbooks.

Only users with the Admin or Owner role can manage monitored mailboxes, triggers, and runbook attachments.

Adding a Monitored Mailbox ​

Monitored mailboxes must be Microsoft 365 mailboxes.

  1. Go to Settings > Integrations > Email Mailbox. If this is your first mailbox, grant admin consent first (see Email Mailbox).
  2. Click Add mailbox (choose Microsoft 365 if asked) and sign in.
  3. When asked how the mailbox will be used, choose Monitored mailbox.
  4. Confirm the Email address (change it to a shared mailbox address if needed) and give it a Display name, such as "Vendor notices".
  5. Click Add mailbox.

The mailbox card shows Monitored mailbox and a Triggers button. Mail is not read until the mailbox has at least one trigger, and checking starts with mail that arrives after that. Mail that arrives while the mailbox has no triggers, or while it is inactive, is never checked later, so a days-old email can't start a runbook when checking resumes.

Creating a Trigger ​

A trigger describes one kind of email worth acting on.

  1. On the mailbox card, click Triggers, then New trigger.
  2. Fill in the form:
FieldDescription
NameA short label, unique within the mailbox (e.g., "Vendor invoice over $5,000").
What to look forA plain-language description of the email, 10 to 2,000 characters. Say what should not count as well as what should.
Only from this domain (optional)Limits the trigger to one sender domain, such as vendor.com. Only mail verified as coming from that exact domain can match.
  1. Click Test on recent mail to see what the description would have done (see below).
  2. Click Create trigger.

Writing a Good Description ​

Every email in the mailbox is checked against your triggers, and most of a shared mailbox is noise. Describe the email as precisely as you would to a new colleague, and name the near-misses to ignore. For example:

An invoice or bill from a vendor for more than $5,000. Not marketing, receipts for payments already made, or quotes.

A newsletter or automated notice that only mentions the same topic does not match unless your description asks for it. Each email matches at most one trigger. When more than one could apply, the most specific one wins.

Anyone can send email to a mailbox, and the From address is easy to forge. Use Only from this domain for any trigger whose runbook acts on what the email says, so a spoofed message can't start it.

Testing on Recent Mail ​

Test on recent mail checks your draft against the mailbox's most recent emails from the last day (up to 30) without saving anything or starting a runbook. The result reads "Matched X of the N most recent emails" and lists each email with a Match or Skip badge, its subject and sender, and a one-line reason.

Adjust the description until it matches the emails you want and skips the rest. Editing the description or domain clears the result, so test again after each change. If no mail arrived in the last day, there is nothing to test against.

Managing Triggers ​

The Triggers tab lists each trigger with its domain limit (shown as From domain), its description, and the runbooks it starts. Use Edit to change a trigger, or Delete and then Confirm delete to remove it.

Checked Emails ​

The Checked emails tab shows every email the mailbox checked, newest first, with Received, From, Subject, and Result columns. Turn on Matches only to hide skipped mail.

  • Result shows the matched trigger's name, Skipped, or Not checked (the check failed after several retries).
  • The reason for the decision appears under the subject.
  • Sender not verified appears under the sender when the email could not be verified as coming from its From address.
  • For a matched email, the result also shows what happened to each attached runbook: 1 run started, Waiting to start a run, No runbook is attached to this trigger, or why a run was skipped.

Skipped emails are kept for 30 days without their text, so you can spot one that should have matched and refine the trigger.

Starting Runbooks from a Mailbox Trigger ​

  1. Open a published runbook and click Triggers (next to Run now and Schedule).
  2. Click Attach trigger and choose:
    • Trigger -- mailbox triggers are listed under the mailbox address, alongside any incoming webhook triggers.
    • Company -- required if the runbook files a completion ticket; otherwise optional. Leave it empty to let the run work across companies.
    • Board / Queue -- shown when the runbook files a ticket, labelled for your PSA.
    • Fill runbook inputs from the trigger -- map each runbook input to a field of the email, such as subject, from_address, from_domain, received_at, or body, or leave it unfilled.
    • Wait for the sender to go quiet -- defaults to Don't wait: start a run for every delivery, so each matching email gets its own run. Choose a wait only if you want related emails grouped into one run.
  3. Click Attach trigger.

Each attachment can be paused with its Active switch or removed with Detach, the same as a webhook attachment.

How Mailbox Runs Behave ​

  • Runs act as the person who attached the trigger, with that person's connections and permissions. If that user is removed or is no longer an Admin, runs are skipped until someone else re-attaches the trigger.
  • The email is data, not instructions. The run receives the mapped inputs, the email's sender, subject, and text, and the reason it matched. Nothing written in the email is treated as an instruction to the agent.
  • Runs are unattended. Nobody is watching a mailbox run, so it follows the same tool rules as an auto-run: tools referenced in the steps run without prompts, high-risk tools run only if they were approved for unattended runs when auto-run was turned on, and escalation-tier tools wait for an approver. See Runbook Safety & Controls.
  • Limits: one run per email per attachment, two runs of the same attachment in flight at a time, and 20 runs per mailbox per hour. A matching email that arrives while two runs are still going waits for a free slot for up to 24 hours rather than being dropped.
  • Mailbox runs appear on the runbook's Runs page and in Executions & Monitoring with a Mailbox badge.

To stop checking a mailbox, edit it and turn off Active, or delete it. Turning a mailbox off also stops any matched email that is still waiting for a run slot.

Troubleshooting ​

  • No emails appear under Checked emails -- The mailbox needs at least one trigger and must be Active. Only mail that arrives after the first trigger is saved is checked.
  • An email that should have matched was skipped -- Read the reason under its subject, then make the trigger's description more specific and use Test on recent mail to confirm. If the trigger has a domain limit, check that the email came from that exact domain and wasn't marked Sender not verified.
  • The wrong trigger matched -- Each email matches only the most specific trigger. Tighten the overlapping descriptions and say what each one should not include.
  • An email shows Not checked -- The check failed repeatedly. The email is not retried; if it mattered, start the runbook with Run now.
  • Matched, but no run started -- The result names the reason: no runbook is attached, the runbook is not published, the attachment is paused, the attaching user lost Admin access, the mailbox was turned off, or the mailbox hit its hourly run limit.
  • Could not test the instructions -- Junto couldn't read the mailbox's recent mail or the check was briefly unavailable. Confirm the mailbox connection is healthy and try again.
  • The mailbox card shows an error -- Reconnect the mailbox if the error mentions credentials. If it says the mailbox has no trigger source, remove the mailbox and add it again.