Plunk's system event list for automation workflow

最終更新日: 2026/06/21

阿部 隼也

AIイノベーションズ 代表取締役社長 | x.com/ai_abe_shunya

Plunk does not show system event list in their docs because the feature is new(? idk) so we need to find them on their code.

These are confirmed event list you can use for workflow against the actual Plunk source code — here's the answer:

"System events" = Plunk's reserved, auto-tracked events

Plunk splits events into two kinds:

• Custom events — ones you track with POST /v1/track.
• System events — a fixed set Plunk fires itself on a contact when something happens. The code calls these "reserved" events: you can't create or delete them via the API (there's an isReservedEvent() guard in EventService.ts that throws Cannot delete reserved system event), but you can use them as workflow triggers exactly like custom events.

So in the Workflows trigger table, the EVENT trigger fires on "custom event via /v1/track, system events such as email.received or contact.subscribed, or segment entry/exit events." That single table cell is the only place the phrase "system events" appears in the prose — which is almost certainly why you couldn't find it.

The complete list (from the source, not the docs)

From the webhooks event table + the isReservedEvent() patterns in apps/api/src/services/EventService.ts:

Reserved pattern in code: email.*, contact.subscribed / contact.unsubscribed, and segment.*.entry / segment.*.exit.

Sources:

• Plunk Workflows concept doc
• useplunk/plunk — webhooks.mdx
• useplunk/plunk — receiving-emails.mdx
• useplunk/plunk — EventService.ts