Complete list of available tokens:
| Token | Description |
{PortalName} |
Portal name |
{FirstName} |
First name of the recipient |
{LastName} |
Last name of the recipient |
{ClientName} |
Client related to the project (Note: Only available for project or finding-related emails) |
{PentestName} |
Pentest/Project name |
{ProjectStartDate} |
Start date of the project |
{ProjectEndDate} |
End date of the project |
{ProjectLead} |
Project Lead assigned to the pentest |
{ClientMembers} |
Client members associated with the project |
{Duration} |
Total duration of the workflow activity |
{WorkflowTaskTitle} |
The title of the related workflow task |
{WorkflowTaskDueDate} |
The due date of the related workflow task |
{FindingCode} |
Finding code |
{FindingTitle} |
Finding title |
{SentByFullName} |
User that triggered the action (e.g., created a finding, updated a finding's status). (Note: Only available for project or finding-related emails) |
{TeamName} |
Team of the user who created the finding (either the Portal Name or Client Name) |
{Project_CustomField?Field=FieldName} |
Pulls the value of a specific custom project field |
How to Use Custom Project Fields as Email Template Tokens
You can pull data from any Custom Project Field directly into your emails.
To do this, insert the {Project_CustomField?Field=FieldName} token from the dropdown, and replace FieldName with the exact internal name of your custom field.
Example: If you have a custom field named priority, you would format the token in your email editor like this: {Project_CustomField?Field=priority}
When the email is triggered, the system will automatically replace this token with the actual data entered into that custom field for that specific project.