Zapier
Start a Zap when a lead arrives, a chat is handed over or a question goes unanswered, or ask your agent a question from any Zap. No code needed.
Zapier is on Growth and Scale. On Free and Starter it is locked, with a link to your plans.
Note
The hiy app isn’t in Zapier’s directory yet, so searching Zapier for hiy finds nothing today. It is also rolling out to selected workspaces first: ask at hello@hiy.ai to be added early. For simpler rules inside hiy, see Automations.
Set it up
Open Workspace › Developers › API keys, name a key “Zapier” and copy it. See API keys.


In Zapier, pick one of the triggers below, or add Ask the Agent as a step.
Paste your API key when Zapier asks. Its Test step lists your agents to confirm the key works.
Pick the agent to watch or ask from the list. Ask the Agent works with Support and Team Agents. An agent of any other kind can start a Zap, but it doesn’t answer one.
Add what should happen in your other app: a row in a sheet, a Slack message, a card on a board.
Triggers
New LeadeventSomeone left their contact details, whether or not the chat was handed over. Event name
lead_captured.
hiy sends each event to Zapier the moment it happens. If a Zap can’t receive it that way, Zapier checks hiy every few minutes instead. Zapier handles the switch for you.
Actions
If your agent can’t answer, the question lands in the Teach queue like any other.
Good to know
- One API key can ask one agent 100 questions a day.
- Only a live, approved agent answers. A draft, or one still awaiting review, answers as if it isn’t there.
- A paused workspace, or a plan that has used its messages, refuses Zapier the same way it refuses a visitor.
- With masking on, the conversation sent to Zapier is the masked text. The lead’s contact details are sent as given.
- Zapier’s calls count against your key’s limits a minute, the same as the API’s: see API keys.