Use Docable's actions in an Agentforce agent

Last updated 25 October 2026.

  • The assistant in Docable

    For people writing templates in Docable.

    Inside the editor. Choose Describe it with AI, or ask for changes.

    Needs Salesforce AI (Einstein) in your org

  • An Agentforce agent

    For teams that already use Agentforce.

    In Salesforce, using Docable's actions.

    Needs Agentforce in your org

  • Claude, or another AI app that supports MCP

    For people who already work in an AI app.

    Connected to Docable's MCP server, which Salesforce hosts in your org.

    Can rebuild a template from a PDF, Word file or picture you share.

    Needs Enterprise Edition or above

  1. A draft template in Docable

    With your fields and your Brand Kit.

    AI works with your template and field names. It prepares. It never approves.

  2. A person checks the proof and makes it live

    Approval and activation always stay with a person.

  3. Generate PDF and Word

    By hand or in bulk.

AI is optional. Everything also works by hand.

At the end your people have an Agentforce employee agent that drafts templates, prepares proofs and makes documents with Docable, running as each signed-in person. For Salesforce administrators who build agents.

The agent drafts. A person connects the fields, checks the draft and approves it in Docable; the agent never approves or activates anything. Docable does not ship a ready-made agent. It ships the actions, and a sample agent shows how to use them.

The Docable Template Assistant, an Agentforce agent, open beside a Work Order: the brief typed, Create a solar PV commissioning certificate template for work orders, branded with the HelioGrid kit, system details, the string readings as a table, site photos, pass or fail, and customer and technician signatures collected on the phone; the agent's plan listing what the template will include, and three questions it asks before it starts.
The Docable Template Assistant beside a Work Order: the brief, the agent's plan, and the questions it asks before it starts.

Before you start

  • Agentforce is on in your org, with employee agents available in your edition and licence.
  • Docable is installed, so its DcsOps*V1 actions exist, and each person has the Docable permission sets the agent’s actions need.

Steps

  1. Start from the Docable Template Assistant, a sample employee agent (not part of the package): one router and four subagents for templates, Brand Kits, proofs and approvals, and documents.
  2. Make it an employee agent with no agent user, so every action runs as the signed-in person and Docable’s permission, licence, record and field checks apply to them.
  3. Point each action at its class, for example apex://DcsOpsGenerateDocumentV1 for generate_document. Use the class’s own label, description, inputs and outputs.
  4. Require confirmation on every action that saves, notifies or makes documents.
  5. Tell the agent to call get_capabilities first, to find field names with search_schema and never write one from memory, and never to say it approved or activated anything.
  6. Give the agent only to people who hold all the Docable sets it needs: Docable Configure, Docable Definition Author, Docable Proof Author and Docable Brand Manager.

Example

In the sample agent, the documents subagent has the five generation actions: generate_document, start_generation_job, get_generation, cancel_generation and retry_generation. Asked to make a PDF, the agent says what it will do and waits for the person to agree before it runs generate_document. Asked for “the same document in our US branding”, it passes that kit as brandKit; the template must allow that kit, or Docable refuses and names the kits it allows.

Check it worked

Ask the agent to create a template. It calls get_capabilities, asks for confirmation before each save, and the answer gives a message and the editor link. Open the link: the draft is in the editor, ready for a person to connect the fields and approve. Ask the agent to approve and activate: it says that is a person’s step in Docable and calls nothing.

The AI draft open in Docable Studio: a Solar PV commissioning certificate on a Work Order with HelioGrid's logo, a field grid for the work order, customer, site address, asset, serial number and technician, a Scope of work section shown only when the description is filled in, a String readings table that repeats for each inspection, site photos, a commissioning result and two signing lines in the outline; the Assistant panel reports Draft created, describes the document, lists five assumptions and says nothing blocks proof now.
A draft made by an agent, open in the editor: the Assistant panel lists its assumptions for a person to check.

If it doesn’t work

What you see What to do
The agent says it can create templates, but nothing is created. The person lacks the Docable permission sets. Agentforce hides actions the person cannot use, so the agent never learns what they can do. Give the agent only to people with all four sets.
The agent is not offered in your org. Agentforce agents must be available and licensed. Use the assistant in Docable or Claude instead.
An action is refused with CapabilityUnavailable. Assign the permission set the message names.

Next

Something unclear or wrong? Tell support. Product page: Automation and API.