Hosting Suite uses WHMCS hooks for client interfaces, checkout validation, lifecycle notifications, invoice events and scheduled processing. Install the complete hook set and decide which system owns each automation before adding custom integrations.
IN THIS ARTICLE
01 Verify the supplied integration files
- Compare the installed files with the current release package.
- Confirm both
includes/hooks/nabtech_hosting_suite.phpandincludes/hooks/nabtech_hosting_suite_trials.phpare present in the WHMCS installation. - Keep the trial-named hook installed even if you do not offer trials. It also connects module processing to the normal WHMCS cron.
- Check that an obsolete renamed copy of the same hook has not been left active after an update.
- Verify client-area output, a relevant lifecycle event and cron completion on a test service.
02 Assign one owner to each action
The normal WHMCS product setup setting controls when provisioning begins. Hosting Suite's application policy can add application setup to that process. A separate custom hook that creates the account again can cause a duplicate or conflicting operation.
For connected renewal services, the suite manages the relevant renewal invoicing path. Do not run another script that independently generates renewal invoices or advances due dates for the same services. Use the supported billing handoff when changing ownership.
03 Coordinate invoice and notification events
Invoice payment and refund hooks drive renewal, trial and AI-credit accounting. An external integration should record genuine transactions through supported WHMCS mechanisms, with correct invoice associations, rather than directly changing a paid flag in the database.
Lifecycle email handling can replace applicable native messages for managed services. Review the suite template's send setting before adding a second custom email for the same suspension or reactivation event. Some events have no native WHMCS equivalent, so test the actual event rather than assuming a fallback.
04 Test a custom integration
Document the hook event, target service population and expected change. Use a controlled test invoice or account and verify the action occurs once. Check retries, timeouts and repeated callbacks, because a successful external response may be delivered more than once.
Keep custom code in its own supported extension or hook file. Editing the distributed module hook makes upgrades harder and can remove essential guards.
What should I check if Hosting Suite automation stops?
Check for missing hooks, mixed release files, cron errors and disabled features before adding a replacement scheduled job. Inspect the existing operation history and remote state so a retry does not repeat work that already succeeded. Record the recovered file or setting and rerun only the verification needed for the affected workflow.