Skip to main content

Procore and Aconex

The shape an integration with Procore or Aconex would take. No live

integration ships in this run; this page documents the design so

the work is mechanical when scheduled.

Direction

Both directions are useful:

  • Inbound: Procore RFI -> Nebula obligation atom
  • Outbound: Nebula item transition -> Procore activity log

Auth

Procore: OAuth 2.0; Nebula stores the refresh token encrypted.

Aconex: Bearer token issued by the Aconex admin; stored encrypted.

Mapping

Each integration ships a mapping table from external entity types

to Nebula atom kinds. The mapping is per-org; the Procore project

selector picks which Procore project becomes which Nebula project.

Failure handling

Failed inbound events are retried via the same backoff as outbound

webhooks (30s, 2min, 10min, 1h, 6h). After 5 attempts they're

moved to a manual reconciliation queue.

Cross links

  • /docs/api/webhooks: outbound shape that mirrors this
  • /docs/integrations/outbound-webhooks: walkthrough