Use Hoko with Make
Use Make's HTTP module or its private Hoko app definition.
Before you start
Create a key with the scopes your modules need. Private app import and signed triggers need Make custom-app access. They are not a public marketplace listing.
Connect Make
For REST, use the HTTP module with https://api.hoko.to. Resolve a collection with GET /collections, create with POST /links, and find with GET /links?externalId=.... Send the key as a bearer header.
Use https://mcp.hoko.to only if your Make account exposes an MCP client module.
Verify the connection
Run a collection read first. Save each external ID and reconcile an uncertain create before retrying. Use a customer-owned HTTPS relay for signed events because Make does not preserve Hoko's raw signed bytes.
Fix common issues
- Treat 401 as an invalid key.
- Treat 403 as a missing scope.
- Treat 429 as a rate limit.
- Honor Retry-After.
Disconnect
Remove the connection, scenario, and webhook, then revoke the Hoko key.
Build the first module
In Make, create an HTTP Make a request module. Set the URL to https://api.hoko.to/collections, add Authorization as a bearer header, and run the read. Use the returned collection ID in a second POST https://api.hoko.to/links module. Save the external ID before any write. The private app definition and signed trigger require custom-app access.