Workflows: write the way you work once

A workflow is a playbook you write once: when to use it, the principles behind it, the process in order, the strict rules, the checks that have to pass, and the shape of the final report. NibWP hands it to the assistant as context it must follow, so the same task comes back the same way each time.

• Starters are already there. Open NibWP → Workflows and you have playbooks for page builds, converting HTML or a Figma frame, SEO passes, redirect fixes, pre-launch checks, WooCommerce products, course builds and more. Edit any of them — once edited, it is yours.
• A workflow does not have to be pinned to be used. The assistant loads one on its own when your task matches its "when to use" section.
• Pin one to make it always-on. A pinned workflow is injected as strict context on every request, whatever you ask. Pin it exclusively when you want exactly one set of rules in force and nothing else.
• Revisions are kept. Every edit is saved as a revision, so a rule that turned out wrong can be rolled back.
• Categories keep it organised — Build Sites, SEO, Content, Forms, Automations, E-commerce, Maintenance, or a category you name yourself.
• Share it when it works. Keep a workflow private, share it with your License Circle, or publish it to the community, where other installs can vote on it.

The assistant can write and edit workflows as well, which is the easiest way to start: do the job by hand once, then ask for it to be written up as a workflow and correct the draft. Workflows come with Pro and with the Bundle.

Full guide: Workflows: playbooks your agent follows