Skip to main content

DocumentEmailCopy

The organization's own wording for one type of outbound document email: the subject line and one body paragraph, merged over the default template.

type DocumentEmailCopy {
askForProof: Boolean
body: String
emailType: String!
id: ID!
includeDetailsByDefault: Boolean
proofInstruction: String
proofReplyTo: String
showBankAccounts: Boolean
subject: String
updatedAt: DateTime!
}

Fields​

DocumentEmailCopy.askForProof ● Boolean scalar​

Sales order reminder only: ask the customer to send a proof of payment in the How-to-pay block. Null = yes (the default).

DocumentEmailCopy.body ● String scalar​

One body paragraph ({{token}} placeholders). Null = registry default

DocumentEmailCopy.emailType ● String! non-null scalar​

Registry key, e.g. 'QUOTE' | 'INVOICE' | 'PAYMENT_RECEIPT'

DocumentEmailCopy.id ● ID! non-null scalar​

The unique ID of this record.

DocumentEmailCopy.includeDetailsByDefault ● Boolean scalar​

Sales order reminder only: start the sender's Include payment details tick box ticked. Null = unticked (the default).

DocumentEmailCopy.proofInstruction ● String scalar​

Sales order reminder only: the proof request sentence ({{address}} = where to send it). Null = the default wording.

DocumentEmailCopy.proofReplyTo ● String scalar​

Sales order reminder only: the email address proofs of payment go to. Null = the Reply-To from Settings > Email, then the company contact email.

DocumentEmailCopy.showBankAccounts ● Boolean scalar​

Sales order reminder only: list the company's bank accounts in the optional How-to-pay block. Null = yes (the default).

DocumentEmailCopy.subject ● String scalar​

Subject override ({{token}} placeholders). Null = registry default

DocumentEmailCopy.updatedAt ● DateTime! non-null scalar​

When the record was last changed.

Returned By​

documentEmailCopies query ● updateDocumentEmailCopy mutation