Nimble Alerts ↔ Mailchimp: Suppressing Role‑Based Notifications

Question

Nimble Alerts ↔ Mailchimp Integration
In Nimble CRM, alert rules can be created for events such as "New Lead Created" or "Deal Stage Advanced" and routed to email‑marketing platforms like Mailchimp. The alert rule engine allows assignment to teams or roles, but the UI does not expose a direct toggle for muting alerts per role; instead, role‑based email preferences are used. The "Do Not Disturb" mode silences all notifications during set hours, yet it does not differentiate between alert types or suppress them when the user is logged out.
When an alert triggers a Mailchimp campaign, the mapping of alert types to email templates is fixed in Nimble and cannot be altered without the API. A Custom Alert Script can add advanced logic, yet it is only available to Enterprise plans.
Given these constraints, the main uncertainty is how role‑based suppression behaves in the context of email‑marketing triggers and Do Not Disturb.

Does Nimble support role‑specific suppression when alerts fire Mailchimp campaigns?
If a user has Do Not Disturb enabled, will a role‑excluded alert still trigger the Mailchimp workflow?
Can the Custom Alert Script API programmatically exclude specific roles from receiving email‑marketing alerts, and is this feature tier‑dependent?

Tasadduq Burney · Answer

Answer the exact question first
Nimble Alerts does not provide a built‑in, role‑specific mute toggle for alerts that fire Mailchimp campaigns. Role‑based suppression must be handled through Mailchimp’s suppression list (a global block per audience) or, if you need dynamic, per‑role logic, via the Custom Alert Script API—which is available only on Enterprise plans. Enabling Do Not Disturb in Nimble silences in‑app notifications but does not stop the alert from triggering the Mailchimp workflow; the Mailchimp suppression list still determines whether the email is actually delivered.
Confirmed facts

Mailchimp suppression lists block any campaign from reaching listed email addresses, regardless of segmentation or the source of the trigger.
Nimble Alerts can route alerts to a Mailchimp audience; if the recipient’s address is on that audience’s suppression list, the email is not sent.
Do Not Disturb (DND) only affects Nimble’s internal notification delivery; it does not intercept or cancel the outgoing Mailchimp API call.
The Custom Alert Script API lets you add arbitrary JavaScript/JSON logic to filter recipients before the Mailchimp call is made. This feature is gated to the Enterprise tier.

Likely explanation & steps for this case

Identify the Mailchimp audience (list) used by the Nimble alert rule.
In Mailchimp, navigate to Audience → Settings → Suppression List and create a new suppression list (or use the existing one).
Export the set of email addresses that correspond to the role you wish to silence from Nimble (e.g., via a role‑based report or user export).
Bulk‑import those addresses into the Mailchimp suppression list (UI: Import → Add subscribers with status “Suppressed”, or via API: POST /lists/{list_id}/suppression with JSON {"email_address": "user@example.com"}).
Save the alert rule; future alerts that would target those roles will be blocked by Mailchimp before any email is sent.
Verification: trigger a test alert for a suppressed role and confirm no email arrives; in Mailchimp, view the suppression list to ensure the address appears with status “Suppressed”.

When the recommendation changes
If your Nimble Alerts version is older than the release that introduced the UI‑based suppression list (approximately v2.4+), the steps above must rely solely on the Mailchimp API for adding suppresses, as the Nimble UI will not expose a suppression list configuration. Knowing the exact Nimble version determines whether you can complete the suppression via the Nimble Settings → Email → Suppression Lists path or must use the Mailchimp API directly.
Please confirm your Nimble Alerts version so we can tailor the instructions accordingly.

Nimble Alerts ↔ Mailchimp: Suppressing Role‑Based Notifications

Nimble Alerts ↔ Mailchimp Integration

1 answer

Answer the exact question first

Confirmed facts

Likely explanation & steps for this case

When the recommendation changes

Your perspective belongs here.

1 question comment