IT OPS
Onboarding Form to Multi-SaaS Account Fan-Out
Takes a submitted IT onboarding intake form and fans out account creation across CRM, project tracking, and ticketing tools in parallel, then collects the results.
How it runs
The automated pipeline, trigger to output.
- TriggerOnboarding intake form submittedHTTP webhook
- LogicSelect required tool seats by role
- ActionCreate CRM user in HubSpotHubSpot
- ActionAdd to projects in AsanaAsana
- ActionProvision Zendesk agent seatZendesk
- OutputPost consolidated result card to SlackSlack
What it does
Converts a single onboarding intake submission into accounts across every line-of-business tool a hire needs. Where the day-one bundle covers core infrastructure, this fans out to the work-app layer: CRM, project tracker, and helpdesk.
When to use it
Use this when new hires need seats in many specialized SaaS tools and creating each by hand is the bottleneck. It is ideal for sales and support teams whose tooling lives outside the standard email-and-chat stack.
How it works
- 1A webhook fires when the IT intake form is submitted with the hire's role and team.
- 2A logic step selects which tool seats the role requires.
- 3A HubSpot action creates the CRM user and assigns the right team and pipeline visibility.
- 4An Asana action adds them to the relevant projects and portfolio.
- 5A Zendesk action provisions an agent seat scoped to their support group.
- 6A final Slack message posts a consolidated result card showing each account's status and any seat-limit errors.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect HubSpotCRM, deals, marketing, support.
- 3Connect AsanaTasks, projects, milestones — everywhere.
- 4Connect ZendeskTickets, queues, knowledge base.
- 5Connect SlackChannels, DMs, threads, mentions.
- 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.