Can I build my own connector?

Yes. A connector is one PHP class in a folder under /connectors/. You can scaffold it with the no-code Connector Builder in six guided steps or write it directly, implementing only the methods your platform needs. OpsIQ discovers the folder automatically. Most connectors are 200 to 400 lines.

Are connectors signed and safe to install?

You can require a trusted OpsIQ signature for every install and re-verify installed connectors on demand against their signed manifests. Uploaded zips run through a static safety scan that rejects dangerous calls like eval, exec and system before anything is written to disk.

Which platforms are supported?

Billing and hosting (WHMCS, cPanel), payments (Stripe, PayPal, Paystack, Flutterwave, Razorpay, Mollie, Pesapal, plus crypto via NOWPayments and Plisio), eCommerce (Shopify, WooCommerce, Magento, BigCommerce, PrestaShop, OpenCart, osCommerce), CMS (WordPress, custom HTML/JS), communication (Gmail, Mailgun, SendGrid, IMAP/SMTP, Slack, Zendesk, Google Calendar) and every major AI provider.

How do webhooks handle signing and rate limits?

Outbound webhooks are HMAC-signed over the raw body, and inbound requests are verified the same way. Failed deliveries back off and retry automatically, every attempt is recorded in a per-endpoint delivery log, and idempotency keeps retried deliveries from double-acting.

What is the difference between a connector and the API?

A connector is the deep, native path that is discovered automatically and feeds context and actions into the AI. The REST API plus inbound and outbound webhooks is the lighter path that covers almost any use case in a few hours. Many teams start with the API and graduate to a connector later.

Integrations & connectors · the platform

Plug into what you already run.

25+ official connectors and 1,200+ executable actions. The AI works from real platform data and can take action — with your approval. Categorised, live-status flagged, signed and sandboxed, with a clean pattern so you can build your own in an afternoon.

Build a connector Browse the catalog

25+ connectors1,200+ actionsHMAC-signed webhooksNo-code builder

🔐 HMAC-signed

↔ Bidirectional sync

Live

Integrations & connectors

Your data. Your install. One AI brain.

OpsIQ connectors run where your platform already lives: inside your own install, self-hosted or cloud. They pull live context, expose approved actions, verify packages, and keep every signal flowing into the same AI behind chat, tickets, CRM, analytics and promotions.

37+connectors across billing, commerce, support, AI and identity

1,200+actions exposed to the AI with approvals and audit trails

Signedtrusted manifests, integrity checks and upload safety scans

Two-waycontext in, approved action out, events mirrored back

Native architecture

Not a marketplace bolt-on. Part of the platform.

A third-party hub turns your customer data into rented traffic. OpsIQ flips the route: connectors sit inside your install, talk directly to the systems you already run, and become first-class AI context, actions, audience signals and audit events.

Vendor hubmetered runsdata leaves your control

OpsIQ installdirect routecontext, action, identity, events

Your storeYour billingYour siteYour helpdesk

connectors/your_platform/connector.php

contextProviders() registerActions() identityProviders() subscribers() handleWebhook()

Under the hood

One folder. One contract.

A connector is discovered when its folder lands in place. Implement the methods your platform supports; OpsIQ wires the admin UI, AI action contract, events, webhooks and identity layer without changing core code.

Live context inreal platform records inside the AI prompt

Safe operations outrole-gated actions with confirmations

React & receiveevent subscribers and inbound webhooks

Zero UI codesettings.json renders the admin controls

No-code builder

Build a connector in six steps.

The in-app builder walks through identity, auth, test, actions, triggers and review. It keeps testing until the connection returns a clean 200 OK, then generates a signable connector folder.

01Identity

02Auth

03Test

04Actions

05Triggers

06Review

Connector BuilderStep 3 / 6

TEST CONNECTION base_url: https://api.platform.com auth: Bearer •••••••• Connected · 200 OK Generates connector.php + settings.json + actions.json

Data in, actions out

Bidirectional by design.

Inbound email and webhooks become real work. Outbound events stream out signed. Every retry, identity decision and action can be audited back to the source.

Email in. Native ticket out.

Point a mailbox or JSON webhook at OpsIQ. Messages are thread-matched, create-or-append, and attachment-aware.

support@acme#4821 · Refund?Assigned

OUT

Every event streamed signed.

contact.upsertedsha256200 OK

Reference connector

WHMCS, fully wired.

