SuperOps IT

SuperOps IT + Konnectify

SuperOps IT Integration with Konnectify

Connect SuperOps IT to Konnectify to automate ITSM operations—sync tickets, tasks, assets, and service items with real-time polling triggers, enrichment actions, and reliable workflow orchestration.

Tickets Tasks Assets Sites Service Catalog Service Items Knowledge Base 5 Triggers 19 Actions

ON THIS PAGE

→ What is SuperOps IT? → API & authentication → How to connect → Triggers (5) → Actions (19) → Popular automations → FAQ

What is SuperOps IT?

SuperOps IT is a cloud-based ITSM platform built for IT service teams to manage tickets and service items efficiently, supported by automation, real-time insights, and reporting.

By integrating SuperOps IT with Konnectify, you can route and enrich ticket updates, automate task creation, synchronize asset changes, and orchestrate consistent IT operations across your PSA/RMM stack and downstream tools.

New to SuperOps IT?

Create your SuperOps account and set up your ITSM workspace (tickets, assets, service catalog).

Visit SuperOps →

New to Konnectify?

Build workflows with polling triggers, branching logic, and multi-app automations—without managing infrastructure.

What you can automate

Create and update tickets from other systems
Notify teams when tickets are created or updated
Create tasks automatically based on ticket events

Sync asset creation/updates to CMDB or inventory
Pull ticket notes and conversations for auditing
Fetch service catalog, service items, and KB items for self-service workflows

API & authentication

Authentication method: API Key (credentials)

Konnectify connects to SuperOps IT using an API Key and your SuperOps Base URL plus Domain. The API key is used on each request to authenticate calls to the SuperOps IT API.

Connection fields

API Key: your SuperOps IT API key
Base URL: e.g. https://api.superops.ai/it or https://euapi.superops.ai/it
Domain: your SuperOps tenant domain (e.g. my-company)

What the API can do

Read tickets, tasks, sites, assets, KB items, and service catalog data
Create tickets, tasks, service items, and ticket notes
Update tickets and fetch ticket conversations/notes

Rate limits & plan considerations

SuperOps IT API access, endpoints, and rate limits may vary by plan and region. If you see throttling errors or delayed polling results, reduce trigger frequency and/or add retry/backoff logic in your workflow.

Official docs: SuperOps IT developer/API documentation (refer to your SuperOps portal for the most up-to-date API reference)

How to connect

Prerequisites

A SuperOps IT account with API access
Your SuperOps API Key, Base URL (US/EU), and Domain
Permission to read/write the objects you want to automate (tickets, tasks, assets, service items)

Add SuperOps IT to a Workflow

Create a new Workflow in Konnectify.
Choose SuperOps IT as your trigger app or as an action step.

Authorize via API Key authentication

Click Connect when prompted.
Enter your API Key, Base URL, and Domain.
Save the connection.

Configure the Trigger or Action

Select the trigger (e.g., New Ticket Created) or an action (e.g., Create Ticket).
Map required fields such as Ticket ID, Asset ID, or content fields for notes/tasks.
Optionally add filters, branching, and retries.

Important Double-check the Base URL region (US vs EU) and your Domain. Incorrect values are the most common cause of authentication and “not found” errors.

Test the Workflow

Run a test using a known Ticket/Task/Asset ID.
Verify the output fields (e.g., notes, conversation messages, asset summaries).

Activate the Workflow

Turn on the workflow.
Monitor the first few runs to confirm polling intervals and expected updates.

Triggers 5

SuperOps IT triggers in Konnectify are polling triggers—Konnectify periodically checks SuperOps for new or updated records and emits events into your workflow.

Tickets 2 triggers

New Ticket Created

Polls the SuperOps API to detect newly created tickets since the last run.

Ticket Updated

Polls the SuperOps API to detect tickets updated since the last run.

Tasks 1 triggers

New Task Created

Polls the SuperOps API to detect newly created task since the last run.

Add another app step to act on new tasks (e.g., notifications, logging, or ticket updates).

Assets 2 triggers

Asset Updated

Polls the SuperOps API to detect assets updated since the last run.

New Asset Created

Polls the SuperOps API to detect assets created since the last run.

Actions 19

Use SuperOps IT actions to fetch records for enrichment, list objects for synchronization, and create/update operational items like tickets, tasks, service items, and notes.

Tickets 8 actions

Get Ticket

Retrieves detailed information about a specific ticket using its ticket ID.

Get Ticket Notes

Retrieves all notes added to a ticket using its Ticket ID.

