Skip to content
New: a free website for your business, live in 48 to 72 hoursWorkflow automation on n8n and Claude, built for your businessFixed price, agreed before we start · Live in 5 to 10 business days30-day money-back guarantee on every planProfessional firms · Agencies · E-commerceYou own every workflow, in your own n8nClaude API: your data is not used for trainingHuman approval on every sensitive stepFree automation audit, no obligation
PURIST
30 days
Money-back window
14 h/wk
Modeled time saved
99.97%
Uptime SLA
< 7 days
Deploy time
PURIST AI
Claude Opus 4.7 · n8n v1.71 · <80ms
What type of business are you running? I'll show you exactly which processes we'd automate first and your estimated ROI.
Powered by n8n + Claude Opus 4.7 Get my free automation plan →
Security
Beginner

Permissions (API)

The specific actions an API key or OAuth token is authorised to perform read-only, write, delete, admin. Best practice: grant automation credentials only the minimum permissions required. An invoice automation should never have permission to delete contacts.

Expert insight

API permissions granted more broadly than a workflow actually needs (full read-write access when the workflow only ever reads data) increase the damage a leaked credential or a workflow bug can cause, scoping API permissions to the minimum the workflow genuinely requires limits the blast radius of anything going wrong.

In a real workflow

A reporting workflow uses a read-only API key, so it cannot modify data even if misused.

Common mistakes

  • Using admin permissions for everything.
  • No review when people leave.

Complexity level

Beginner

Anyone can understand this no technical background needed.

Quick facts

Category Security
Level
Beginner

Browse the full glossary

← All 325 terms

See it in action

Want Permissions (API) built into your automation?

Book a free audit and we'll show you exactly how this applies to your business.

Get my free automation plan →