ignacionelson 5c00d189e4 Deletions can start a Zap after all ...

I said they could not, in the guide, the Zapier page and the changelog.
That was carried over from the limitation of polling a list, where a
deleted row stops being returned and nothing marks the moment it went. It
was never true of the activity endpoint: file.deleted is recorded like
any other action, so ?action[]=file.deleted works today.

Checked with a test rather than the enum, which turned up the shape a
caller needs: a deletion entry has no subject, because the row is gone by
the time the entry is written, so the name is snapshotted into
context.name instead. Reading subject.name there gets you null.

2026-08-25 18:51:05 -03:00

..

api

Add an activity endpoint, so an integration can react rather than poll for shape

2026-08-25 18:44:51 -03:00

api-guide.md

Deletions can start a Zap after all

2026-08-25 18:51:05 -03:00

api-zapier.md

Deletions can start a Zap after all

2026-08-25 18:51:05 -03:00

email-oauth.md

Name the tab Outgoing email, not Sending

2026-08-24 06:58:28 +02:00