Zapier
Invoke Zihin agents from Zapier with the Invoke Agent action. It calls a
hosted agent (over @zihin/agent-client) and returns the result for use
in later Zap steps.
The Zihin Zapier app is being submitted to the Zapier marketplace. The steps below describe the connector once it's available.
Connect your account
| Field | Description |
|---|---|
| API Key | zhn_live_* / zhn_test_* from Settings → API Keys (the tenant is embedded). |
| Base URL | Defaults to https://llm.zihin.ai. Override only for a private deployment. |
| Allow custom base URL | Off by default. Enable only to target a base URL outside the Zihin domain whitelist — your key is sent there. |
| Allow HTTP / localhost | Development only. |
The connection is tested by listing your agents.
Action: Invoke Agent
| Field | Description |
|---|---|
| Agent | The agent to invoke — populated from your tenant (dynamic dropdown). |
| Message | The input sent to the agent. |
| Session ID | Reuse to continue a conversation; the output returns the session ID. |
| Temperature / Max Tokens / Timeout (ms) | Optional generation and call controls. |
| Include Raw Events | Include the raw SSE events in the output (debugging). |
Output fields (mappable in later steps): content, sessionId, model, usage (total tokens,
cost), sources.
Zapier caps each step at ~30 seconds. The action is best for agents that respond quickly. Long-running agents (asynchronous callback) are on the roadmap.
Error handling
Failures are mapped to native Zapier errors: an authentication problem prompts a reconnect, a rate limit triggers Zapier's hold-and-retry, and other failures surface a clear message — never leaking your API key.
Example
[Trigger] → [Zihin · Invoke Agent] → [Action with {{content}}]
- Create a Zihin connection (above).
- Add Zihin → Invoke Agent, pick the Agent, and map the Message.
- Use the
contentoutput in the next step; storesessionIdto continue the conversation.