Liongard
+
Konnectify
Liongard Integration with Konnectify
Connect Liongard to Konnectify to monitor and manage IT environments, devices, systems, metrics, and users—then automatically sync changes into your downstream tools and operational workflows.
Environments
Agents
Alerts
Systems
Users
Launchpoints
Devices
Inspectors
Metrics
13 Triggers
17 Actions
What is Liongard?
Liongard is an IT documentation and monitoring platform that discovers, inventories, and tracks changes across customer environments—covering systems, devices, users, and operational metrics.
With Konnectify, you can turn Liongard change events into automated workflows: enrich records, create follow-up tasks, update dashboards, and keep tools like ticketing, CMDB, and alerting systems in sync.
New to Liongard?
Create an account and set up your first inspector to start collecting inventory and change data.
Visit Liongard →
New to Konnectify?
Build workflows across your IT toolchain with triggers, actions, routing, and data mapping.
Sign up for Konnectify →
What you can automate
• Sync newly created environments to your CMDB
• Track agent additions/updates and notify your team
• Route new alerts (tasks) into ticketing or chat
• Enrich device inventory with lookups and tagging
• Create/update launchpoints programmatically
• Manage inspector metrics (create/update/delete) at scale
API & Authentication
Authentication method: API credentials
This integration uses credential-based authentication with a API ID, API Secret, and your Liongard Instance (for example, us1). Konnectify stores these securely to authenticate API requests to Liongard on your behalf.
API coverage in this connector
- Environments: create, update, delete, fetch details
- Agents: update, delete, fetch details
- Alerts (tasks): fetch details
- Inventory: find device profiles
- Launchpoints: create, update, find, delete
- Metrics: create, update, delete
- Systems & Users: find and fetch details
Important notes
Rate limits & access: Liongard API availability and rate limits can vary by plan and tenant configuration. If you see intermittent failures, reduce polling frequency and avoid large burst updates.
How to connect Liongard to Konnectify
Prerequisites
- A Liongard account with API access enabled
- Your API ID and API Secret
- Your Liongard Instance name (example:
us1)
- A Konnectify workflow where you can add a Liongard trigger or action
Add Liongard to a Workflow
- In Konnectify, open an existing workflow or create a new one.
- Click Add step and choose Liongard from the app list.
Authorize via API credentials
- Enter your API ID and API Secret.
- Set Instance (example:
us1).
- Save the connection.
Configure the Trigger or Action
- Select the Liongard event you want to monitor (trigger) or the operation you want to run (action).
- Fill in required fields (IDs, environment references, and any filter fields).
- Map outputs from previous steps into Liongard inputs as needed.
Tip: Actions like Get Environment, Get Agent, and Find Device require the correct Liongard IDs. If you’re unsure which ID to use, add a lookup step first (or capture the ID from a trigger payload).
Test the Workflow
- Run a test to confirm authentication succeeds.
- Verify the step outputs contain the expected Liongard objects (environment, agent, metric, etc.).
Activate the Workflow
- Turn the workflow on.
- Monitor the first few runs to confirm polling frequency and results match expectations.
Triggers
13
This connector includes 13 polling triggers. Konnectify periodically checks Liongard for new or updated records and then starts your workflow when matches are found.
Environments
2 triggers
New Added Environment
Monitors for newly created environments in your Liongard instance.
Updated Environment
Monitors for updated environments in your Liongard instance.
Agents
2 triggers
New Agent Added
Monitors for newly created agents.
Agent Updated
Monitors for updated agents.
Alerts
1 trigger
New Added Alerts (Tasks)
Monitors for newly created Alerts (tasks).
Systems
2 triggers
New System Added
Monitors for newly created systems.
System Updated
Monitors for updated systems.
Users
1 trigger
New User Added
Monitors for newly created users.
Launchpoints
1 trigger
New Launchpoint Added
Monitors for newly created launchpoints.
Devices
1 trigger
New Device Created
Monitors for newly created devices in your Liongard environment.
Inspectors
1 trigger
New Inspector Added
Monitors for newly created inspectors.
Metrics
2 triggers
New Metric Added
Monitors for newly created metrics.
Metric Updated
Monitors for updated metrics.
Actions
17
Use actions to create, update, find, and delete Liongard records from inside your workflows.
Environments
4 actions
Create Environment
Creates a new environment in Liongard.
Update Environment
Updates an existing environment in Liongard.
Delete Environment
Deletes an environment from Liongard.
Get Environment
Fetches detailed information about a specific environment from Liongard.
Agents
4 actions
Update Agent
Updates an existing agent in an environment.
Delete Agent
Deletes an agent from Liongard.
Get Agent
Fetches detailed information about a specific agent from Liongard.
Get Alert
Fetches detailed information about a specific alert (task) from Liongard.
Systems
1 action
Find System
Fetches detailed information about a specific system from Liongard.
Users
1 action
Find User
Fetches detailed information about a specific user from Liongard.
Launchpoints
4 actions
Create Launchpoint
Creates a new launchpoint for an inspector in an environment.
Update Launchpoint
Updates an existing launchpoint for an inspector in an environment.
Find Launchpoint
Fetches detailed information about a specific launchpoint from Liongard.
Delete Launchpoint
Permanently deletes an existing launchpoint using its ID.
Devices
1 action
Find Device
Fetches detailed information about a specific device profile from Liongard's inventory.
Metrics
3 actions
Create Metrics
Creates one or more new metrics for an inspector.
Update Metrics
Updates one or more existing metrics.
Delete Metrics
Deletes one or more metrics from Liongard.
Popular automations
Examples of common Liongard automations you can build with Konnectify using the available triggers and actions.
Auto-enrich new environments
When a new environment is created, pull full details and sync key fields into downstream systems.
New Added Environment
→
Get Environment
→
Update Environment
Validate new devices as they appear
When a new device is discovered, look up its device profile to enrich inventory data and drive follow-up steps.
New Device Created
→
Find Device
Respond to new alert tasks with context
When Liongard creates a new alert (task), fetch the full alert payload for routing, categorization, and escalation.
New Added Alerts (Tasks)
→
Get Alert
Keep inspector metrics aligned
When a metric changes, update related metrics (or create new ones) to keep monitoring consistent across inspectors.
Metric Updated
→
Update Metrics
→
Create Metrics
FAQ
How does authentication work for Liongard in Konnectify?
Liongard connections use API credentials: API ID, API Secret, and your instance name (for example, us1). Konnectify uses these to authenticate API calls securely for your workflow runs.
Which Liongard plans are supported?
The integration works with Liongard accounts that have API access enabled. If an endpoint returns authorization errors, verify API permissions for your tenant and confirm your plan includes the API features you’re using.
Are Liongard triggers webhooks or polling?
All triggers in this connector are polling triggers. Konnectify checks Liongard on an interval and triggers your workflow when it finds new or updated items (environments, agents, systems, metrics, etc.).
How do I prevent duplicates?
This connector does not include a dedicated “upsert” action. To prevent duplicates, store and reuse stable identifiers (like environment ID, agent ID, device profile ID) and add a lookup step before “create” operations. When possible, prefer “update” actions once you have the Liongard object ID.
What happens if Liongard rate limits my workflow?
If Liongard responds with rate-limit errors, reduce trigger frequency, avoid high fan-out patterns (for example, calling many “Get” actions per trigger event), and add throttling/queueing in your workflow where available. For persistent limits, confirm your tenant’s API limits with Liongard.
Can I connect multiple Liongard accounts/instances?
Yes. Create multiple Liongard connections in Konnectify—each with its own API ID/Secret and instance value—and select the correct connection per workflow (or per step) as needed.
What is the “Instance” field and how do I set it?
“Instance” identifies the Liongard region/tenant host (for example, us1). Use the value provided by your Liongard account or found in your Liongard URL/tenant details. If you enter the wrong instance, authentication may succeed but API calls can fail or return empty results.
Ready to automate your Liongard workflows?
Connect Liongard to Konnectify and build reliable automations across your IT operations stack.
Get started free →