Use QCLF Email Template Tokens

QCLF 1.1.27 defines 76 token names, but each email trigger exposes only the shared base tokens plus the event-specific tokens that make sense for that workflow. The Email editor updates its visible token buttons from the selected trigger.

Tokens are runtime context placeholders. They do not grant access to data that the event/recipient path did not already authorize.

Insert Supported Tokens

  1. Open the email template and confirm its Trigger/Recipient context.
  2. Use the displayed token buttons rather than guessing placeholder names.
  3. Keep recipient fields such as {recipient_name} tied to the person receiving that copy.
  4. Preview/test the template, then verify one real event with a safe test account before broad use.

Base and Event-Specific Context

Base tokens include recipient identity, site/product details, and notification-settings URL. Event-specific groups add Topic/Message, live-session, moderation/report, sanction, guest-approval, task/health, media, or entitlement context as appropriate. For example, private {guest_email} is defined only for guest/moderation-safe triggers.

Runtime Unresolved-Token Protection

Actual delivery performs literal token replacement and then scans subject, HTML, and Plain Text for unresolved {token}-style placeholders. If any remain, that template delivery is blocked and recorded as a failed attempt instead of sending a broken message.

Important Test-Renderer Boundary

Source-confirmed limitation: Send Test/Preview builds sample values for token-like placeholders found in the template, including a manually typed placeholder that is not in the canonical registry. Such a test can therefore look resolved even though a real event has no runtime value for that token. Use the trigger-aware token buttons as the validity authority; a real unresolved token will be blocked at delivery.

Keep Tokens Out of Secrets

The registry intentionally exposes safe notification context—not passwords, permanent managed-service credentials, or arbitrary private application state. Do not paste secrets into template bodies or create hand-written placeholders for them.

Community Discussion

Want to compare forum workflows, share practical QCLF tips, or discuss how other Joomla site owners use this feature? Visit the QC Live Forum Community. For private support, bug reports, account-specific entitlement problems, or feature requests, use the QuantaCade support system.