The useful starting point: Hotjar

Hotjar gives product and research teams a structured way to manage recordings, heatmaps, surveys, feedback, and users. For Beam, the starting point is a narrow, reviewable handoff rather than a promise to manage the whole process. For Hotjar, treat recordings, surveys, and heatmap signals as evidence and keep the product owner responsible for interpretation

How the workflow should behave

Use the product record as context, not as permission. Establish how the recording enters review, what information Beam receives, and where the result is stored. Stop when the connector or account cannot support the documented rule

Examples for review

• A sensible pilot begins when a recording record is created, updated, or ready for review. Confirm the source record, required fields, and human owner before asking Beam to prepare any downstream action.

• Once the pilot is understood, test a second path for recording exceptions; keep the write-back operation narrowly scoped until it is verified.

Operational value

• A concrete first use case for the product's documented resources.

• Better visibility into the fields and permissions a workflow actually needs.

• A rollout that preserves human judgment where the source does not define the answer.

Before you build

Check the connector's available read, write, search, notification, and event operations for your Beam workspace. Confirm the vendor authentication method, required scopes, plan limits, and any approval requirements. Treat the two workflow patterns above as designs to validate, not promises of universal coverage.