App Functions — Design the Trigger & Execution Type

Decide what runs and when before you write any code.

Step 1 — Confirm the event contract

The doc-grounded event catalog — every trigger grouped Merchant vs Customer, its sync/async type, and its documented payload.data shape — lives in references/event-contexts.md. Use it to pick the trigger and read the context shape; never assume a payload.

Sources of truth: salla_functions action=list_triggers (no app_id needed) for live trigger names and categories; salla_functions action=get for a trigger's authoritative .d.ts. Customer-event docs ship illustrative payloads — confirm those field names via action=get or the schema doc before relying on them.

Gate: "Do you have the confirmed payload.data field names for this event?"

Step 2 — Choose the execution type