AppControler
Start scan

Automate AppControler with n8n, Zapier, or REST

Works with n8n, Zapier, scriptsAuth via MCP API key~8 min

What the API gives you

The same MCP API key that powers Cursor also works as a plain REST key. Hit /api/v1 endpoints from n8n, Zapier, Make, cron jobs, or scripts to automate AI-governance reports:

# High-risk AI apps
curl -s "https://appcontroler.com/api/v1/apps?ai_only=true&risk_level=HIGH" \
  -H "Authorization: Bearer acp_YOUR_KEY"

# Who uses ChatGPT
curl -s "https://appcontroler.com/api/v1/apps/users?app_name=ChatGPT" \
  -H "Authorization: Bearer acp_YOUR_KEY"

# Renewals in the next 60 days
curl -s "https://appcontroler.com/api/v1/renewals?within_days=60" \
  -H "Authorization: Bearer acp_YOUR_KEY"

# Block an app
curl -s -X PATCH "https://appcontroler.com/api/v1/apps" \
  -H "Authorization: Bearer acp_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"app_name":"Perplexity","policy":"Blocked"}'

n8n: schedule a renewals report (step by step)

  1. Create an MCP API key

    AppControler → Integrations → MCP / API keys → Create MCP key. Copy the acp_… key (shown once).

  2. Add the HTTP Request node

    In n8n, add an HTTP Request node. Method GET, URL https://appcontroler.com/api/v1/renewals?within_days=30.

  3. Send the Authorization header

    Under Headers, add Authorization = Bearer acp_YOUR_KEY — or store it as Generic Header Auth credentials so the key sits in n8n's credential vault instead of the workflow.

    Header name is exactly Authorization; value starts with Bearer followed by a space.

  4. Act on the response

    The response is JSON. Chain it into a Slack node, an email node, or an IF node — e.g. post to #it-ops only when the renewals list is not empty.

  5. Schedule it

    Add a Schedule Trigger (daily or weekly) so the report runs without anyone opening n8n.

Workflow ideas

TriggerCallAction
Cron dailyGET /api/v1/renewals?within_days=14Post to #it-ops if any act-by is close
Cron weeklyGET /api/v1/apps?ai_only=true&risk_level=HIGHEmail a founder digest of risky AI apps
Form submissionPATCH /api/v1/appsApprove or block an app from an internal request form
CronGET /api/v1/summaryDashboard metrics for leadership

Optional: n8n AI agent via the MCP node

n8n's MCP Client Tool node can point an AI Agent at AppControler directly. Configure it with:

Endpoint: https://appcontroler.com/api/mcp
Transport: HTTP (Streamable HTTP)
Authentication: Generic Header Auth
  Name:  Authorization
  Value: Bearer acp_YOUR_KEY

The agent can then call list_ai_apps, get_policy_summary, list_upcoming_act_bys, and friends on its own — e.g. “summarize our AI governance posture and email it to me.”

FAQ

MCP node or HTTP Request node in n8n?

Use the MCP Client Tool node when you want an AI agent to pick tools by itself inside an n8n Agent. Use plain HTTP Request nodes for deterministic reports and schedules — they are simpler and cheaper to run.

Which endpoint should I call?

Use /api/v1/* REST endpoints (apps, summary, renewals) for straightforward JSON responses. Use /api/mcp only for MCP clients speaking JSON-RPC.

Can Zapier or Make use the same key?

Yes. Any tool that can send an HTTP request with a custom Authorization header works — Webhooks by Zapier, Make HTTP module, Google Apps Script, cron + curl.

How often should I rotate keys?

Rotate when a team member leaves or a key may have leaked: revoke it in Integrations and create a new one. Only a hash is stored, so leaked keys cannot be read back from AppControler.

See every AI tool connected to your workspace

Free scan shows the apps employees authorized with company sign-in — before you connect them to AI assistants.

Start free AI scan

More setup guides