Flow actions

Sliick Docs ships three Flow actions for use in record-triggered, scheduled and screen Flows. All three are designed never to throw: a failure comes back as success = false plus an errorMessage, so your Flow can branch on the outcome rather than halting the whole transaction.

The running user of any Flow that calls Sliick Docs needs the Sliick_Docs_Automation permission set.

Generate Sliick Doc

One record, and the Flow waits for the result.

Input	Required	Notes
templateId	yes	Must reference a template with a published release.
recordId	yes	Must match the release’s base object.
outputFormat	no	PDF (default) or Word. Must be enabled on the template.

Outputs: jobId, contentDocumentId (the saved file), success, errorMessage.

Generate Sliick Docs (Bulk)

Many records, in the background. The action returns the batch identifier immediately.

Input	Required	Notes
templateId	either	One of templateId or bundleId is required, not both.
bundleId	either	Pass this for bundle bulk runs.
queryCondition	one of	A record filter to target records.
recordIds	one of	A list of up to 2,000 record IDs.
reportId	one of	A tabular Salesforce report of up to 2,000 rows. The report’s primary object must match.
jobLabel	no	Defaults to Flow Run @ <timestamp>.
batchSize	no	1 to 200, default 1.
outputMode	no	Individual (default), Combined or Both.
outputFormat	no	PDF (default) or Word. Word requires Individual output mode.

Outputs: batchId, success, errorMessage.

One important Flow-authoring rule: pass your record collection to the bulk action once, not inside a Loop. Wrapping the bulk call in a Loop creates one batch per record instead of one batch for the whole set, which is almost never what you want.

Generate Sliick Bundle

One record, several templates, one combined file, and the Flow waits for the result.

Input	Required	Notes
bundleId	yes	Must reference a bundle with a published release.
recordId	yes	Must match the bundle’s base object.
outputFormat	no	PDF (default) or Word. Bundle Word uses the org theme.

Outputs: jobId, contentDocumentId (the combined file), success, errorMessage.

A Flow cannot generate a download-only template. A Flow has nowhere to hand a file to, so a template configured to offer a download without saving the document is refused before it runs, with a message naming the setting to change. Organisations on the premium rendering path are unaffected: those renders always save the document.

Three automation shapes this unlocks

1. Auto-on-state, in a record-triggered Flow. An Opportunity entry condition of IsClosed = TRUE calls Generate Sliick Doc with a template and the record’s Id, so a closeout PDF lands on every newly closed Opportunity automatically. Pair it with auto-email to send it to the customer too.
2. Recurring batch, in a scheduled Flow. Daily at 2am, get the Accounts updated yesterday, then make a single call to Generate Sliick Docs (Bulk) with the resulting collection. Customers receive an overnight statement.
3. User-driven bulk, in a screen Flow. A picker for the template and a picker for the filter or report, then Generate Sliick Docs (Bulk), then display the returned batch identifier with a link to the Doc Batches tab so the user can monitor progress.