n8n-nodes-directoryz

n8n-nodes-directoryz

Connect Directoryz to n8n workflows using your own account. This package exposes 4 named operations through the product's authenticated API, with form fields for required inputs and optional fields you choose explicitly.

Installation

For self-hosted n8n, open Settings → Community Nodes → Install and enter n8n-nodes-directoryz. On n8n Cloud, installation depends on n8n's community-node verification; npm publication alone does not make a node verified.

Use n8n 2.40.7 or newer, with OAuth dynamic client registration support. Older installations should upgrade before using this credential.

Authentication

• Add the Directoryz node and create a Directoryz OAuth2 API credential.
• Click Connect my account. n8n discovers the product authorization server and registers its own callback automatically.
• Sign in to your Directoryz account, check the account and permissions on the consent screen, and approve the connection.
• Save the credential and select an operation.

No API key, client secret, browser cookie, or access token belongs in a workflow field. n8n stores the OAuth credential and refreshes tokens. Your account roles, ownership checks, available integrations, plan limits and credits still apply. You can revoke the connection in the product's connected-app settings. This node contacts only https://mcp.directoryz.app/mcp; the n8n OAuth flow contacts the product's discovered authorization server.

Operations

Operation	Access	Purpose
Get Directory	Read	Read an owned directory without publishing it.
Get Profile	Read	Read your connected workspace profile.
List Directories	Read	List directories in your selected Directoryz workspace.
List Listings	Read	Read listings within an owned directory.

Example workflow

Import the included example, select your credential, and execute the manual trigger. It runs Get Profile once and outputs the account response. Replace the trigger with a schedule to build a recurring report, then connect a filter, spreadsheet or notification node.

For operations that return IDs, map the returned ID into the required field of a second Directoryz node. Returned arrays stay inside the response object; use n8n's Split Out node when you need one item per record. Pagination fields are exposed only where the product supports them; advance the cursor/page explicitly rather than assuming all records were fetched.

Writes and account limits

Write operations require Confirm Write Operation. Review the inputs before enabling it: every workflow execution may repeat the action, create a draft, change account data, or consume product credits depending on the selected operation. The node does not retry write operations automatically. Use read-only operations for monitoring and deduplicate scheduled workflows that create data. Product authorization remains enforced by the server.

Error handling

• Reconnect OAuth after an authorization failure or revoked grant.
• Check account permissions and plan limits for forbidden or rate-limited responses.
• Invalid inputs stop the item before sending a request. Product-specific validation remains authoritative.
• On Error → Continue returns an error item linked to the original input. Failed MCP tool results are never returned as successful data.
• No passwords, environment variables, or customer data are bundled. No external runtime dependencies are installed by this package.

Development

npm ci --ignore-scripts
npm run lint
npm test

Releases are built and tested in GitHub Actions, then published to npm with provenance. Public snapshots use GitHub Actions bot attribution.

Links

• Website
• Privacy policy
• Source and issues
• n8n community-node installation

MIT licensed. This community integration is not an n8n core node.