Put your Procore project data on your website.
Eighteen shortcodes and a block, reading live from the Procore API: project directories, team members, drawings, specifications, RFIs, submittals, punch lists, observations, daily logs, change orders, schedule milestones, vendors and offices.
Read-only. It never writes to Procore. Nothing this plugin does can change your project data — which is the first question anyone sensible asks about a plugin that holds ERP credentials.
No license key. No activation. No phone-home.
Nothing to register with us and no remote check. The only service contacted is Procore, with your own application credentials, which are encrypted at rest and never rendered back into a page.
Built for the way Procore actually works
- Two authentication modes. A Developer Managed Service Account (OAuth 2.0 client credentials), which keeps working when staff change because it is not tied to a person; or the authorization code grant, acting on behalf of a signed-in Procore user so output respects their own permissions.
- Caching that respects the rate limit. Procore enforces an hourly quota *and* a ten-second spike limit. Every response is cached, with a per-endpoint lifetime you control and a site-wide floor that no single page can undercut — so one shortcode with an aggressive cache setting cannot take your whole app over the limit.
- It degrades, it doesn’t break. If Procore is unreachable, the last good response is served instead of an error. Repeated failures trip a circuit breaker that pauses requests and resumes automatically.
- Real pagination. Result sets are assembled by following Procore’s
Linkheaders, not by guessing page numbers. - Diagnostics that tell you something. The connection test reports each stage separately and probes every endpoint, so you see exactly which Procore tool permissions your credentials have — which is the cause of an empty shortcode nine times out of ten.
wp ibuilder-procore doctordoes the same from the shell.
Privacy is handled, not assumed
Procore project directories contain real people’s contact details. Email addresses are suppressed twice over: a global setting suppresses them, and each shortcode must separately opt in with show_email="true". Both must allow it before an address renders. Turning that off is a deliberate decision, and the plugin makes you make it deliberately.
Procore’s error messages routinely name accounts and permissions, so they are shown to administrators only. Visitors get a neutral message.
Control over the output
Every shortcode takes company_id, project_id, id, limit, page, all, orderby, order, columns, fields, template, class, title, cache and empty_text. Every one is sanitised, and columns and fields are checked against an allow-list — naming a field is not a free pass to read arbitrary Procore data.
“ [ibuilder_procore_rfis project_id="12345" limit="10" columns="number,subject,status,due_date" title="Open RFIs"] “
Also
- A block with a variation per shortcode and a live server-rendered preview in the editor, so an editor sees the real data rather than a placeholder.
- Five theme-overridable templates: copy into
your-theme/ibuilder-procore/and your version loads instead. Overrides survive updates. - An optional read-only, allow-listed REST proxy so your own front-end code can read the same cached data without holding Procore credentials.
- Six WP-CLI commands:
test,doctor,projects,cache_warm,cache_clear,reset_token. - PSR-4 autoloaded,
declare(strict_types=1)throughout, translation-ready. No bundled third-party code at all and nothing from a CDN. - No branding of ours anywhere.
Requirements
WordPress 6.5+, PHP 7.4+ with OpenSSL. You need your own Procore account and your own application registered in the Procore Developer Portal. This plugin does not come with Procore access and cannot provide it. For the service-account mode, a Procore company administrator has to install your app before it can see anything — connecting is not the same as being installed.
Procore is a registered trademark of Procore Technologies, Inc. This plugin is an independent integration and is not affiliated with, endorsed by or sponsored by them.
Full documentation ships inside the zip.