Skip to content
Merulan

Nylas mailbox setup

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

Connecting Nylas mailbox redirects the operator to the provider and returns with a grant. Merulan support holds the credential. The catalog no longer offers Nylas mailbox for a new connection. An earlier connection keeps running, and the material below describes it.

Prerequisites

Nylas mailbox refuses the connection until every item holds.

  • A Merulan support request, because the catalog no longer offers a new Nylas mailbox connection.
  • An existing Nylas grant for a mailbox already connected this way.

Credentials

Nylas mailbox stores the credential under the operated custody the registry declares, so Merulan never shows the secret again once the connection is saved.

  • No secret is typed into Merulan. The Nylas grant returns tokens that Merulan seals, and the grant identifier lands on the connection row.

Scopes

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

  • email.read_only
  • email.send
  • calendar.read_only

The Nylas mailbox reads and sends mail and reads calendars. The calendar half is read-only.

Verification

Support-operated connection governs the Nylas mailbox connection. Nylas admits its own application with the underlying mail provider, and the Merulan catalog keeps the Nylas mailbox card hidden while existing connections keep working.

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