bluebeam_skill

Overview

This skill integrates with Bluebeam to manage Projects, Sessions, Documents, Markups, Users and related entities used in AEC workflows. It exposes common operations like listing projects and sessions, creating projects/sessions, retrieving markups, and managing session files. Use it when you need programmatic access to Bluebeam data and workflows via the Membrane CLI proxy.

How this skill works

The skill uses Membrane as the runtime and authentication layer so you never handle raw API keys. Membrane provides pre-built actions (list-projects, get-session, create-session, get-session-markups, create-file-snapshot, etc.) and an HTTP proxy for custom endpoints. Invoke actions or proxy requests through the Membrane CLI; Membrane injects auth headers, handles pagination and refresh tokens automatically.

When to use it

• Automate retrieval of Bluebeam Studio Projects or Sessions for reporting.
• Create or update Studio Sessions and Project folders as part of deployment scripts.
• Fetch session files and markups for audit, QA, or downstream processing.
• Generate combined PDF snapshots of files with markups for distribution.
• Invite or add users to sessions programmatically during project onboarding.

Best practices

• Always use Membrane’s pre-built actions before calling raw endpoints — they handle pagination and edge cases.
• Create a persistent Membrane connection instead of storing credentials locally; Membrane manages token refresh.
• Run membrane action list --intent=QUERY to discover available actions and input schemas before building calls.
• Use membrane request only when pre-built actions don’t cover a use case; prefer --json and explicit headers for predictable behavior.
• Test in a non-production Bluebeam tenant or sandbox before automating destructive actions like delete-session or delete-project.

Example use cases

• List all Studio Projects and export metadata to an asset management system.
• Automate session creation and invite users when kicking off a new construction review cycle.
• Retrieve session markups and attach them to issue trackers or punchlist workflows.
• Create file snapshots that merge markups into distributable PDFs for permitting or client sign-off.
• Remove or archive old projects and session files as part of a cleanup job.