Go to example tasks
Find hardcoded API keys in a Make.com scenario
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.
Make.com Scenario Backup & GitOps - Blueprintsmediocre_interest/make-scenario-backup
Backed up
Type
ID
Name
+13 fieldsTextNumberBooleanListObject
Input
Scenario blueprint
Output fields
Backed up
Type
ID
Name
Change
What changed
Active
Schedule
Modules
Modules added
Modules removed
Modules modified
Connections
Team
Last edited in Make
Possible secrets
Snapshot
Sign up on Apify01
Create your Apify account to access the Make.com Scenario Backup & GitOps - Blueprints.
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.
