Salesforce Automation for Document Generation & Signing

 

If you are a Salesforce geek, then you probably already know that automation is one of the biggest advantages the #1 CRM provides. The Salesforce platform and its workflow automation tools can help you streamline almost any business process you can think of. In this article, we focus on how to automate document generation and signing processes in Salesforce, with the help of Titan, a no-code platform built for Salesforce. The benefits of automating both your doc gen processes and your Salesforce eSignatures are that you will ramp up efficiency, save on administrative time, promote accurate data entry, and close your biggest deals fast.

Business Automation for Salesforce Doc Gen

First up, we take a look at how you can automate your document generation for Salesforce using Titan combined with the power of Salesforce Flows.

Salesforce Flows is a workflow tool designed to help you automate your business processes and increase efficiency in your organization. Using Salesforce Flows, you have the ability to curate guided and personalized experiences for users by automating any number of steps in a workflow process to suit the needs of your company and niche.

Titan Docs is a market-leading Salesforce solution that enables you to dynamically generate documents, such as quotes, proposals, and invoices, using real-time Salesforce data. You can work with any standard or custom object in Salesforce and push any doc to Salesforce in seconds.

Before we learn more about triggering a Titan document from within a Salesforce Flow, ensure that you have an API-enabled edition of Salesforce and that you have installed Titan via the AppExchange. Finally, remember to connect Titan to Salesforce.

You can work with any Salesforce record but for this use case, we will look at an Account:

After this, as an example, you can log a call:

After you click save, this data will be visible in a document that will be sent to you and relevant users. Let’s see how this works in a Salesforce Flow!

Visualize your process automation solution in a Salesforce Flow, where you can use a trigger of your choice to send your document. In the scenario below, we have set up our flow for the Account object, where the trigger is pulled every time an Account record is updated:

Using Titan’s package for Salesforce, you can call Titan using a custom Apex Class. It is this Apex Class that will ultimately generate your document. The Apex Class is called FTDocGen and for it to work properly, you need to correctly set its input values: the APIKey and FormHash of your document, as well as the ID of your object:

To get complete information on how to find these input values, check out the section on document generation in this FTDocGen guide. To find out more about how Titan’s package can streamline your process automation solutions, read more about its Salesforce package.

Once these steps are complete, your document and all its changes will be attached to an email. You will be able to see the call you logged in your Account. This document is fully dynamic:

Check out this video to learn more: Automate Doc Gen with Salesforce Flow.

Process Automation for Signing Documents

Now that we have taken a look at a use case for automating document generation from within a Salesforce Flow, let’s examine how you can automate signing processes using Titan Sign and Salesforce’s workflow tools. 

As mentioned in the above Doc Gen section, you will need to have installed Titan and have an API-enabled edition of Salesforce to get going.

Titan Sign enables you to work with any record of your choosing in Salesforce, but for the sake of this example, we are using a Standard Opportunity:

In order to illustrate this use case, we have changed the stage of the Opportunity below to “Proposal/ Price Quote”, before marking it as complete:

As we will see in just a moment, this is the action that will send a dynamic document to be signed by an internal or external user.

Let’s head over to our Salesforce Flow to see how this is all setup. You can see that the Opportunity object is configured at the start of the flow:

Simply click on this object to find out what makes it tick and you will see that the flow will be triggered every time you update a record:

You will also be able to see that the conditions for this record are “StageName Equals Proposal/Price Quote”. (You might remember that you met this condition a few steps back when updating your Opportunity).

But how does this trigger a signing process? Well, Titan Sign is triggered by an Apex Class, FTDocGen, that you can call from within your Salesforce Flow. This empowers you to automate the entire signing process.

This Apex action requires the API Key and FormHash input values from the document you want signed as well as the ID of your object. Learn how to get these values in the section on Titan Sign in this guide.

You have viewed what this automation looks like within a Salesforce Flow. Next, check your inbox to verify that the action has been triggered successfully. And hey presto, you will see you received a request to sign a document. You can sign by clicking on the link to your document:

If you want, you can choose to set up 2FA so that the user will need to authenticate themselves at this stage. When your document opens in the Titan software, you can fill it in, map relevant fields to Salesforce, and click Finish Sign.

This is how you trigger a signing process from within a Salesforce Flow using Titan. Learn more via this video on Titan’s eSignatures for Salesforce.

Workflow Automation Software for Salesforce

Thanks for reading, we hope you enjoyed learning more about Titan’s business automation software for Salesforce. Why not try this no-code solution next time you want to automate your document generation or signing processes?