Use Hoko with Zapier
Use Zapier's MCP connection or its private app path.
Before you start
Create a key with the scopes your actions need. The private app and trigger path remain manual provider setup. They are not a public Zapier listing.
Connect Zapier
For MCP, add https://mcp.hoko.to and store the bearer key in Zapier's secure connection field.
For REST, use https://api.hoko.to. Resolve a collection with GET /collections, create with POST /links, and find with GET /links?externalId=....
Verify the connection
Read collections or links first. Save each external ID and reconcile an uncertain create once before any retry.
Fix common issues
- Treat 401 as an invalid key.
- Treat 403 as a missing scope.
- Treat 429 as a rate limit.
- Honor Retry-After. Keep secrets out of Zap steps and logs.
Disconnect
Remove the connection or private app credential and revoke the Hoko key.
Choose the path
Use Zapier MCP when your account shows the MCP connection option. Use Zapier Interfaces or the private app editor for the reviewed private app path. Use the REST action URL https://api.hoko.to only in an HTTP step, with the bearer key in Zapier’s secure connection. The Hoko private app is not a public marketplace listing.