Plugs into the systems you already use.
Procore, Autodesk Construction Cloud, OneDrive/SharePoint, Google Drive, and Dropbox are where your project data already lives. Forward connects to all five via official OAuth and makes everything in them answerable by text — no replacement, no migration, no per-seat license to add. Scheduling and accounting integrations ship as customers ask.
Procore
- Drawings (current revisions, history, sheet metadata)
- RFIs (full text, response, attachments, ball in court, status)
- Submittals (status, ball in court, approval dates)
- Specifications
- Daily logs (manpower, weather, notes)
- Observations
- Project rosters (for field-user enrollment)
- Draft RFIs (queued for PM approval — never auto-posted)
- Draft observations (same — PM approves before posting)
Official Procore OAuth. A Procore admin grants Forward access on a per-project basis. We never store your Procore credentials.
Revoke us in Procore (Account → Apps & Integrations → Forward) and we lose access immediately. Your data we have indexed is then deleted within 30 days.
Autodesk Construction Cloud
- Sheets (current published versions + revision history)
- Project files
- Issues
- RFIs (in ACC RFI tools)
- Forms
- Models — federated BIM model properties (room dimensions, equipment IDs, finishes)
- (Read-only today; draft writes on the roadmap.)
Official Autodesk Forge OAuth. Granted by an Autodesk account admin per hub and per project. Supports current Autodesk Build / ACC + legacy BIM 360.
Revoke at Autodesk Account Admin → Custom Integrations. Our access ends immediately.
OneDrive + SharePoint
- Spec PDFs (project manuals, division-level files)
- Finish schedules + FF&E plans
- As-builts and redline overlays
- Equipment cut sheets, submittal data archives
- Field photos archived from a project folder
- Any text-indexable file (Word, Excel, PDF)
- (Read-only. No Files.Write scope is ever requested.)
Microsoft Graph OAuth via /common authority — works with personal Microsoft accounts AND Entra ID (Azure AD) tenants. Delegated scopes: Files.Read.All, Sites.Read.All, offline_access, User.Read.
Revoke at Microsoft account → Privacy → Apps. Forward loses access on the next API call.
Google Drive
- Folder of project documents (whole Drive or a scoped folder)
- Shared Drives, when your IT has them
- Spec PDFs, finish schedules, as-builts, cut sheets
- Photos archived from the field
- Google Docs, Sheets, Slides — exported as PDF on read
- (Read-only. Only drive.readonly scope is requested.)
Google OAuth 2.0 via Cloud Console. Scopes: drive.readonly + userinfo.email. Tokens are stored encrypted per tenant. Supports Workspace and personal Google accounts.
Revoke at myaccount.google.com → Security → Third-party access. Forward loses access on next API call.
Dropbox
- Project folders (whole Dropbox or a scoped sub-folder)
- Team Folders, for business accounts
- Spec PDFs, finish schedules, redlines
- Field photos archived to a Dropbox folder
- Any text-indexable file (Word, Excel, PDF)
- (Read-only. Only files.metadata.read + files.content.read scopes are requested.)
Dropbox OAuth 2.0 with token_access_type=offline. Scopes: files.metadata.read, files.content.read, account_info.read. Tokens stored encrypted per tenant.
Revoke at dropbox.com/account/connected_apps. Forward loses access immediately.