Using WordPress? Every integration here is also available as a plugin. Browse the plugin store →
Questions
Answers to the 16 questions asked most often about WPIntegrate: what a component is, what it can reach in your Microsoft 365 tenant, what the WordPress plugins cost, and what is and is not on sale today.
01 / 04
A component is a custom HTML element that renders live Microsoft 365 data inside your own page. You paste two lines — a script tag that loads the bundle, and the element itself carrying an embed key — and everything else about it, which Microsoft 365 source it reads, how it is laid out, what colours it takes, resolves from that key at boot. Changing any of it later never means editing the page again.
No. Access to Microsoft 365 is resolved on our side of the request, not in the visitor’s browser, so nobody is asked to sign in to Microsoft to see a booking form, a document library or a team directory. What the visitor gets is an ordinary part of your page.
Yes. A custom element runs in any framework or in plain HTML with no build step, so the same two lines work in Astro, Next.js, Webflow, Squarespace, a SharePoint page or a static file you edit by hand. WordPress is the one platform that also gets the job as a plugin with a Gutenberg block.
No, unless you want to. In managed mode your IT administrator is asked to grant consent once, and that is the whole of what your side has to do. In proxy mode you supply your own gateway base URL and API key, which means you register the application and we never hold a Microsoft Graph token at all.
Only if you want it to. Widgets are white-labelled: a tenant sets a brand theme and any single instance can override it, so the host page’s brand wins including its dark mode. The design system supplies defaults rather than mandates, and WPIntegrate branding stops at the boundary of our own properties.
02 / 04
Nowhere new. Components read Microsoft 365 at the moment the visitor looks rather than keeping a copy, so what is on the page is what is in SharePoint, Outlook or Entra ID. Form submissions are not stored either: they are delivered to the destination you configure — email, webhook or a Microsoft 365 target — and we keep no copy of them. A booking writes the appointment into your own Microsoft 365; the short-lived record we need to complete and reconcile it is deleted automatically.
Yes, in proxy mode. You supply a base URL and an API key for a gateway you run; we store that key encrypted at rest and forward to it, so Graph traffic never leaves your perimeter and the audit log is yours. The embed on the page is identical either way, so the decision is an infrastructure one rather than a content one.
Only what the consented scopes allow, and only for the source that instance is configured against. Licensing is checked server-side on every configuration request, and an embed key renders only on the domains you list — so a copied snippet does not work somewhere else.
WCAG 2.1 AA, self-imposed rather than contractual. It is treated as a hard gate because the widgets render inside your website, which makes any contrast or semantics failure we ship your accessibility failure on your domain. Every foreground and background pair in the design system is verified in both light and dark before it can be built.
03 / 04
Not yet. The component platform is in pre-launch, so the channel open today is the WordPress plugin store at plugins.wpintegrate.com. If a component rather than a plugin is what you need, say so through the contact page — named demand is what sets the order components are released in.
Each plugin is priced on its own page, and there are 19 of them. Most are sold through our own store at plugins.wpintegrate.com; a handful are listed on CodeCanyon instead, and those carry that marketplace’s price and terms rather than ours.
Yes. Installed plugins call api.wpintegrate.com for update metadata and licence checks, and that endpoint stays live. Nothing we ship is allowed to quietly break a site that has not upgraded — that is a standing product principle, not a transitional promise.
No. Both lines are permanent and neither is a funnel for the other. The plugins are for teams who live inside WordPress; the components are for everyone else, including WordPress sites that would rather embed than install.
04 / 04
Yes — that is one of the three audiences the product is built for. Each customer organisation is its own tenant with its own brand theme and its own component instances, and any single instance can override the theme, so nothing on a client’s site has to carry our name. There is no reseller programme to sign up to today.
Three named engagements, and they are listed with their starting figures on the services page: a branding package, a nonprofit grant management solution and a professional association member portal. Anything outside those shapes starts as a conversation rather than a quote, because what it costs depends on what you already have.
Existing plugin customers reach downloads and licence keys through their store account at plugins.wpintegrate.com. For anything else — a question before buying, a problem after, or an enquiry about a component — the contact page is the route, and it reaches a person rather than a queue.
This page is written from what people actually send us, so a question that is missing is a gap rather than a boundary. The plugin store is open today; the component platform is in pre-launch and collecting named demand.