IT OPS
Day-One Welcome Kit and Document Access Setup
Triggered by an onboarding webhook, builds the new hire's welcome kit by creating their personal folder, granting access to role-relevant docs and handbooks.
How it runs
The automated pipeline, trigger to output.
- TriggerOnboarding webhook receivedHTTP webhook
- ActionCreate personal onboarding folderGoogle Drive
- LogicSelect document set by team
- ActionGrant doc access and copy welcome indexGoogle Drive
- ActionPublish handbook links to onboarding spaceConfluence
- OutputDM hire their links and first-day checklistSlack
What it does
Gives a new hire everything they need to read on day one. It creates a personal onboarding folder, shares the right handbooks and runbooks based on their team, drops a curated index doc inside, and sends them a direct welcome message with links so they don't have to hunt for anything.
When to use it
Use this when the friction in onboarding isn't account creation but document discovery — people not knowing where the handbook, IT setup guide, or team wiki lives. Pairs well with a separate provisioning workflow.
How it works
- 1An onboarding system fires a webhook with the hire's name, team, and email.
- 2The flow creates a personal onboarding folder in Google Drive.
- 3It branches on team to select the matching set of shared documents.
- 4It grants the hire read access to those docs and copies a welcome index into their folder.
- 5It publishes the team handbook link set to a Confluence onboarding space entry.
- 6It DMs the hire on Slack with their folder link and first-day checklist.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect Google DriveDocs, sheets, slides, files.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.