Construction Management integration
Autodesk Construction Cloud COI compliance integration
Check every supplier contract in Autodesk Construction Cloud, now Autodesk Forma, against the insurance the supplier actually carries. Pikorua Security reads contracts and cost payment applications through Autodesk Platform Services, verifies each supplier's certificate and endorsements, and flags non-compliant suppliers on the contract before the cost manager reviews a payment application.
Autodesk Construction Cloud, Riverbend Logistics Center
Contract RLC-SC-018
Flagged: COI deficient
GL 5520-1187-04 renewal has no CG 20 37. Cost manager notified before review of payment application #05.
- Supplier
- Summit Steel Erectors
- Contract value
- $2,416,000.00
- Payment application
- #05, $96,540.00, in review
- COI status (custom)
- Non-compliant
- Deficiency (custom)
- CG 20 37 missing
Written by Pikorua Security Oct 16, 2026, 06:00 AM ET
- Setup time
- 40 minutes
- Connection
- APS OAuth 2.0 + Cost API + webhooks
- Fields synced
- 6 fields, 5 trigger events
- Included on
- Professional and Enterprise
Sync fields
What Pikorua Security reads from and writes to Autodesk Construction Cloud.
| Field | Direction | What happens |
|---|---|---|
| Hub companies | Autodesk Construction Cloud to Pikorua Security | Companies from your Forma hub (formerly the ACC account) become Pikorua Security vendors, matched on legal name and trade. |
| Projects | Autodesk Construction Cloud to Pikorua Security | Project names, addresses and owners, used to check that the owner and your entity are named as additional insureds. |
| Supplier contracts (Cost Management) | Autodesk Construction Cloud to Pikorua Security | Contract number, supplier, value and status decide which requirement template applies on each project. |
| Cost payment applications | Autodesk Construction Cloud to Pikorua Security | Read as soon as a supplier submits, through cost payment webhook events. Autodesk's API keeps payment applications read-only, so review and approval stay in Forma Build. |
| Contract custom attribute: COI status | Pikorua Security to Autodesk Construction Cloud | Compliant, Non-compliant or Expiring, written to a list attribute you create on contracts, visible and filterable in the contract log. |
| Contract custom attribute: deficiency | Pikorua Security to Autodesk Construction Cloud | The failed rules in plain words, such as "CG 20 37 missing" or "Auto limit $500,000 vs. $1,000,000 required", with a link to the verified packet. |
Trigger events
When the certificate changes, Autodesk Construction Cloud changes with it.
- Hold
Supplier submits a cost payment application while non-compliant
Then: Pikorua Security flags the contract within seconds of the webhook, emails the cost manager the deficiency, and records the payment application number against the hold.
- Hold
General liability or umbrella policy expires
Then: Contract COI status set to Non-compliant, and the supplier and its broker receive the renewal request with an upload link.
- Hold
Waiver of subrogation missing (CG 24 04 or WC 00 03 13)
Then: Non-compliant with the missing form named; the broker's checklist lists the exact endorsement the contract requires.
- Hold
New supplier contract created
Then: Pikorua Security opens a compliance request to the supplier using the project's requirement template, before mobilization.
- Release
Renewal verified
Then: Custom attributes return to Compliant and the deficiency text clears, so the next payment application is reviewed normally.
Setup
Live in 40 minutes.
5 steps, done by your Autodesk Construction Cloud administrator and a Pikorua Security Admin together. Nothing to install on your servers.
APS OAuth 2.0 + Cost API + webhooks- 1
Add the custom integration
A hub administrator adds Pikorua Security's Autodesk Platform Services client ID under Custom Integrations in Account Admin and selects the projects it may access.
- 2
Create two custom attributes
In Cost Management settings, add a COI status list attribute and a deficiency text attribute on contracts. Pikorua Security writes only to these two fields.
- 3
Authorize with 3-legged OAuth
A cost administrator signs in from Pikorua Security's Integrations screen, so every write is attributed to a named user in the project history.
- 4
Match suppliers
Pikorua Security lists hub companies and proposes vendor matches. Resolve the few that differ by DBA or LLC suffix.
- 5
Subscribe to events
Pikorua Security registers webhooks for contract and cost payment events, then runs a first pass showing every supplier that would be flagged today.
Autodesk Forma, formerly Autodesk Construction Cloud
In March 2026 Autodesk began moving Autodesk Construction Cloud into the Autodesk Forma brand. Autodesk Build is now Forma Build, Docs is now Forma Data Management, and accounts are now hubs. Autodesk kept URLs, logins and APIs the same through the rename, so the Pikorua Security connector works exactly as before. This page uses both names because your team will search for both.
Cost Management is where the money is. Supplier contracts, schedules of values and cost payment applications live there, and Cost Management's own compliance requirements workflow can require suppliers to attach documents such as certificates of insurance before they submit a contract. That workflow confirms a document is present. Pikorua Security confirms what the document says: limits, forms, edition dates and named additional insureds against your exhibit.
Why the connector flags instead of rejecting
Autodesk's Cost Management API exposes payment applications to outside applications as read-only. Pikorua Security respects that: it does not try to approve or reject a payment application. It flags the contract, alerts the reviewer and records the deficiency, and the cost manager makes the call inside Forma Build with the evidence in front of them.
For most general contractors that is the right split. The person reviewing the pay app sees a Non-compliant attribute and a one-line reason, such as an expired auto policy or a missing completed operations endorsement, and keeps it in review until the broker responds. If you need a hard stop at payment, place it in your accounting system through Pikorua Security's CMiC, Viewpoint Vista or Foundation connectors.
More construction management connectors
Teams that connect this usually connect these too.
FAQ
Autodesk Construction Cloud connector questions.
Pikorua Security is compliance software. It verifies certificates and endorsements against your contract requirements; it does not sell insurance or give legal advice.
Does the rename to Autodesk Forma change anything for the connector?
Can Pikorua Security reject a payment application in Forma Build?
Does it work on BIM 360 projects?
How is this different from Cost Management's compliance requirements?
14-day free production trial
Connect Autodesk Construction Cloud during your 14-day trial.
Upload your current certificates, authorize Autodesk Construction Cloud, and see which vendors would be on hold today before you switch a single rule on.