myapi

n8n community node for the MyApi platform — services proxy, skills, automations, notifications, workspaces, vault instructions. Usable as an AI Agent tool.

Package Information

Released: 3 mo ago
Downloads: 0 weekly / 0 monthly
Latest Version: 0.1.1

Available Nodes

Documentation generating…

MyApi icon
MyApi
Interact with the MyApi platform: call any connected service (Gmail, Drive, GitHub, Slack, 80+ toolkits), manage skills, automations, notifications, workspaces, and vault instructions.

Documentation

n8n-nodes-myapi

n8n community node for the MyApi platform. One node covers the whole platform surface — and it doubles as an AI Agent tool, so LLM agents inside n8n can drive MyApi autonomously.

What it can do

Resource Operations
Service List connected services, get one, list its methods, execute any action on any connected service (Gmail, Google Drive/Calendar, GitHub, Slack, Notion, and 80+ Composio-backed toolkits) via /services/:name/execute — named method or raw provider endpoint proxy
Skill List, get, get markdown content, create
Automation List, get, create, update, delete, run now, list runs (/triggers engine)
Notification List, unread count, mark read, mark all read, delete
Workspace List, get, create, list members
Vault Instruction Get stored per-service usage instructions
Custom API Call Any HTTP method against any /api/v1/* endpoint — full platform coverage for everything not modeled above (dashboard, audit, devices, email, billing, orgs, export/import, …)

Installation

n8n UI (recommended)

Settings → Community Nodes → Install → enter n8n-nodes-myapi.

Manual / self-hosted

cd ~/.n8n/nodes
npm install n8n-nodes-myapi

Restart n8n.

Credentials

Create a MyApi API credential:

  • Base URL — https://www.myapiai.com (or your self-hosted instance)
  • API Token — create in Dashboard → Access Tokens. Use a scoped token with only the scopes your workflow needs (e.g. services:gmail:read); a personal token grants full access.
  • Workspace ID — optional, for multi-tenant setups (sent as X-Workspace-ID)

The credential test calls GET /api/v1/services.

Using as an AI Agent tool

The node declares usableAsTool: true. To let AI Agent nodes use community nodes as tools, set on your n8n instance:

N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true

Then in an AI Agent node, add MyApi under Tools. Typical agent patterns:

  • "Check my unread notifications and summarize them" → Notification → Get Many
  • "Send an email via Gmail" → Service → Execute Action (gmail, method GMAIL_SEND_EMAIL)
  • "Run my morning-digest automation" → Automation → Run
  • Anything else → Custom API Call (the agent can hit any /api/v1 endpoint the token's scopes allow)

Tip: expose parameters to the model with $fromAI() expressions, e.g. set Service Name to {{ $fromAI('service') }} so the agent picks the service itself.

Scopes & security

  • Every call is authenticated with your token and audited server-side by MyApi.
  • Scoped tokens are enforced per service and per read/write level; a 403 from the node means the token lacks the required scope, not an n8n problem.
  • Write actions on services require services:write or services:{name}:write.

Development

npm install
npm run build      # tsc + icon copy → dist/
node scripts/smoke.js   # offline routing smoke test

Link into a local n8n for live testing:

npm run build && npm link
cd ~/.n8n/nodes && npm link n8n-nodes-myapi

License

MIT

Discussion