---
title: 21.3 Supported Event Types
description: "Application normalizes events from different platforms into canonical types. Common examples:"
url: "https://peikly.com/docs/integrations-event-types/"
updated: "2026-10-10"
category: External Integrations
tags:
  - Manual sync
---

# 21.3 Supported Event Types

Application normalizes events from different platforms into canonical types. Common examples:

| Category | Canonical Event Types |
| --- | --- |
| Customer lifecycle | `CustomerCreated`, `CustomerUpdated`, `CustomerDeleted` |
| Cart & checkout | `CartAbandoned`, `CartRecovered`, `CheckoutStarted`, `CheckoutCompleted` |
| Orders | `FirstOrderPlaced`, `RepeatOrderPlaced`, `OrderCompleted`, `OrderCancelled`, `OrderRefunded` |
| Products | `ProductViewed`, `ProductAddedToCart`, `ProductRemovedFromCart` |
| WordPress publishing | `PostPublished`, `PostUpdated`, `PostDeleted` |

How these behave in workflows:

- WordPress and WooCommerce customer, cart, checkout, product, and order events are treated as mixed triggers. You can use them with contactless steps or resolve a CRM contact first.
- PrestaShop and Shopify should target the same commerce trigger set when their connectors emit provider-backed events.
- WordPress post events are intentionally contactless. Choose those triggers when you want automations around content publishing rather than customer communication.
- If an event-driven workflow needs to send contact-based email or WhatsApp messages, add **Add/Upsert Contact** as its first step ([11.11](/docs/activity-add-upsert-contact/)). On **External Integration Event Received** this happens automatically before the first action step.