Understand core CRM hooks used by Courier

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

This guide explains that which external CRM events update module records.

What this guide helps you do

Know which external CRM events update module records. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.

Follow these steps

1. Go to Core CRM event → Courier hook.
2. Check the source record and choose the supported action.
3. Save or submit once, then reopen the record and verify the result.

Fields and options

Rules and limits

• Use the supported screen and permission; do not bypass validation or edit database records directly.

Check it worked

• The source record, status/history and any downstream notification, provider, POD or finance record should agree after the action.

Security, audit and operational checks

• Use the exact record and least-privilege role before changing any state.
• Verify the saved record after every action; a browser message alone is not evidence that every downstream step completed.
• Use protected document and image routes rather than exposing server filesystem paths.
• Keep customer, driver, provider, financial and credential data within the authorised workflow.
• For provider, finance, employment, transport and compliance decisions, follow the organisation’s authorised professional process.

Related guides