Memory Wiki

Now I have a complete picture of the codebase. Let me create all 6 files.

All 6 files are created, pass PHP syntax validation, and the autoloader in `profe-crm.php` already references them correctly. Here's the summary: --- ## Summary ### Files Created **1. `/var/www/html/wp-content/plugins/profe-crm/includes/class-automation.php`** (16.7 KB) - **Class:** `Profe_CRM_Automation` - **CRUD:** `get()`, `create()`, `update()`, `delete()`, `get_all()`, `count()`, `count_by_status()` - **Step management:** `get_steps()`, `add_step()`, `update_step()`, `remove_step()`, `reorder_steps()` - **Stats:** `get_run_count()`, `get_completed_count()`, `get_active_contacts()` - All serialized fields (conditions, settings) handle `maybe_serialize()/maybe_unserialize()` **2. `/var/www/html/wp-content/plugins/profe-crm/includes/class-automation-step.php`** (10.9 KB) - **Class:** `Profe_CRM_Automation_Step` - **CRUD:** `get()`, `create()`, `update()`, `delete()` - **Validation:** `is_valid_action()` (9 valid actions), `is_valid_benchmark()` (3 valid benchmarks) - **Schema provider:** `get_action_settings_schema()` returns field definitions for all action types **3. `/var/www/html/wp-content/plugins/profe-crm/includes/class-automation-runner.php`** (27.1 KB) - **Class:** `Profe_CRM_Automation_Runner` - Core execution engine with full pipeline: - `start_automation()` — creates run entries, processes first step - `process_step()` — dispatches actions/benchmarks/wait steps - `process_next_step()` / `advance_to_next_step()` — walks the step chain - `process_delayed_steps()` — cron handler that processes `status='waiting'` runs whose delay has elapsed - `cancel_automation()` / `complete_automation()` - `get_contact_automations()` - Benchmark listeners wired via `profe_crm_label_applied`, `profe_crm_label_removed`, `profe_crm_activity_recorded` hooks - Fallback direct execution (`execute_action_direct()`) if the Actions registry isn't available yet - Uses `class_exists()` guards throughout **4. `/var/www/html/wp-content/plugins/profe-crm/includes/class-triggers.php`** (7.7 KB) - **Class:** `Profe_CRM_Triggers` - Registry pattern: `register()`, `get_registered()`, `get_trigger()`, `fire()` - 9 default triggers registered: `user_registered`, `contact_label_applied`, `contact_label_removed`, `studio_joined`, `studio_left`, `reputation_threshold`, `activity_occurred`, `contact_meta_updated`, `user_logged_in` - `fire()` queries all ACTIVE automations matching the trigger name and starts them via the Runner - Includes basic condition evaluation framework **5. `/var/www/html/wp-content/plugins/profe-crm/includes/class-actions.php`** (15.9 KB) - **Class:** `Profe_CRM_Actions` - Registry + executor pattern: `register()`, `get_registered()`, `get_action()`, `execute()` - 9 default actions with settings schemas: `apply_label`, `remove_label`, `send_notification`, `add_note`, `change_status`, `http_webhook`, `update_meta`, `remove_from_automation`, `wait` - Each action has a dedicated private executor method: - `apply_label`/`remove_label` → `Profe_CRM_Label_Relation::attach/detach()` - `send_notification` → `bp_notifications_add_notification()` with fallback to ContactNotes - `add_note` → `Profe_CRM_Contact_Notes::add()` (returns note_id as string) - `change_status` → direct `$wpdb->update()` on contacts table - `http_webhook` → `wp_remote_post()` with contact data payload - `update_meta` → `Profe_CRM_Contact_Meta::set()` - Extensible via `profe_crm_execute_action` filter **6. `/var/www/html/wp-content/plugins/profe-crm/includes/class-segment-builder.php`** (33.9 KB) - **Class:** `Profe_CRM_Segment_Builder` - 5-layer filter query engine using EXISTS subqueries (no cartesian joins): - **General** — contact field filters with operators: `=`, `!=`, `>`, `<`, `>=`, `<=`, `LIKE`, `NOT LIKE`, `IN`, `NOT IN`, `BETWEEN`, `IS NULL`, `IS NOT NULL` - **Labels** — `in` (any), `not_in` (none), `in_all` (has all), `not_in_all` (missing at least one) - **Custom Fields** (meta) — `=`, `!=`, `LIKE`, `NOT LIKE`, `IN`, `NOT IN`, `EXISTS`, `NOT EXISTS` - **Activities** — `in_last_days`, `before_date`, `after_date`, `never`, `count_gt`, `count_lt` - **Automation** — `entered`, `not_entered`, `completed`, `active`, `cancelled` - `query()` returns contact IDs, `count()` returns integer - Segment CRUD: `save_segment()`, `get_segment()`, `get_segments()`, `update_segment()`, `delete_segment()` - `query_segment()` loads a saved segment, decodes filters JSON, and runs the query - Automatic unique slug generation, JSON encoding/decoding for filters ### Key Design Decisions - All classes follow existing plugin conventions (no namespaces, `Profe_CRM_` prefix, `$wpdb->global`, `current_time('mysql')`) - All user input goes through `$wpdb->prepare()` — no raw SQL with concatenated values - `class_exists()` guards protect against missing model classes during early initialization - The Runner lazy-loads references to Triggers/Actions from the main CRM instance via `init` hook - Benchmark automations use WordPress action hooks to advance waiting runs when conditions are met