Preskočiť na obsah
Dakoty — PomocníkDakoty — PomocníkDakoty — Pomocník

Make app

The Dakoty app for Make is a set of modules built on the Developer API v1. It has 13 instant triggers (Watch …), actions and searches for leads, companies, contacts, activities, tasks, invoices and bookings, and one universal module, Make an API call. Nothing in the app is a separate API: each module calls an endpoint you can also call from your own code, so the API reference describes what the modules send and receive.

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

Connection and key

Section titled “Connection and key”

The connection in Make asks for one value, an API key that starts with dk_live_. Make sends it as Authorization: Bearer <key> and checks it with GET /me. A valid key shows the name of your organization next to the connection; a wrong or revoked key returns 401.

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 covers leads, companies, contacts, activities, tasks, reading invoices, bookings and orders, and webhook management. It 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.

Triggers use REST hooks

Section titled “Triggers use REST hooks”

When you switch a scenario on, the trigger module registers a webhook with POST /webhooks. The webhook is named Make - <event>, for example Make - lead.created. When you switch the scenario off or remove the trigger, Make deletes it with DELETE /webhooks/{id}. You do not paste URLs anywhere. The pattern is described in REST hooks, and deliveries, signatures and retries work as in Webhooks.

Triggers need webhooks:manage and the read scope of the entity they watch, for example leads:read for Watch new leads.

Actions and searches

Section titled “Actions and searches”

Each action (for example Create a lead or Move a lead to a stage) makes one request. Create a lead accepts an Idempotency-Key header, so a retried scenario run does not create the lead twice; see Idempotency.

Each search (for example Search leads) follows the cursor pagination of the list endpoint. The Limit field sets how many records one run returns; it defaults to 10 and the app never asks for more than 100 per page. The rules are in Pagination and sync.

The dropdowns in some fields (owner, pipeline, activity type, project) call lookup endpoints in the background. Those lookups need the read scope of their area, for example users:read for the owner list. The module description names the extra scopes it needs.

Make an API call

Section titled “Make an API call”

Use Make an API call for any endpoint that has no module yet. You enter the path after https://api.dakoty.com/api/v1/public, the method, optional headers, a query string and a body. The module adds the Authorization header itself, so you never type the key into a request.

The path must be relative to the API. Both /me and me work. The module always sends the request to api.dakoty.com, so the key cannot leave Dakoty.

Errors and limits

Section titled “Errors and limits”

The module shows the API’s error code and message in Make. Retry rules, the status codes and the rate-limit headers are in Errors and rate limits.

Availability of the Make app

Section titled “Availability of the Make app”

If you cannot see the Dakoty app in Make yet, you can reach the same endpoints with Make’s HTTP module. The Slovak help article How to connect Dakoty with Make shows how, starting with a GET /me check.

Section titled “Next steps and links”