Eminio CRM — Automation Test Console
Checkpoint 6 verification tool. Fill fields, tap a button, read the response at the bottom.
Worker Base URL
Sessions
SESSION A
Login A
not logged in
SESSION B
Login B
not logged in
Session B only needed for the cross-org isolation test (step 10).
1. Seed the 5 templates — POST /automations/seed-templates
Use session
A
B
Seed 5 templates
Creates all 5 disabled (is_active=0) — enable individually below.
2. List / Toggle / Delete rules
Use session
A
B
GET /automations
Rule ID
Toggle on/off
Get (+ recent executions)
Delete
3. Create a custom rule — POST /automations
Use session
A
B
Name
Trigger event
deal_created
deal_stage_changed
deal_won
deal_lost
deal_reopened
deal_value_changed
activity_completed
activity_overdue
contact_created
contact_updated
Action type
create_activity
add_note
assign_deal
assign_activity
change_deal_stage
create_notification
Delay (minutes, 0 = instant)
Conditions (JSON array, optional — e.g. [{"field":"value","operator":"gt","value":1000}])
[]
Action params (JSON object — e.g. {"type":"call","title":"Follow up","priority":"high"})
{"type":"call","title":"Test follow up","priority":"high"}
POST /automations
4. Manually run the tick — POST /automations/run-tick
Use session
A
B
Run tick now
Runs the exact cron logic immediately — scans overdue activities, processes due delayed executions.
5. Execution history — GET /automations/executions
Use session
A
B
status
(any)
pending
success
failed
skipped
GET /automations/executions
6. Notifications — GET /notifications
Use session
A
B
GET /notifications
Notification ID
Mark as read
7. Trigger real CRM events (uses existing endpoints)
These fire the SAME routes from checkpoints 1-5 — use them to prove automation actually reacts to real Deal/Contact/Activity changes.
Use session
A
B
Deal ID
New stage_id (for move)
PATCH /deals/:id/stage
Contact first name
POST /contacts (create)
Response Log
Clear
No requests yet.