Power Automate

Import the private Hoko connector and create links from a Power Automate flow.

Download the preview connector

The connector runs in Power Automate, Power Apps, or Copilot Studio and calls Hoko's existing API. No dedicated Hoko job runner is required. Local REST checks pass; Microsoft import and workflow execution still need verification in an authorized disposable environment. This is an actions-only private preview, without marketplace listing.

Microsoft currently requires OpenAPI 2.0 and a definition smaller than 1 MB. This export is generated from Hoko's canonical contract; it introduces no new API version. See Microsoft's connector FAQ.

Create a connection

  1. Create a custom connector from the definition in your Power Platform environment. 2. Import the connection properties if your tooling supports that file. 3. Create a connection with a Hoko API key that has linksRead and linksWrite.

The secure connection sends X-API-Key to https://api.hoko.to. The key selects the Hoko workspace and permitted collections. There is no workspace override, session cookie, or human token field. Keep the key in the connection, outside flow payloads and logs.

Use disposable local Hoko fixtures for tests. Staging, production, and Playground are not disposable databases. A cloud flow needs an explicitly authorized reachable fixture before it can run acceptance checks.

Prevent duplicate writes

Set the create action's retry policy to None. Use one serialized flow as the exclusive owner of each mapping. Persist a prepared intent, payload fingerprint, and request ID in a durable store before sending the create request. A connector definition alone does not supply that store or enforce serialization.

After a timeout or uncertain response, use the external ID lookup. Do not send another create request automatically. Missing or multiple matches, changed input, or an unresolved prior intent require operator reconciliation. Keep the intent when execution fails; deleting it permits duplicate writes.

Hoko still enforces scopes and rate limits through the shared engine. Preserve X-Request-Id, the X-RateLimit-* headers, and Retry-After for support and scheduling. Treat 401 and 403 as a connection or permission issue. Respect 429 and reconcile before any later write.

Remove the preview

Remove the test flow, connector, connection, and owned fixture records, then revoke its temporary Hoko key. Provider import, connection, create, lookup, denial cases, and cleanup must be recorded before this connector is called verified.