Setting up Agentforce with Documill

Description: Summarizes an Opportunity and runs Documill flow

Scope: Only handle Opportunity summarization and flow triggering

Example input:

“Create Quote for this opportunity 006XXXXXXXX”

“Create a proposal for [name of the opportunity] opportunity”

Instructions to include: 

1. Retrieve record ID from the current opportunity tab 

2. Alert user if products or contacts are missing 

3. Use any 18-digit ID starting with 006 as an Opportunity ID 

4. Inform if Opportunity Products or Contact Roles are empty 

5. Extract record ID from URLs or opportunity names if no ID is given 

6. Validate input before executing flows 

7. Set OppID = recordId 

Setup -> Process Automation -> Flows

1. Create new Flow (like Screen Flow)

2. Add new External Services Action element. This element should be the External Service operation ‘Post Task’ that was created previously. Now ‘Body’ should be listed in action’s Input Values. Give it value:

a.       New Resource -> Variable

b.       API Name -> “PostTaskBody” (could be anything)

c.       Data Type -> Apex-Defined

d.       Apex Class -> Select Dynamic Apex class that is created by External Services. Usually it is named like this:
ExternalService__<External Service name>PostTaskRequest
or similar.

3. Assign request body by creating ‘Assignment’ element before the action element. Give it a Label and Name. Each of the body property is set separately. Flow Builder should suggest the previously constructed Apex-Defined variable when searching for variables.

To retrieve the record, create a new variable as so:

The API Name OppID was defined in the Agent instructions above.

Once this variable is created, set it as the <recordID> in the assignmnet action.

Flow should be now set and ready for testing.

Setup -> Process Automation -> Flows

1. Create new Flow (like Screen Flow)

2. Add new External Services Action element. This element should be the External Service operation ‘Post Batch’ that was created previously. Now ‘Body’ should be listed in action’s Input Values. Give it value:

   1. New Resource -> Variable

   2. API Name -> “body” (could be anything)

   3. Data Type -> Apex-Defined

   4. Apex Class -> Select Dynamic Apex class that is created by External Services. Usually it is named like this:
      ExternalService__<External Service name>PostBatchRequest
      or similar.

3. Assign request body by creating ‘Assignment’ element before the action element. Give it a Label and Name. Each of the body property is set separately. Flow Builder should suggest the previously constructed Apex-Defined variable when searching for variables, similar to creation of Flow for Task API. Only exception is made when defining task array objects; each of the task objects must be constructed separately in Flow. To do that:

   1. Select Variable as body > tasks

   2. Operator as Add

   3. Value as New Resource -> Variable -> Give it a name (i.e. taskVar) -> Data Type as Apex-Defined -> Select Apex Class, that is named similar to this
      ExternalService__<External Service name>_PostBatchRequest_tasks

      Add these task objects as many as needed.

4. Before Flow is ready, previously created task objects needs “params” and “id” properties as stated in Post Batch documentation. New Assignment element is needed and placed before the body assignment element. Simply just give field values to task objects (taskVar > params > id) and Flow should be now ready for testing.

Note:
If the batch body content size grows substantially large and complex, consider implementing the integration using an HTTP callout instead of External Services. HTTP callouts provide easier control over request construction, allowing greater flexibility for modifying and managing the request body content.