You have discovered Yousign API and want to integrate it fast and without issues in Salesforce? We have good news, you are in the right place!

This repository contains code examples to integrate the Yousign API into Salesforce. We will connect through named credentials with an API Key. The code samples, the initialization package and the documentation provided here complete but does not substitute the Yousign API documentation where you will find a dedicated Salesforce section 🚀

Check the License tab ☝️

1. Having an Yousign account with API. If you do not have an API key yet, please create a free Yousign trial account!
2. A Salesforce Developer, Enterprise (or above) Edition.
3. Visual Studio Code. Your Visual Studio Code should be set up with the necessary Salesforce development tools including the Salesforce CLI.

1. In Salesforce go to Setup > Process Automation > Process Automation Settings set an admin (generic account if possible) as Default Workflow User. Click Save.
2. Download or clone the SFDC-Toolbox repository. On github click the code button then select Download ZIP. Then unzip the files on your computer in folder.
3. In VS Code type Ctrl-K Ctrl-O (on Windows) or command-K command-O (on a Mac) to open a folder. Select the folder containing the downloaded files.
4. Authorize your Salesforce Developer Account within Visual Studio Code. To do this press command + shift + P (on a Mac) or Ctrl + Shift + P (on Windows) to open the Command Palette. Then type SFDX:Authorize an Org and press Enter. In the browser window that opens, log into your Salesforce Organization, then on the next screen, click Allow to grant access. If you don't see the SFDX:authorize an Org option, please check that you completed the 3rd point of the prerequisites.
5. Deploy the code to Salesforce.
   1. On a sandbox/developer organization Navigate to the force-app/main/default/manifest/ folder in the menu on the left and right-click the package.xml file, then select SFDX: Deploy Source to Org. Now when you sign into your Salesforce Developer Edition (account) you will find the clases and Lightning Web Components defined in this project.
   2. On a production organization Select the Terminal menu then click on New Terminal. Type sfdx project deploy start -x manifest/package.xml -l RunSpecifiedTests -t YS_INVOCABLE_GetSignedDocument_Test YS_INVOCABLE_UploadDocument_Test YS_Service_Test YS_MultipartUtil_Test YS_Utils_Test YS_WebhookListener_Test YS_WebhookDispatcher_Test YS_INVOCABLE_VisualForceToPDF_Test --verbose then press Enter.
6. Configure your organization by following the step detailed in the Getting Started documentation.

We gives access to Users through Named Credentials with Permission Sets. This allows to keep the API keys secrets and to fine tune user accesses to match business needs.

We integrated the Yousign API OpenAPI Specification (OAS) into Salesforce as an External Service. This way, all data structures used by the Yousign API are already created in your organization. You can used them to send requests to Yousign API from Salesforce easily through multiple means: Low code (flows), Code (Apex methods).

The schema below describe how the request are constructed in Salesforce to fill automatically the base path of the endpoint and the credentials. It also contains how Yousign replies.

To have the latest information in Salesforce, Yousign send webhooks to notified Salesforce. We then treat those webhooks with Platform Events.

We create some fields and object in Salesforce that match the Yousign object structure. This is a model based on the functionalities provided with this toolbox and do not support all of the features available in Yousign API.

Anything that can go wrong will go wrong. Murphy's Law

Although it should not happen (and we hope it will not), we have to face it: errors can happen. As most of the webhook management's work is done asynchronously for permfomance and security reasons, we need to log those errors to be aware of them.

We do not want to overcharge your organization by adding a Log__c SObject you might already have. As such we do not include our own Log__c SObject here. However some functionalities are ready to trigger a log creation if an error happens.

Hence, feel free to plug the following methods to your own logging object or create a new Log__c one for the occasion. The methods toErrorLog, insertExceptionsAsLogs and insertLogsFuture can all be found in the YS_Utils Apex Class and can be rapidly customized.

By exploring the code repository you will be able to find reusable and customizable examples. Here is a non-exhaustive list of where to find some examples you might want to work with.