This is a public demo. Everything resets in about 43 minutes, so feel free to change anything - your edits will be discarded and nothing here is real data.

iBuilder Connect for Procore

Publish live Procore data on WordPress. Cached, rate-limit aware, read-only.

Procore data rendered on ordinary WordPress pages by shortcode, plus the connection diagnostic with its per-endpoint permission probe — which is the screen anyone who has fought Procore API permissions recognises instantly. Fourteen of sixteen endpoints are readable; two answer 403, and the diagnostic says which and why.

What to look at

Logins

  • Admin, read-only — viewer.demo / ibuilder-demo-viewer (every admin screen opens; saving is refused)

What this demo does not show

This demo is not connected to Procore. A live demo would need a real Procore account, and publishing a real project’s RFI log or team directory on a public site discloses someone else’s commercially sensitive information and someone else’s contact details. So it runs against a local sandbox holding an invented project that belongs to nobody. The OAuth exchange, the permission probe, the caching, the rate-limit handling and the rendering are all the plugin’s own code. Email suppression — the plugin’s default — is left on, which is why the team table shows no addresses.