Skip to main content
MailerPath can store workflow-related preferences so you can keep client-specific behavior organized. This is useful when you want a client to keep a list of enabled workflows or a small set of preferences that affect delivery and automation.

​
What can be stored

  • Enabled workflow list
  • Client preferences object

​
Why clients might use this

  • Keep workflow choices grouped in one place.
  • Support client-specific delivery preferences.
  • Make account-level configuration easier to review.
  1. Keep the data structure simple.
  2. Store only preferences that are useful to the client.
  3. Review values when workflows are added or removed.
  4. Avoid duplicating data that already lives in another setting.

​
Good practice

  • Use clear keys and labels.
  • Keep the preferences object small and readable.
  • Treat this as supporting configuration, not a replacement for core settings.