Get Ticket Conversation

Retrieves all conversation messages for a ticket using its Ticket ID.

Get All Ticket List

Retrieves All Tickets

Create Ticket Note

Creates a new note on a ticket.

Create Ticket

Create a Ticket in SuperOps.

Update Ticket

Update a ticket in SuperOps

Get Service Item

Retrieves detailed information about a service item using its Item ID.

Tasks 2 actions

Get Task

Retrieves detailed information about a task using its Task ID.

Create Task

Creates a new task in SuperOps.

Assets 3 actions

Get Asset

Retrieves detailed information about a asset

Get Asset Summary

Retrieves key summary information about an asset using its Asset ID.

Get All Assets

Retrieve All Assets

Tip: use Asset Updated trigger + Get Asset Summary to reduce payload and speed up downstream routing.

Sites 1 actions

Get Site

Retrieves detailed information about a site using its Site ID.

Use sites to route workflows by customer/location (e.g., different SLAs or notification rules).

Service Catalog Items 2 actions

Get Service Catalog Item

Retrieves detailed information about a service catalog item using its Item ID.

Get All Service Catalog Items

Retrieve All Service Catalog Items

Service Items 1 actions

Create Service Item

Creates a new service item in SuperOps,

Best practice: store the created Service Item ID in your source system to avoid duplicates.

Knowledge Base Items 2 actions

Get Knowledge Base Item

Retrieves detailed information about a knowledge base item using its Item ID.

Get All KB Items

Retrieve All Knowledge Base Items

Popular automations

Example workflows you can build with SuperOps IT + Konnectify using the available triggers and actions:

Enrich every new ticket with full details + initial note

When a ticket is created, pull the full ticket payload and append a standardized triage note (SLA, escalation rules, next steps).

New Ticket Created → Get Ticket → Create Ticket Note

Create a follow-up task for every new task (checklists or routing)

When a task appears in SuperOps, fetch details and automatically create a related task (e.g., QA step, approval, or handoff).

New Task Created → Get Task → Create Task

Keep asset updates visible by writing a ticket note

When an asset changes, pull a compact summary and record it in a ticket note (useful for change tracking and audit trails).

Asset Updated → Get Asset Summary → Create Ticket Note

Auto-triage: update tickets when conversation or notes change

When a ticket is updated, pull the latest notes/conversation and update the ticket fields (priority/status/owner) based on keywords or rules.

Ticket Updated → Get Ticket Conversation → Update Ticket

FAQ

How does Konnectify authenticate with SuperOps IT?

This integration uses API Key authentication. You provide an API Key along with the correct regional Base URL (US/EU) and your tenant Domain. Konnectify uses these credentials to sign API requests to SuperOps IT.

Which SuperOps IT plans are supported?

Any SuperOps IT plan that provides API access for the endpoints used (tickets, tasks, assets, service catalog/items, KB) should work. If an endpoint returns authorization errors, verify your plan includes API access and that the API key has the needed permissions.

Are the SuperOps IT triggers polling or webhooks?

All available triggers for this connector are polling triggers (e.g., “New Ticket Created”, “Ticket Updated”, “Asset Updated”). Konnectify checks SuperOps periodically and uses a cursor to continue from the last successful run.

How do I prevent duplicates?

This connector does not expose an explicit “upsert” action in the current version. To prevent duplicates, store the created SuperOps object ID (Ticket ID / Task ID / Service Item ID) in your source system, or add a lookup step (e.g., list/search in your other app) before creating new records.

How does Konnectify handle rate limits and retries?

If SuperOps responds with throttling or transient errors, reduce polling frequency and enable retry/backoff in your workflow steps (where available). For high-volume environments, consider batching logic across your workflow (e.g., process only changed fields or use “Get Asset Summary” instead of “Get Asset”).

Can I connect multiple SuperOps IT accounts or regions?

Yes. Create separate connections for each tenant/region by using different API Key, Base URL (US/EU), and Domain values. Then select the desired connection per workflow step.

What’s the difference between Ticket Notes and Ticket Conversation actions?

Use Get Ticket Notes to retrieve internal notes added to a ticket, and Get Ticket Conversation to retrieve conversation messages (often used for communications/history). If you’re building an audit trail or syncing communications to another system, conversations are typically more complete; for internal runbooks, notes may be the better source.

Ready to automate your SuperOps IT workflows?

Connect SuperOps IT to Konnectify and start building reliable ticketing, task, and asset automations in minutes.

Get started free →