Plugins

Everything else on this site is about calling into Biflus — reading and writing your own account's clients, items, and invoices. A plugin is the other direction: code Biflus calls out to, to add a real capability inside the product itself.

Early stage, reviewed by hand. Plugins are a genuinely new part of Biflus. Every submission is reviewed before it can run against a real account's data — there's no self-serve marketplace yet, just a working submission and review flow.

What a plugin can do

A working example already exists: a Shopify integration that pulls a store's product catalog into Biflus as real, reusable Items — matched and kept in sync by SKU, not a one-time import. That's the shape a plugin takes: something a Biflus account can turn on, that then does real work inside the product on its own.

How it works

When an account enables a plugin, Biflus can call the plugin's own webhook with a small JSON payload identifying which account and what triggered the call. The plugin does whatever it needs to, then writes the result back through Biflus's own API using the same credentials every other integration on this site uses.

POSTyour-service.example.com/webhook Called by Biflus, not the other way around

Submit a plugin

Plugin submission, review, and approval happen on a separate site built specifically for it: plugins.biflus.com. That's also where the exact payload shape and write-back contract are documented in full.