Go to example tasks
Find hardcoded API keys in a Make.com scenario
Scan a Make.com blueprint for credentials typed into modules - API keys and bearer tokens in HTTP headers or module fields instead of a connection or a custom variable - plus HTTP modules with TLS verification switched off. Every hit is masked in the results, with the exact field to fix and how.
Make.com Scenario Auditor - Linter & Cost Reviewmediocre_interest/make-scenario-auditor
Severity
Ops wasted / month
Savings / month (USD)
Cost confidence
+13 fieldsTextNumberBooleanListObject
Input
Blueprint JSON
Rule set:security
Minimum severity:low
Output fields
Severity
Ops wasted / month
Savings / month (USD)
Cost confidence
Rule
Finding
Category
Scenario
Module
Module id
Message
Remediation
Evidence
Field
Runs per bundle
How it was priced
Docs
Sign up on Apify01
Create your Apify account to access the Make.com Scenario Auditor - Linter & Cost Review.
Start the run02
The Actor will start running based on the input automatically.
Receive the output03
Monitor the progress in real-time. You will be notified as soon as your dataset is complete and ready for review.
Integrate into your workflow04
The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow.
