Procore, ready to run.
The Procore integration runs the check on whether a contractor is clear to work. Floowed reads the vendor record, the insurance certificates and the licenses, checks them against your requirements, and records what is still missing.
What it does.
What Floowed reads from Procore
- Vendors and subcontractors in the company directory
- Insurance records: type, insurer, policy number, limit, effective and expiry dates
- The license number and trades on the vendor record
- Documents attached to the vendor, whatever their quality
What it writes back
- The compliance status on the insurance record itself
- The reasoning and what is still outstanding, as notes
- The vendor marked prequalified, or made inactive, where the rules say so
The hard part has never been storing the certificate. It is reading an insurer's PDF, finding the expiry and the limit, and knowing whether that satisfies the contract. That is the part we do. In Procore's model, compliance lives on each insurance record (compliant, non-compliant, expired, undecided and their in-progress variants) rather than as one status on the vendor, so we set it record by record.
A subcontractor onboarding case, from invitation to cleared for site.
- Gather
A subcontractor is added to the Procore directory. We pull the vendor record and its insurance records, and the certificate their broker sent to your Outlook inbox.
- Interpret
We read the certificate for insurer, policy number, limit and dates, and the license number on the vendor record.
- Chase
The general liability limit is under your requirement, so we email the broker for an updated certificate and follow up until it arrives.
- Decide
Your requirements run in the deterministic policy engine. A subcontractor who doesn't fit goes to the project manager to decide.
- Act
We set the status and notes on each insurance record, mark the vendor prequalified, send the subcontract through DocuSign and create the supplier in Sage.
Used in the same case
The connection, in detail.
How it connects.
- 1
Connect Procore
Using OAuth 2.0: authorization code for a user, or client credentials through a Developer Managed Service Account. Nothing migrates and nothing is replaced.
- 2
Build your operation
Describe it in Slack, Teams or the Floowed Dashboard. Floowed builds it and asks only what it can’t work out.
- 3
Let it run
Every case runs from request to outcome, the same way each time, with the reasons on record. Anything sensitive waits for a person.
Questions
Does Floowed integrate with Procore?
Yes. The Procore integration connects over OAuth 2.0 across vendors, projects, insurance records and the documents attached to them.
How does the Procore integration connect?
OAuth against your Procore company, scoped to what you approve.
What can Floowed do with Procore data?
Contractor clearance is a document problem wearing a compliance hat. Floowed reads the certificates, pulls out coverage and expiry, checks them against your requirements, sets the status on the insurance record, and chases whoever needs to send a new one.
Do I need to build a workflow to use it?
No. Describe your contractor clearance, connect Procore, and set your own insurance and license requirements.
Is my Procore data secure?
Access is scoped at connect time and revocable there. Every clearance carries its reasoning and a full audit trail, which is the point when someone asks why a contractor was let on site.
What does the Procore integration cost?
Nothing extra. Integrations are included, and you pay for the work Floowed does on a case.
Start with Procore. Add the rest.
Free to try, no card, no sales call. Your first $80 of credits is on us.