Outcome. Shortly after each marketing email send, an admin gets a Slack alert only if that send's bounce rate is well above the portal's recent historical average, so a bad list segment or a deliverability problem is caught within hours, not at the next monthly review.
Workflow map
Enrollment, branches and actions at a glance
reporting-alerts-025
flowchart TD
A[Marketing email send completes] --> B[Wait 3 hours]
B --> C[Custom code: fetch this send's stats and 30-day baseline]
C --> D{Recipient floor met and bounce rate above threshold?}
D -->|yes| E[Post Slack alert naming the email and rate]
D -->|no| F[Exit silently]
When to use it, when not to
- UseUse it on portals sending regular marketing email campaigns where deliverability matters, sender reputation, domain health.
- UseUse it to catch a send to a stale or purchased list segment, a broken personalization token causing bounces, or a sudden domain-level blocking event.
- SkipDo not use it for very low-volume sends, a handful of recipients, where one or two bounces look like a huge percentage spike without being a meaningful signal. Set a minimum recipient-count floor.
- SkipDo not treat this as deliverability monitoring on its own. Pair it with the sending domain's actual authentication status (SPF, DKIM, DMARC) checks, which this fiche does not cover.
The preview ends here. Six sections are in the library.
counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.4 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.3 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.5 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build, and the custom coded action ships as a ready-to-paste .js file.PDF, Markdown, JSON, code
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library,
149 EUR
or the reporting and alerts pack, 39 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.
