Find hardcoded API keys in a Make.com scenario

Created by

Mediocre_Interest

Actor

Make.com Scenario Auditor - Linter & Cost Review

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.

Try for free

Make.com Scenario Auditor - Linter & Cost Reviewmediocre_interest/make-scenario-auditor

Severity

Ops wasted / month

Savings / month (USD)

Cost confidence

+13 fields

Input

Blueprint JSON:{3 fields}

Rule set:security

Minimum severity:low

Output fields

Severity

Ops wasted / month

Savings / month (USD)

Cost confidence

Rule

Finding

How it works

Sign up on Apify or log in

The Make.com Scenario Auditor - Linter & Cost Review Actor is ready to run with the inputs already set for "Find hardcoded API keys in a Make.com scenario". Sign up or log in and you'll land in Apify Console with a copy of this exact task.

Start the "Find hardcoded API keys in a Make.com scenario" task

The Make.com Scenario Auditor - Linter & Cost Review Actor will start running based on the input automatically. You can also change all the input fields, like blueprint json, rule set, and more, to match your specific use case.

Receive the "Find hardcoded API keys in a Make.com scenario" output

Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as severity, ops wasted / month, savings / month (usd), and more.

Integrate into your workflow

The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also run the "Find hardcoded API keys in a Make.com scenario" task via API.