Skip to main content
Configview reads your Make account (make.com, formerly Integromat, the automation platform) through the Make API v2 (https://<zone>/api/v2, for example https://eu1.make.com/api/v2), using an API token created in your Make profile. Configview sends only GET requests. It never creates, changes, runs or deletes anything in Make. You will end up with 2 required secrets (MAKE_API_TOKEN, MAKE_ZONE) and 1 optional secret (MAKE_ORGANIZATION_ID) in Configview when setup is complete.
Scope of this integration today. Configview answers “who can build automations in Make, what are they connected to, and which automations are running”: organizations and their security settings, teams, members with their organization and team roles, every scenario (owner, active or not, schedule type, last edit, apps used, operation and error counts), the third-party connections (app, name, expiry, which scenarios use them), webhooks and mailhooks (receiving host only), and on Enterprise plans the audit log and operations per scenario. It does not read scenario blueprints, connection credentials or data, execution logs or the data your scenarios move.

What you need

  • A Make account with the Admin or Owner role in the organization (an Admin sees every team; a plain member sees only the teams they joined)
  • Your zone: the host in your browser address bar when you are signed in to Make, for example eu1.make.com, eu2.make.com, us1.make.com or us2.make.com
  • For the audit log and usage tables: an Enterprise plan (audit logs need Admin or Owner, usage needs the Owner role)

Step 1: Open the Make page in Configview

Open Configview in a second browser tab and leave it open: https://{companyname}.configview.com/admin/integrations/make

Step 2: Create a read-only API token

Make tokens belong to a user and carry the scopes you tick. Use a dedicated member (for example configview@yourcompany.com) with the Admin role, so the token never depends on one person’s account.
  1. Sign in to Make as that member and open your profile (bottom left) > API access
  2. Click Add token, give it a label such as Configview
  3. Tick only these read scopes:
    • organizations:read
    • teams:read
    • user:read
    • scenarios:read
    • connections:read
    • hooks:read
    • Enterprise only: audit-logs:read and analytics:read
  4. Do not tick any :write or scenarios:run scope. Configview never needs them.
  5. Click Save and copy the token. Make shows it once.
  6. In the Configview tab paste it into MAKE_API_TOKEN and your zone host (for example eu1.make.com, without https://) into MAKE_ZONE, then save.
  7. Optional: to cover only one organization, paste its numeric id into MAKE_ORGANIZATION_ID. Leave it empty to cover every organization the member belongs to in this zone.
A token works in one zone. If you have organizations in several zones, add them as separate connections.

Step 3: Connect and verify

  1. Click Connect. Configview creates its tables and schedules every collector at your default run time:
  1. Click Verify now. The health check reads the secrets, checks the zone, then lists your organizations and the teams of the first one.
If a check fails:
  • 401. The token is wrong, revoked, missing a scope, or was issued in a different zone than MAKE_ZONE.
  • 402, 403 or 404. The plan or the member’s role cannot read that area. The audit log and usage tables skip cleanly on a plan without them; the rest are not affected.

Data Tables

Each table has a run_at column and keeps only the newest run, except the audit log, which is a permanent archive.

Things worth knowing

Connections and who they act as. The API returns the app a connection is for (for example slack) and the label your team gave it. It does not say which person authorized it, so Configview shows the app, the name, the label, the expiry and the scenarios using it. A connection no scenario or webhook uses stands out as unused access. Roles are ids. Members and teams carry a role id. The Roles table maps each id to its name; join them to read “Admin” or “Team Member”. Large accounts take time. Team roles need one call per member and scenarios, connections and webhooks one call per team. Configview paces itself at 40 requests per minute, so an account with hundreds of members takes several minutes to finish. Owners and tools. Scenarios of type tool (sub-scenarios) are left out of the Scenarios table.

Rate limits

Make limits the API per organization plan: Core 60, Pro 120, Teams 240 and Enterprise 1,000 requests per minute, with HTTP 429 beyond. Configview paces itself at 40 requests per minute and waits as long as Make asks when it is told to slow down.

What isn’t collected

  • Scenario blueprints, module settings, descriptions and custom properties
  • Connection credentials, connection data and the free-text metadata of a connection
  • Webhook URL paths (only the receiving host) and webhook request logs
  • Execution logs and the data your scenarios process, data store records, variables
  • API token values (the API lists only the calling member’s own tokens, so Configview does not read them)
  • The detail body of an audit log entry