Zapier

REST hooks for Zapier/n8n: post to a target URL when Liza events occur (Triggers) and send messages (Actions). Base path: /v1/zapier · Auth: Bearer

Method	Path	Purpose
GET	/v1/zapier/events	List available trigger events
POST	/v1/zapier/hooks	Subscribe to a REST hook (event, target_url, filters)
GET	/v1/zapier/hooks	List your own hook subscriptions
DELETE	/v1/zapier/hooks/{id}	Unsubscribe from a hook
GET	/v1/zapier/triggers/{event}/sample	Sample/test data for a trigger
POST	/v1/messages	Send a chat message (Action) — see Messages

Trigger events

Event	Fires when …
list_item.created	a task was created
block.created	a chat block/message was created
notification.created	a notification was created

GET /v1/zapier/events is always authoritative; an unknown name is rejected on subscribe with 400 unknown_event.

Subscribe to a trigger

curl -X POST https://api.eu.liza.app/api/v1/zapier/hooks \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"event":"list_item.created","target_url":"https://hooks.zapier.com/…"}'

On each matching event Liza sends a POST to target_url. The body is — as Zapier expects for REST hooks — an array containing one record:

[ { "id": "…", "sid": "…", "text": "Prepare release", "list": "…" } ]

To stop it, remove the hook via DELETE /v1/zapier/hooks/{id}.

Delivery & cleanup

• Delivery is fire-and-forget per hook, with a 10 second timeout. There is no retry on failure.
• If a hook answers 410 Gone (Zapier reports this for disabled or deleted Zaps), Liza removes the subscription automatically.
• For testing, GET /v1/zapier/triggers/{event}/sample returns real sample data from your organization.

n8n

n8n uses the same mechanics (generic outbound hooks + inbound actions).