How to: work with integrations

NIBWP is powerful on its own, but it gets dramatically more useful the moment you have other plugins active — because it turns each one into agent-callable tools. The Integrations panel is where you see which of your plugins NIBWP has detected and what abilities each one contributes. This guide explains how integrations work, how to enable and use them, and how to think about the new powers they unlock.

Open the Integrations panel

Go to NIBWP › Integrations. You will see a directory of supported plugins, each marked active, available or pro. Active integrations are contributing abilities right now; the panel tells you exactly what each exposes.

How integrations work

There is almost nothing to configure. When a supported plugin is active, NIBWP introspects it — reads its post types, taxonomies, fields and data model — and exposes typed tools for it automatically. Deactivate the plugin and its tools disappear. This is why your agents can work ACF fields, WooCommerce products or FluentCRM contacts without you writing a line of glue code.

Step 1 — See what is detected

Scan the panel for your active plugins. Each shows its status and ability count. If a plugin you expect is missing, confirm it is active — NIBWP only exposes active plugins.

Step 2 — Explore what an integration exposes

Click an integration to see its abilities, or ask a connected agent directly. For example, with ACF active:

You: What can you do with ACF on this site?\nnibwp/acf-manage-fields - read + write field groups and values\nI can read and create ACF field groups, and set field values on posts.

Step 3 — Put it to work

Once an integration is active, your agent can operate that plugin through plain-language instructions — bulk-updating WooCommerce products, managing FluentCRM contacts, filling ACF fields across many posts. The integrations reference documents each one, and the case studies show full builds.

Safety with integrations

Integration abilities follow the same model as everything else — they respect token scopes, honor force-draft, are rate-limited, and are logged. A WooCommerce write through an integration is as controlled as any other write.

FAQ