IT OPS
Agent-driven full onboarding kit for a new department mailbox
An agent takes a new-department brief, provisions the Outlook shared mailbox, configures signature and auto-reply, creates a Teams channel, and files an onboarding doc.
How it runs
The automated pipeline, trigger to output.
- TriggerDepartment onboarding brief reaches Done-planning in Mondaymonday.com
- LogicAgent decides which kit components the department needs
- ActionProvision shared mailbox in Exchange OnlineShell
- ActionSet signature and auto-reply in OutlookOutlook
- ActionCreate linked department channel in TeamsMicrosoft Teams
- OutputPublish Confluence onboarding page and mark brief completeConfluence
What it does
Goes beyond just creating a mailbox: an agent assembles a complete department comms kit, deciding which pieces a given department needs based on its onboarding brief.
When to use it
Use this for the white-glove launch of a customer-facing or high-touch department where a bare mailbox is not enough — you want branded signatures, an auto-reply, a Teams home, and documentation all set up together.
How it works
- 1The Monday onboarding brief reaches the Done-planning stage, triggering the agent.
- 2The agent reads the brief and decides which kit components apply (some departments need an auto-reply, others do not).
- 3A shell step provisions the shared mailbox in Exchange Online.
- 4An Outlook step sets the mailbox signature and, where required, a business-hours auto-reply.
- 5An ms-teams step creates a department channel linked to the mailbox for internal coordination.
- 6The agent writes a Confluence onboarding page documenting the mailbox, owners, and conventions, then marks the brief complete.
Set it up
What you configure once, before turning it on.
- 1Connect monday.comVisual work management for teams.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 3Connect OutlookMail, calendar, contacts.
- 4Connect Microsoft TeamsChannels, chats, files.
- 5Connect ConfluenceSpaces, pages, blueprints.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More IT Ops workflows
Recurring Sensor Fault Root-Cause Investigator
On a schedule, an agent reviews recent Monday work orders and BigQuery telemetry to identify equipment with repeating faults, drafts a root-cause hypothesis with a recommended fix.
Daily Building Anomaly Digest to MS Teams
Each morning queries BigQuery for the prior day's flagged sensor anomalies, summarizes them by site and system into a ranked briefing.
Agentic Inactive-Seat Reclamation Review
An agent investigates each idle SaaS seat by correlating SSO login gaps with HR status and ticket history, classifies it as reclaim, hold, or escalate, and drafts a reasoned…
Reconcile SSO logins against expense spend to find unmanaged tools
Joins SSO usage data with expense/payment records in Snowflake to surface tools that are being used but not paid for, or paid for but never logged.
Approved-Seat Deprovision Execution
Fires when an IT approver confirms a seat for removal, then executes deprovisioning via the IdP API and logs the action to an audit table and a Linear cleanup ticket.
HVAC Anomaly Detection to Severity-Routed Work Orders
Ingests building HVAC telemetry via webhook, flags out-of-band temperature, pressure, or runtime readings.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.