Automation

One record or thousands.

Every way to generate, one service behind them all.

From wherever work happens.

A button on the record page or a list, the Salesforce and Field Service mobile apps, a Flow, a schedule, Apex, REST, an Experience Cloud site, Claude or an Agentforce agent.

  • Record page
  • List
  • Mobile
  • Schedule
  • Flow
  • Apex
  • REST
  • Experience Cloud
  • Claude
  • Agentforce
One generation serviceThe same access rules and the same results, whichever way you ask.
PDFWord
A record page, a list, Flow, Apex, REST, an Experience Cloud site, Claude and Agentforce all ask the same Docable generation service, which makes the PDF and the Word file.

A few lines of Apex.

The same call makes one document or many. Flow and REST take the same request.

Apex · a PDF and an editable Word file for one record
DcsGenerateV1.Request request = new DcsGenerateV1.Request();
request.templateId = templateId;
request.recordIds = new List<Id>{ workOrderId };
request.outputs = new List<String>{ 'PDF', 'DOCX' };
request.requestKey = UUID.randomUUID().toString();

DcsGenerateV1.Result result = DcsGenerateV1.generate(request);

Flow, Apex and REST guides

In bulk, in the background.

Make one document or thousands in one run, by hand or from Flow and Apex, and follow each run on the Generation Runs tab.

The Generation runs tab in Docable, every generation in the org newest first: a Statement of account run, 3 of 3 made, and a Ternbrook delivery note run, 30 of 30 made, each in user mode with the template's Brand Kit choice and the time submitted.

The service report starter

On a schedule.

Month-end statements, weekly service reports, renewal notices: a schedule picks the records with rules or a SOQL filter and runs without Flow, as the person who set it.

A schedule in Docable named Month-end statements, on the Statement of account template with rules, marked Active: from 1 November 2026 at 06:00 Europe/London, every month on the 1st, Docable will make a PDF from Statement of account for each Account that matches your rules, skipping records it already did, running as you with your access; the next run and last run are shown.

Schedules in the documentation

On a phone. Even offline.

From the Salesforce and Field Service mobile apps. In the Field Service app you still preview the document and capture the signature offline; the file is made and saved to the record when the phone reconnects.

  • Generate Service Document in the Field Service mobile app while offline: the note Offline example, the document may differ and is made from the latest details when you're back online, and the example page of a site visit report for work order 00000046, Annual service: east roof array, rows 3 to 5, Coldharbour Leisure Centre, with the site photo, the result banners, the customer and site box and the work carried out, marked EXAMPLE, with Back and Submit at the foot.

    Offline: the example preview, filled from the phone

  • The Field Service mobile app's Data Sync page, marked UPLOADS PENDING, OFFLINE: Sync, Downloads completed, and Pending Uploads, 1, the document request saved on the phone at 2:01 PM.

    Submitted: made and filed when the phone syncs

Docable for Field Service

Learn how.

Step-by-step guides, with the screens.

Be first in line.

Docable is on its way to the Salesforce AppExchange. Join the waitlist and we'll tell you the moment it's ready to install.

Join the waitlistTalk to us