Integrations, shortcodes and extension points¶
Check how CRM-NG connects to other services and which interfaces a custom integration can use.
Needs: Technical reference
An integration needs more than an available menu. It may also require a compatible plugin, provider account, credentials, authorization and scheduled jobs. Check the connection status and a real test result for your installation.
Integration directory¶
| Integration | Purpose | Verification path |
|---|---|---|
| Booking Hub | Appointment scheduling | Settings → Online Booking; dependency status and test appointment |
| Google / Microsoft calendars | Staff calendar connection | Calendar authorization/status and controlled event test |
| SMTP / Gmail API | Outbound mail | Transport setup, test delivery and mail health |
| Slack / Teams / Google Chat / Discord | Incoming-webhook notifications | Allowed endpoint, test and delivery log |
| Stripe | Invoice checkout and processor events | Test checkout, signed webhook and invoice payment result |
| NetBox export | Inventory data handoff | Inspect export and validate destination mapping |
| Knowledge Base Git | Repository-connected content | Verify repository/path, sync behavior and article result |
| Lead-form import | Copy supported external form definitions | Import to draft and inspect mappings before publication |
| Workflow webhooks | External event intake/output | Secret endpoint or configured request, controlled payload and run history |
Add a portal or form with a shortcode¶
Place the appropriate shortcode on a page and test it with the intended type of user. Use the identifiers exactly as written; changing the displayed product name does not rename these interfaces.
| Shortcode | Purpose |
|---|---|
[client_portal] |
Customer workspace |
[employee_portal] |
Employee self-service |
[cg_onboarding] |
Client onboarding |
[cgcrm_lead_form id="123"] |
Published lead form; replace 123 with the actual ID |
[cg_service_wizard] |
Guided service needs |
[cg_service_explorer] |
Restricted pre-release service discovery |
Work with the REST endpoints¶
The application registers routes under cgcrm/v1. They include deal records and activity or stage actions, timer start and stop operations, searches for services and contacts, referral and related-record searches, knowledge-base category actions, and Stripe checkout and webhook routes.
Behavior depends on the release, enabled modules and account capabilities. Browser requests need a signed-in session. External integrations need the supported authentication method, while Stripe webhooks use signature verification. Knowing an endpoint's URL does not make it public or unrestricted.
Before building an integration, check the route against the deployed release and test the records and permissions it will use. The workflow registry lists additional options available through automation.