Nimbus

Connecting a Business Unit

Connecting a Business Unit gives Nimbus the credentials it needs to read automation data and act on failures. You do this once per Business Unit, either during onboarding or later from Settings → Tenants → Add tenant.

What you are creating #

Nimbus authenticates to SFMC with a server-to-server installed package — an OAuth client that belongs to the Business Unit. It never uses a person's login, so the connection keeps working when staff change.

1. Create the installed package in SFMC #

  1. In SFMC, switch to the Business Unit you want to connect.
  2. Open Setup (your name, top right → Setup).
  3. Go to Platform Tools → Apps → Installed Packages.
  4. Click New, give the package a name such as Nimbus Monitoring, and save.
  5. Add a component of type API Integration, and choose Server-to-Server.
  6. Grant the integration these scopes:

- Automations — Read, Write, Execute - Data Extensions — Read, Write - Journeys — Read - Email — Read, Write (used to host the CloudPage snippet) - Webhooks / Event Notification — Read, Write - SaaS / Provisioning — Read

  1. Save the component.

2. Copy the four values #

From the API Integration component, copy:

ValueLooks like
**Client ID**a long alphanumeric string
**Client Secret**a long alphanumeric string
**MID**the numeric Business Unit ID
**Authentication Base URI**`https://mcXXXXXX.auth.marketingcloudapis.com/`

The mcXXXXXX portion of the Base URI is your subdomain — Nimbus extracts it automatically when you paste the full URI.

3. Enter the credentials in Nimbus #

On the connection screen, fill in:

  • Business Unit name — a friendly label, e.g. Acme — Production.
  • MID
  • Subdomain (or paste the full Base URI)
  • Client ID
  • Client Secret

Click Verify & Connect. Nimbus immediately requests an OAuth token and checks the scopes. If the request fails — wrong secret, missing scope, wrong subdomain — Nimbus shows the error and saves nothing. Fix the issue and try again.

4. What happens on success #

When the credentials pass, Nimbus:

  1. Encrypts and stores the credentials.
  2. Creates the tenant record.
  3. Queues registration of the ENS webhook and subscription so SFMC starts pushing events.
  4. Begins deploying the CloudPage snippet.

The next step is Deploying the CloudPage Snippet, which unlocks per-step enrichment and reruns.

Updating or rotating credentials #

From Settings → Connection an admin or owner can update the stored credentials and change alert thresholds. You can also disable a tenant to pause all event processing without deleting it.