Tokens insert submission, form, site, and generated-file values into template and delivery fields.
Use token syntax with double braces:
{{ token_name }}
| Token | Meaning |
|---|---|
{{ submission_id }} |
ConcreteCMS Express entry ID for the submission. |
{{ submission_date }} |
Submission date. |
{{ submission_time }} |
Submission time. |
{{ form_name }} |
Display name of the Express form entity. |
{{ site_name }} |
Current site name. |
{{ date }} |
Current date when the rule runs. |
{{ time }} |
Current time when the rule runs. |
{{ download_link }} |
Download link inserted into email body when the email action is configured to include a link. |
Express form fields can also be available as tokens when the rule runs. Token availability depends on the selected form and the fields saved with the submission.
Tokens are commonly used in:
Some token values can be transformed with filters:
{{ form_name|upper }}
{{ form_name|lower }}
{{ submission_date|date('Y-m-d') }}
If a token cannot be resolved at runtime, the output may be empty or the template/delivery action may need review. Use Execution Logs to diagnose token-related failures.