# Find hardcoded API keys in a Make.com scenario

**Use case:** 

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.

## Input

```json
{
  "blueprintJson": {
    "name": "Order sync - HTTP to CRM",
    "flow": [
      {
        "id": 1,
        "module": "http:ActionSendData",
        "version": 3,
        "parameters": {
          "handleErrors": false
        },
        "mapper": {
          "url": "https://api.example.com/v1/orders",
          "method": "get",
          "headers": [
            {
              "name": "Authorization",
              "value": "Bearer sk-proj-EXAMPLEONLYnotarealkey0123456789abcd"
            }
          ]
        },
        "metadata": {
          "designer": {
            "x": 0,
            "y": 0
          }
        }
      },
      {
        "id": 2,
        "module": "http:ActionSendData",
        "version": 3,
        "parameters": {
          "handleErrors": false
        },
        "mapper": {
          "url": "https://hooks.example.com/notify",
          "method": "post",
          "qs": [
            {
              "name": "token",
              "value": "glpat-EXAMPLEONLYnotarealtoken1"
            }
          ]
        },
        "metadata": {
          "designer": {
            "x": 300,
            "y": 0
          }
        }
      },
      {
        "id": 3,
        "module": "util:SetVariable2",
        "version": 1,
        "parameters": {},
        "mapper": {
          "name": "apiKey",
          "scope": "roundtrip",
          "value": "{{var.crmToken}}"
        },
        "metadata": {
          "designer": {
            "x": 600,
            "y": 0
          }
        }
      }
    ],
    "metadata": {
      "version": 1,
      "scenario": {},
      "designer": {
        "orphans": []
      }
    }
  },
  "makeZone": "eu1",
  "organizationIds": [],
  "teamIds": [],
  "scenarioIds": [],
  "include": [
    "scenarios",
    "connections",
    "customVariables",
    "dataStores",
    "dataStructures",
    "hooks",
    "keys",
    "scenarioFolders"
  ],
  "backupStoreName": "make-scenario-backup",
  "seedVersionHistory": false,
  "maxVersionsPerScenario": 10,
  "gitBranch": "main",
  "gitPath": "make/",
  "gitRedaction": "standard"
}
```

## Output

```json
{
  "runAt": {
    "label": "Backed up",
    "format": "string"
  },
  "resourceType": {
    "label": "Type",
    "format": "string"
  },
  "resourceId": {
    "label": "ID",
    "format": "string"
  },
  "name": {
    "label": "Name",
    "format": "string"
  },
  "changeType": {
    "label": "Change",
    "format": "string"
  },
  "diffSummary": {
    "label": "What changed",
    "format": "string"
  },
  "isActive": {
    "label": "Active",
    "format": "boolean"
  },
  "scheduleType": {
    "label": "Schedule",
    "format": "string"
  },
  "moduleCount": {
    "label": "Modules",
    "format": "number"
  },
  "modulesAdded": {
    "label": "Modules added",
    "format": "number"
  },
  "modulesRemoved": {
    "label": "Modules removed",
    "format": "number"
  },
  "modulesModified": {
    "label": "Modules modified",
    "format": "number"
  },
  "connectionCount": {
    "label": "Connections",
    "format": "number"
  },
  "teamName": {
    "label": "Team",
    "format": "string"
  },
  "lastEdit": {
    "label": "Last edited in Make",
    "format": "string"
  },
  "secretsFound": {
    "label": "Possible secrets",
    "format": "number"
  },
  "snapshotUrl": {
    "label": "Snapshot",
    "format": "string"
  }
}
```

## About this Actor

This example demonstrates how to use [Make.com Scenario Backup & GitOps - Blueprints](https://apify.com/mediocre_interest/make-scenario-backup.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/mediocre_interest/make-scenario-backup.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/mediocre_interest/make-scenario-backup.md

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).