- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Custom fields are available when you are editing emails either when Sending Manual Emails, creating email templates, or creating emails in Collection Paths.
Custom Fields Format
All custom fields start with {{ and end with }}
Custom Field Name | Description |
---|---|
{{customerRef}} | The customer reference field, if one exists. E.g. 'CAN001' |
{{customerName}} | The name of the customer. E.g. 'Cannon Supplies Ltd' |
{{contactName}} | The name of the contact at the customer. E.g. 'John Doe' |
{{senderName}} | The name of the email sender. This is taken from the Name field value stored in Collection Path Settings |
{{senderEmail}} | The email address of the email sender. For emails sent via Collection Path, this is taken from Email field value stored in Collection Path Settings. For manual emails, this is the email address of the logged in user. |
{{companyName}} | The name of your accounting company linked to Credit Hound. E.g. Bellweather Garden Supply |
{{companyTelephone}} | The telephone number of your accounting company linked to Credit Hound, |
{{companyWebsite}} | The website address of your accounting company linked to Credit Hound, |
{{#transactions}} | Indicates the start of a transactions list. Since an email can reference multiple transactions, we use this to indicate the start of the list. |
{{/transactions}} | Indicates the end of a transactions list. |
{{transactionRef}} | The transactions reference value. |
{{transactionDate}} | The date of the transaction. |
{{transactionType}} | The type of the transaction. E.g. 'Invoice' |
{{dueDate}} | The due date of the transaction, i.e. the date it should be paid by. |
{{transactionAmount}} | The total amount of the transaction. |
{{outstandingAmount}} | The outstanding, unpaid amount of the transactions. |