Skip to content
Merulan

Affinity meeting notes setup

What an operator supplies to connect the Affinity meeting notes Source, and the verification the provider requires.

Connecting Affinity meeting notes accepts a provider API key the operator pastes once. Merulan holds the credential directly. The catalog no longer offers Affinity meeting notes for a new connection. An earlier connection keeps running, and the material below describes it. Meeting notes are now a Collection of the Affinity Source.

Prerequisites

Affinity meeting notes refuses the connection until every item holds.

  • An Affinity account on a plan that issues API keys.
  • Affinity meeting notes enabled for the users whose notes a Pipeline reads.

Credentials

Affinity meeting notes stores the credential under the direct custody the registry declares, so Merulan never shows the secret again once the connection is saved.

  • One Affinity API key, pasted once and sealed on save.

Scopes

Affinity meeting notes carries no scope list in Merulan: the Affinity key itself holds the requested scopes for this Source.

An Affinity key carries no scope list. Reach is the issuing user, so narrow the user rather than the key.

Verification

Workspace-issued credential governs the Affinity meeting notes connection. Affinity issues the key inside the customer account, so no application review stands between the key and production data.

  • Connect and map a Source runs the connect ceremony and binds collections once the credential is in hand.
  • Integrations lists every Source that carries a setup page, with its ceremony and verification posture.