Make

Run Hoko's private link actions and link.created trigger in Make.

Use the private app

The Hoko Make app runs inside Make and calls Hoko's unversioned resource REST API. It needs no dedicated Hoko job runner, queue, scheduler, or background service.

The app is private. Make import, connection, scenario execution, and provider review remain external acceptance work.

Download the repository editor bundle: hoko.private-app.json. The file is generated from Hoko's source and is not a native Make one-click import or export file. Map base, connection, and each module's parameters, communication, and output fields into the matching Make editor sections. Select the saved Hoko connection on every module.

Configure the connection

Create a Hoko API key in Dashboard → Integrations → API Keys. Store it in Make's secure connection field. Use https://api.hoko.to as the Hoko origin. The key selects one Hoko workspace. Do not add a workspace ID to a module.

When you create each Make module, select the saved Hoko API key connection in the module's connection field. The bundle metadata does not bind a Make host connection automatically. Follow Make's custom-app setup, step 6.

The connection test and Find Link require linksRead. Create Link also requires linksWrite.

Use the actions

ActionRequired valuesResource routeEngine metadata
Create LinkDestination URL, Collection ID, External ID, Request IDPOST /linkslinks.createFromApi
Find LinkExternal ID, Request IDGET /links?externalId=...links.list

Pass a stable, namespaced source record identity as External ID. Keep it at or below 255 characters. Pass a required correlation Request ID at or below 128 characters. Use the exact same external ID for Find Link.

Create Link sends one raw create request. It does not check for an existing mapping or read the result again. Surround the action with a durable prepared intent, an exact lookup, and readback in one serialized scenario owner. Find Link requests two matches and returns a wrapper with matches, matchCount, requestId, and rateLimit. The scenario handles zero, one, or two matches.

Before creating a link, call GET https://api.hoko.to/collections with the same connection. Copy the returned collection ID into Collection ID. Resolve previously saved collection references through this lookup before writing a new mapping.

Set the scenario controls

Configure the Make scenario with these values:

SettingValuePurpose
Process data in orderOnGives each mapping one exclusive scenario owner.
Store incomplete executionsOffPrevents incomplete runs from being saved for replay.
Commit after each moduleOnCommits the prepared intent before the Hoko write.

Make normally commits at the end of a scenario. If a later module or timeout fails, that behavior can roll back the prepared intent. It does not undo a link that Hoko already created. Do not add a Retry error handler around Create Link. Automatic completion belongs to the Retry error handler; it is not a global scenario setting.

For personal data, you may enable Keep data confidential. Make describes that option as a privacy recommendation. It does not guarantee that data is absent from provider logs.

See Make scenario settings.

Successful output includes the Hoko link identity, short URL, destination URL, collection ID, external ID, and request ID. Valid rate headers produce bounded rateLimit metadata with limit, remaining, and resetAt.

Handle retries

Link creation has no idempotency guarantee. Disable automatic retry for incomplete executions and do not add a retry error handler around Create Link. Do not retry after a timeout, malformed response, or lost acknowledgement. Look up the exact external ID before any later write. Keep a prepared intent, source account, foreign record ID, payload fingerprint, request ID, and returned Hoko link ID in Make scenario state.

Treat 401 as an invalid or revoked key, 403 as a missing scope, and 429 as a rate limit. Create Link maps 429 and 5xx responses to runtime errors, because Make's rate-limit error class can trigger automatic retries. Honor Retry-After. Keep request IDs and rate metadata in redacted logs.

Keep the app private

This slice excludes analytics, API-key management, billing, profile uploads, destructive workspace actions, OAuth, MCP, and public Make distribution.

Use disposable local Hoko fixtures for acceptance. Do not use production, staging, or Playground as a test database. Record the Make app revision, scenario export, successful read and write, denied scope, revoked key, rate limit, uncertain-write handling, secret redaction, and cleanup before calling the app verified.