runmend
Back to profiles

Creator Stack

Make.com
Excellent

15 automations·Digital Courses·Audited Mar 26, 2026

4070
91/100
Excellent

Automation health

Everything is running cleanly.

3 low-severity findings — nothing urgent.

DetectorsZombie· 1SilentError rateError spike· 1ConsecutiveAuth health

Issues grouped by detector

3 open · across 3 automations

Zombie automations

· 1 affected

Active but never executed. Trigger is likely misconfigured, or the scenario is no longer needed.

New Student → Welcome Email (Old Template)

This scenario sends a welcome email using your old branding (pre-rebrand 6 months ago). Your new enrollment flow already sends a branded welcome via ConvertKit. 100% of new students get two welcome emails — one old, one new.

RecommendationTurn off this legacy scenario. Your ConvertKit sequence already handles the welcome email with your current branding. Having two welcome emails confuses students.

Error spike

· 1 affected

Today's error rate is more than 2× the 7-day baseline. Something recently broke.

New Enrollment → Drip Content Schedule

Your Teachable API usage is at 82% of the hourly rate limit. During your last course launch (200+ enrollments in 1 hour), this scenario hit the limit and 34 students didn't get their Day 1 content on time. Next launch is in 2 weeks.

RecommendationAdd a Sleep module with a 2-second delay between API calls in this scenario, or use Make.com's built-in rate limiting to spread enrollments over a longer window during launches.

Other findings

· 1 affected
Payment → Grant Circle Community Access

Students are being added to your Circle community by both this scenario and your Teachable-Circle native integration. No harm done — Circle deduplicates — but you're using unnecessary Make.com operations.

RecommendationDisable this scenario since the native Teachable-Circle integration handles it. This will save ~45 operations/month.

AI analysis— Claude's independent take on this profile

AI Diagnostic

Excellent