IT Workflow Builder

AssetSonar can automate work tied to assets, software, members, purchase orders, and work orders. Teams can start an asset lifecycle workflow when a record changes or a due date arrives, apply module-specific conditions, then update the record, notify stakeholders, or invoke a connected app. Practical uses include asset assignment and custody updates, inactive-device cleanup, purchase order follow-up, renewal reminders, license reclamation, and audit follow-ups. Available conditions and actions depend on the module selected in the Trigger node, so the builder presents the fields and operations relevant to that record.

Yes. AssetSonar can use ticket events as workflow triggers and apply conditions to route service work using ticket fields. IT teams can automate ticket assignment, send an acknowledgment when a ticket is created, update related records, close eligible tickets, and trigger notifications or escalations around service-level agreement (SLA) risk. Because AssetSonar connects tickets with users, devices, software, and service history, workflow actions can use that context rather than relying only on ticket text. The exact conditions and actions shown depend on the selected ticket event and module configuration.

Yes. AssetSonar can start onboarding or offboarding automation from a member event, HR signal, webhook, or supported app connector. A workflow can use member and asset context to update records, send notifications, call identity or communication systems, and route failed steps for review. For offboarding, documented member automations can revoke licenses and lock devices through supported mobile device management (MDM) controls when a user is deactivated. Prebuilt connectors such as Microsoft Entra and Microsoft Teams, along with custom Web Requests, can extend the process beyond AssetSonar.

Yes, but the configuration depends on the process being automated. The IT Workflow Builder can react to approval events or related record changes, evaluate conditions, and run notifications, record updates, or connected actions. Purchase order approvals use AssetSonar’s dedicated multi-tier procurement workflow controls, where teams can define criteria such as amount, vendor, or delivery location and route requests to named users, roles, or a manager hierarchy. This lets procurement retain its approval-specific routing controls while related follow-up work continues through AssetSonar’s wider automation capabilities.

The module selected in the Trigger node establishes the record context for the workflow. It determines which fields are available for conditions, which in-app actions can be configured, and which placeholders can pass data into later steps. In an asset workflow, for example, downstream nodes can use relevant asset values such as the name, owner, location, or status. Selecting the module first also prevents the builder from presenting actions that do not apply to the triggering record. This module-aware setup makes the canvas an IT workflow designer rather than a generic process diagram.

Yes. AssetSonar provides prebuilt app connectors for supported services. IT teams can use a Webhook trigger to receive an external signal or a Web Request node to call an API. Web Requests support GET, POST, PUT, PATCH, and DELETE methods, along with headers, query parameters, request bodies, pagination, and multiple authentication methods. Data returned by an app connector or API call can be mapped into later workflow steps through expressions and placeholders.

Yes. AssetSonar can process arrays returned by a Web Request or another data-producing node. A Data Transformation node can filter or deduplicate data before it continues. A Split node can separate an API response into individual items, while a Loop node can run connected steps once for each item. Teams can choose whether a loop continues after an item fails or stops at the first failure, then inspect individual iterations in the Execution Logs. Nested Loop nodes are not currently supported.

AssetSonar saves credentials created for Web Requests in a credential vault so they can be reused instead of entered into every node. Prebuilt app connectors prompt for the authentication details required by the selected service, such as OAuth 2.0, and a saved connection can be selected in later workflows. Web Requests support Basic Auth, Header Auth, OAuth 2.0, or No Auth, depending on the endpoint. For the native AssetSonar connector, credentials are prefilled for Account Owners, Administrators, and custom roles with access to Settings.