Integrations

Webhooks and Zapier

Updated on 11/3/2026

Send your store's events to other tools with the Zapier integration.

What it does

Horsee delivers your store's events (order created, order paid, refund, chargeback, new lead, new contact and abandoned cart) to Zapier, which passes each event on to your CRM, ERP, spreadsheet or email marketing tool. Today there is no screen to register your own webhook URL: sending events out of Horsee goes through Zapier.

Available events

  • order.created: new order created
  • order.paid: payment confirmed
  • order.refunded: order refunded
  • order.chargedback: chargeback received
  • lead.created: new lead
  • contact.created: new contact
  • cart.abandoned: abandoned cart

Step by step

  1. In the store menu, open Settings > Apps and, on the Zapier card, click Configure.
  2. Click Generate key and copy the API key. Save it now: it won't be shown again.
  3. In Zapier, create a Zap and search for the Horsee app.
  4. Under "Connect account", paste the API key.
  5. Choose a trigger (paid order, new lead, abandoned cart…) and the action in the destination app.
  6. To use the abandoned cart trigger, enter in the Abandoned cart field how many minutes of inactivity fire it. Empty or 0 means off.

The Zapier window in Horsee shows how many Zaps are connected and the date of the last delivery.

What each event contains

Each event arrives as JSON with the event name, the store and the date. Order events include the number, status, currency, total, payment method, the customer (name, email and phone) and the items (name, SKU, quantity and price). Lead events include the type, the source, the cart value and the UTMs. In Zapier, each field shows up for you to map in the destination app.

Common errors

  • Last delivery failed: Horsee retries when Zapier doesn't respond. If it keeps failing, open the Zap in Zapier and check its run history.
  • You lost the key: click Regenerate key and paste the new key into the Zapier connection.
  • Zaps stopped receiving events: check that the key wasn't revoked. After you click Revoke, connected Zaps stop receiving events until you generate another key.
  • Abandoned cart doesn't fire: the minutes field needs a number greater than zero.
Tip: to read store data on demand (AI agents, scripts), see the API and MCP article in the Help Center.

Was this article helpful?

Your feedback helps us improve our guides