Working with integrations

The core abilities cover WordPress itself — posts, terms, users, media, files, code. An integration adds abilities that speak one plugin's own language: Advanced Custom Fields field groups, Bricks templates, Gravity Forms feeds and notifications, Bit Form's own database tables. Without one, an assistant can only reach such a plugin the long way round.

1. Open NibWP → Integrations. Each plugin or service is a card, with a switch and a badge.
2. Read the badge. Detected — switch on to use means the plugin is installed and active here. Not detected means the card exists but the plugin does not. Active means you have switched it on, Locked — needs Pro that it is a premium card, and Always on that it cannot be switched off.
3. Switch on what you need. Activate detected turns on every card whose plugin is actually present, which is usually the right first move. Activate all and Deactivate all are next to it, and you can filter by All, Free or Premium, search, or sort by which plugins were detected.
4. Confirm in NibWP → AI Abilities. The new tools appear there as rows. Reconnect or refresh the tool list in your AI client so it sees them too.

Two things to expect. An integration's abilities only load when the plugin is detected, the card is switched on, and the card is unlocked — so switching one on for a plugin you do not have adds nothing until you install it. And premium cards carry a PRO badge: they need a Pro or Bundle licence, though a standalone Skill licence unlocks the integrations that Skill declares.

If a plugin you rely on has no card, the Need a custom Integration? button on that screen sends the request to us.

Full guide: How to: work with integrations