Email generated documents
Sliick Docs does not email generated documents itself. To send documents, build a Flow as described here. A packaged email Flow action is planned for a later release.
E-signature emails (invitations, reminders and the signed copy) are a separate feature and are not affected.
One email for each generated document
Section titled “One email for each generated document”- Create a record-triggered Flow on Generation.
- Trigger: when a record is created or updated.
- Entry conditions: Status equals
Succeededand Artifact File Id is not empty, only when the record is updated to meet them. The second condition matters: in a Combined PDF only batch, each record’s generation has no file of its own. - Add a Run Asynchronously path and put the steps below on it, so the email goes out after the document is saved.
- Keep the run mode at System Context Without Sharing. People with only Sliick Docs User cannot see Generation records, so a Flow that runs as them would fail.
- Find the recipient. Root Record Id is the Id of the record the document was made for.
- To use an email template, Send Email needs a Recipient ID: a Contact, Lead or person account. For a Contact or Lead template that is Root Record Id itself. For another object, use Get Records on it and read a Contact lookup, for example an Opportunity’s primary contact.
- Without an email template, send to an address: use Get Records on the template’s object with that Id, read the email address you want (for example the owner’s), and write the subject and body in the action.
- Get the file. What Artifact File Id holds depends on where the document was saved.
- Salesforce Files (the default): Artifact File Id is a ContentDocument Id, and Send Email needs a Content Version Id instead. Use Get Records on Content Version where ContentDocumentId equals Artifact File Id and IsLatest is true, and keep the first record.
- Sliick Files storage: the document is not a Salesforce file, so it cannot be attached. Send a link instead: add the Sliick Files: Create Share Link action with File ID set to Artifact File Id, and put its URL in the email body. Share links are a Sliick Files premium feature and must be turned on in Sliick Files, and the user the Flow runs as needs the Sliick Files API permission. Test this branch once with a document saved to Sliick Files before you rely on it.
- If you use both, add a Decision on whether Artifact File Id starts with
069(a Salesforce file) and take the matching path.
- Send Email (the standard Salesforce action):
- Email Template ID with Recipient ID, or Subject and Body with Recipient Address List (step 2);
- Related Record Id: Root Record Id, so the email template’s merge fields read the record;
- Sender Type:
OrgWideEmailAddress, with Sender Email Address set to your org-wide address; - Attachment ID: the Content Version Id from step 3 (leave it empty when you send a share link). Attachment ID Collection takes several;
- Log Email on Send: on, if you want the email logged as an activity.
One email for each batch
Section titled “One email for each batch”- Create a record-triggered Flow on Doc Batch, when Status is updated to
SucceededorPartial Success, with a Run Asynchronously path. - For the combined PDF, use Get Records on Content Version where ContentDocumentId equals the batch’s Combined File Id and IsLatest is true, and put its Id in Attachment ID. The combined PDF is always a Salesforce file.
- For one file per record, use Get Records on Generation where Doc Batch is the batch and Status is
Succeeded, and loop over them with steps 2 to 4 above. - For one ZIP of all the files, wait for ZIP Status instead of Status. See Build a Flow that delivers the ZIP.
- Don’t attach “the files on the batch”: the batch also holds working files and the ZIP.
Limits
Section titled “Limits”- Salesforce allows 5,000 single emails a day across your org. Past that, Salesforce refuses the send.
- Send one test email with your largest document: the attachment size limit was not checked with Sliick Docs files.
- Sliick Docs Admin and Sliick Docs Automation can read every Generation and Doc Batch field these Flows use.
Upgrading from auto-email
Section titled “Upgrading from auto-email”- On an upgraded org the six Auto Email fields on Template and the four Email fields on Generation stay, but nothing reads or updates them. New installs do not have them.