The WHMCS Bridge is the reference for depth: customers, services, invoices, tickets, attachments, identity resolution, AI actions and audience flags all moving through one connector.

Set up the WHMCS Bridge

WHMCScustomers · services · invoices

OpsIQ AItickets · actions · audiences

Supply-chain safety

Signed manifests. Sandboxed installs.

Require a trusted OpsIQ signature before install, re-verify installed connectors against their manifest, and reject dangerous uploaded packages before files touch your server.

Require-signedblock untrusted packages

On-demandhash and integrity re-checks

Static scanreject eval, exec and system calls

Audience capability

Connectors that target.

Any connector can publish an audience catalog and resolve flags for a known visitor. Promotion Studio reads those flags to target real platform state, fail-closed.

Explore promotions

WHMCS flagaudienceFlags()Promotion StudioWin-back offer

What every connector can do

A shared capability surface.

Every connector duck-types the same contract. Implement only what your platform supports, and the matching capability lights up automatically.

Context providers

Live platform data inside the AI prompt.

Universal actions

Platform operations with role gates and audit logs.

Identity resolution

Map anonymous visitors to real customers.

Event subscribers

React to platform, CRM and promotion events.

Bidirectional sync

Backfill records, poll and receive webhooks.

Ticket mirroring

Pull and push replies with attachments.

Audience flags

Publish targeting signals for promotions.

Security sync

Share blocked-IP and risk state.

The connector catalog

Every system, already wired.

Official connectors follow one contract and stay grouped the way teams actually search for them, with live and coming-next signals visible at a glance.

Ship your own

Build your own — or skip the build.

Use the deep native path when you want a full connector. Use the universal API plus inbound and outbound webhooks when a lighter integration gets the job done in hours.

connectors/your_platform/

connectors/your_platform/
├─ connector.php       // extends AbstractConnector
├─ actions.json        // action contract manifest
├─ settings.json       // admin config schema
└─ ContextProvider.php // live data → AI prompt

Skip the build

Use the universal API.

REST endpoints, inbound webhooks and outbound signed events cover most custom integration jobs without a native connector.

Read API docs

Developer guide Read the docs

⚖️ How it compares

Native connectors vs a third-party hub.

What an in-platform, AI-native connector gives you that a bolt-on integration marketplace never will.

Capability	Third-party integration hub	OpsIQ connectors
Live data feeds the AI prompt	—	Context providers, grounded
AI runs platform actions (with approval)	Manual / Zapier steps	1,200+ universal actions
Where your data flows	Through a vendor hub	Directly between your systems
Runs on a self-hosted install	—	✓
Build your own	Limited / paid tier	No-code wizard or one PHP class
Supply-chain safety	Varies	Signed manifests + static scan
Bidirectional ticket mirroring (+ attachments)	Email forward	Both ways, native tickets
Audience targeting from billing state	—	audienceFlags() → Promotion Studio
Per-event pricing	Metered task runs	Included with the platform

Common questions

Connectors, answered.

Everything teams ask before they wire OpsIQ into the systems they already run.

Yes. A connector is one PHP class in a folder under /connectors/<slug>/. You can scaffold it with the no-code Connector Builder (six guided steps) or write it directly — implement only the methods your platform needs, like contextProviders(), registerActions() and handleWebhook(). OpsIQ discovers the folder automatically and renders the admin form from your settings.json. Most connectors are 200–400 lines.

You can require a trusted OpsIQ signature for every install, and re-verify installed connectors on demand against their signed manifests to catch on-disk tampering. Uploaded zips also run through a static safety scan that rejects dangerous calls like eval, exec and system before anything is written to disk.

Billing & hosting, payments, eCommerce, CMS, communication, identity and every major AI provider. If yours isn't listed, you can build it or request it.

Where the platform allows it, yes. Connectors stream live context into the AI, run actions back on the platform, backfill historical records, poll or receive webhooks for ongoing changes, and mirror tickets both ways — including attachments.

Yes. Connectors run on your OpsIQ install whether it's self-hosted or cloud. Data flows directly between your systems and your install — not through a third-party hub.

Outbound webhooks are HMAC-signed over the raw body, and inbound requests are verified the same way. Failed deliveries back off and retry automatically, and idempotency keeps retried deliveries from double-acting.

A connector is the deep, native path. The REST API plus inbound/outbound webhooks is the lighter path that covers almost any use case in a few hours.