@feastalytics/cli 0.1.20 → 0.1.22

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/plugin/skills/feast/references/workflows/automations.md +1 -1
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@feastalytics/cli",
3
- "version": "0.1.20",
3
+ "version": "0.1.22",
4
4
  "description": "Command-line client for the Feastalytics platform — list, create, and update campaigns, automations, offers, and members-program rewards from the terminal.",
5
5
  "type": "module",
6
6
  "bin": {
package/plugin/skills/feast/references/workflows/automations.md CHANGED
@@ -38,7 +38,7 @@ Automations have a staging tier, and it is the default path. Changes accumulate
38
38
  ### Choosing the trigger
39
39
 
40
40
  - **Campaign flows: prefer `viewCampaign` over `signUp`.** A guest viewing the campaign page is the natural entry point: it captures new sign-ups *and* returning guests. Use `signUp` only for members-program welcome flows or a fire-once-at-registration moment.
41
- - **`offerRedemption`, `offerExpiration` and `pickupDate` are conditions, not triggers.** They never fire as triggers, so saving one as a trigger is rejected. Use them as conditions on an automation with a trigger that does fire (an expiration nurture chain checks `offerExpiration` as a condition).
41
+ - **`offerExpiration` is rarely a *flow* trigger.** Use it on an individual automation inside an expiration nurture chain, not as a standalone flow's trigger type.
42
42
 
43
43
  ### Conditions: the nested event/occur shape
44
44