Find hardcoded API keys in a Make.com scenario

Created by

Mediocre_Interest

Actor

Make.com Scenario Backup & GitOps - Blueprints

Scan a Make.com scenario blueprint for credentials typed straight into a module - bearer tokens in headers, keys in query strings - before you share the blueprint or commit it. The sample on this page holds two, in two different places, and a third value that reads from a Make custom variable, which is safe and is deliberately not counted.

Try for free

Make.com Scenario Backup & GitOps - Blueprintsmediocre_interest/make-scenario-backup

Backed up

Type

Name

+13 fields

Input

Scenario blueprint:{3 fields}

Output fields

Backed up

Type

Name

Change

What changed

Active

Schedule

Modules

Modules added

Modules removed

Modules modified

Connections

Team

Last edited in Make

Possible secrets

Snapshot

How it works

Sign up on Apify or log in

The Make.com Scenario Backup & GitOps - Blueprints 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 Backup & GitOps - Blueprints Actor will start running based on the input automatically. You can also change all the input fields, like scenario blueprint, 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 backed up, type, ID, 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.