n8n node

The Dakoty community node for n8n is the npm package n8n-nodes-dakoty (open source, MIT, github.com/dakoty/dakoty-n8n-nodes). It contains two nodes and one credential, all built on the Developer API v1. Nothing in the package is a separate API: each operation calls an endpoint you can also call from your own code, so the API reference describes what the node sends and receives.

For the step-by-step setup in n8n and in the Dakoty settings, see the Slovak help article How to connect Dakoty with n8n.

Installing the npm package

Self-hosted n8n: Settings → Community nodes → Install → n8n-nodes-dakoty. n8n Cloud shows the node after n8n has verified the package. Until then, n8n’s HTTP Request node with a Header Auth credential reaches the same endpoints.

The Dakoty API credential

The Dakoty API credential asks for an API key that starts with dk_live_. n8n sends it as Authorization: Bearer <key> and tests it with GET /me; a wrong or revoked key returns 401 and n8n shows the message from the API. The second field, Base URL, defaults to https://api.dakoty.com/api/v1/public and exists only so you can test against a local Dakoty.

Create the key in Dakoty under Integrations → API keys and pick the preset Make / Zapier / n8n – bežné použitie (the preset name is in Slovak in the CRM). The preset does not include invoices:write or bookings:write, so Create an invoice, Create a booking and Cancel a booking return 403 until you add those scopes. The scope rules are in Authentication and scopes.

The Dakoty node

One node with seven resources and 33 operations, the same scope as the Make app.

Resource	Operations
Lead	Create, Update, Get, Get Many, Find, Archive, Move to Stage
Company	Create, Update, Get, Get Many, Find
Contact	Create, Update, Get, Get Many, Find
Activity	Create, Update, Get, Get Many, Complete
Task	Create, Update, Get, Get Many
Invoice	Create, Get, Get Many
Booking	Create, Get, Get Many, Cancel

Each operation makes one request; each record in data becomes one n8n item.

• Get Many follows the cursor pagination of the list endpoint. With Return All the node requests pages of 100 until has_more is false; otherwise Limit (1 to 100) sets how many records come back. The rules are in Pagination and sync.
• Find calls the exact-match …/find endpoints and returns nothing when there is no match.
• Create and the other write operations accept an Idempotency Key (an Idempotency-Key header), so a retried workflow run does not create the record twice; see Idempotency.
• The dropdowns call lookup endpoints in the background and need the read scope of their area, for example users:read for owners.
• Errors show the API message and a description such as [403] FORBIDDEN. For 429 turn on Retry On Fail in the node settings. See Errors and rate limits.

The node identifies itself with User-Agent: n8n-nodes-dakoty/<version> (n8n).

The Dakoty Trigger node

On activation the trigger registers a REST hook: POST /webhooks with the n8n webhook URL, the events and the name n8n – <workflow name>. When you deactivate or delete the workflow, the node deletes the hook with DELETE /webhooks/{id} (204, and 404 counts as done). You do not paste URLs. See REST hooks and Webhooks for the pattern, delivery and retries.

You can pick any of the 41 events of the catalog (leads, companies, contacts, clients, activities, tasks, invoices, bookings, orders). The key needs webhooks:manage and the read scope of every selected entity, for example leads:read for lead.created.

Output. Simplified (default) returns all fields of the record plus event_id, event_type, occurred_at, organization and test, the same flat shape as the Make triggers. Raw returns the whole envelope with the record under data.

Signature. n8n hands the node the raw request body, so unlike Make the trigger verifies the signature. Verify Signature is on by default: the node checks webhook-id, webhook-timestamp (5 minute tolerance) and webhook-signature (HMAC-SHA256 with the whsec_… secret returned when the hook was created) as described in Verifying signatures. A request that fails the check gets 401 and starts no execution.

n8n’s Listen for test event registers its own hook and removes it afterwards. The n8n webhook URL must be reachable over https from the internet; Dakoty rejects localhost and private addresses.

Where to go next

• Getting started with the Dakoty API for a first call with curl, Node.js or Python.
• Authentication and scopes to choose the right scopes for your key.
• API reference for every endpoint and field.