Skip to main content

Integration

Maintained by AEC Integrations

How Bluebeam Revu and Raken exchange data

2 data objects sync

These flows are asserted by AECi.

0 of 2 vendor-confirmed

Native

Raken → Bluebeam Revu

Built by Raken

Creating a Bluebeam Session on a Raken RFI pushes every PDF attachment on that RFI into a Bluebeam Studio Session and invites the RFI's assignees automatically. Stakeholders mark up the shared PDFs in Bluebeam; when the session is finalised from Raken, the marked-up files come back and attach to the RFI as new documents prefixed "Bluebeam". Sessions are named [Project Name] - [RFI Number]. The connection is per user — each person authenticates their own Bluebeam account so Studio permissions stay tied to individuals — and requires the Raken Performance Plan plus an active Bluebeam Core or Complete licence.

Syncs both ways

  • RFIs Unverified · AECi
  • Documents Unverified · AECi

Directory updates

Know when new tools and reviews land

AEC Integrations is live and still growing. Add your email for occasional updates as we expand the directory with new tools, integrations, and reviews.