Skip to content
Merulan

Slack setup

What an operator supplies to connect the Slack Source, and the verification the provider requires.

Connecting Slack runs an OAuth grant in the operator browser. Nango holds the credential, and Merulan holds a handle to it. An operator who holds the material below connects in one pass.

Prerequisites

Slack refuses the connection until every item holds.

  • A Slack workspace, and a member who may approve a connected application.
  • Membership in every channel a Pipeline reads, because Slack returns nothing from a channel the application never joined.

Credentials

Slack stores the credential under the brokered custody the registry declares, so Merulan never shows the secret again once the connection is saved.

  • No secret is typed into Merulan. The Connect session returns a connection handle, and Merulan stores the handle rather than the token.

Scopes

Slack requests the scopes the registry declares, and a grant missing one of them fails the first collection read.

  • channels:history
  • channels:read
  • chat:write
  • users:read

Reading a Pipeline uses the history and channel scopes. The write scope covers messages an operation posts back.

Verification

Broker-registered application governs the Slack connection. Slack admits the broker-registered application, and a Slack workspace owner may restrict or remove it at any time.

  • 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.