Integration - Signi and MAKE / Integromat

Modified on Thu, 13 Jun at 8:45 AM

Principles and benefits
Before you start integration
Signi connector methods vs. direct Signi API calls
Example integration scenario "Google Form > Signi using patterns" in Integromat
Example integration scenario "GoogleDrive > Signi with file transfer" in Integromat
Download and upload example blueprints of integration scenarios
More Information
Examples of implemented connections

Principles and benefits

Signi is an application, service, IT component that provides electronic signatures on documents from your environment, your customers, suppliers or employees. Signi can be used via a user interface or can be controlled via a so-called API.
Similarly, your application also has some kind of API that can be used to control it remotely, or at least some kind of file export, the ability to read from a database, etc.
MAKE/ Integromat is then the "glue" between the applications, a service that ensures that the two applications agree to work together, with the possibility to define scenarios how they should "talk" to each other, ...
... to automate the whole company process.

Before you start integration

Signing documents seems like a trivial task. You send a document for signature and it comes back signed. However, experience has shown that the variability of the signing process is quite large - Where does the data for signing come from? Who will sign when? What is to happen after the signature? What about refusal to sign or approval?

Therefore, we recommend at least a cursory review of the following topics in preparation for integration with Signi.

Most importantly:

You'll need to create two integration scenarios - one transmits the signing documents to Signi, while the other transmits back the signing results.
You can either pass either finished PDF/DOCX files as supporting documents to Signi, or just structured data to populate the template in Signi.
You can get the results back from Signi by creating webhooks in Integromat / MAKE and passing their addresses to Signi when passing the documents or by storing the contract_id i.e. the document number in Signi from the result of the call and periodically asking for their status.
Signi connector vs. direct Signi API call - The Signi connector for MAKE/Integromat contains the basic methods in a basic variant. If that's not enough for your needs, an option is to directly call the Signi API endpoints via the HTTP Request operator. See below for more details.

Example integration scenario in MAKE / Integromat : Pipedrive > Signi

Example integration scenario in MAKE / Integromat : Signi > Pipedrive

Signi connector methods vs. direct Signi API calls

the Signi connector for MAKE / Integromat contains the basic methods in a basic variant . Just search for it under the name "Signi" when building an integration scenario. See https://www.make.com/en/help/app/signi for more information.
HTTP Request for direct API call - If the connector is not enough for your needs, there is an option to directly call Signi API endpoints via the HTTP Request operator, which you look up under the name HTTP when building an integration scenario. See the Signi API call examples and Typical integration tasks for its parameters. This allows you to use new and advanced features that are not available in the connector.

Example integration scenario "Google Form > Signi using patterns" in Integromat

Signing a document using document templates in Signi is a very quick way to integrate when the integrated application contains the documents to create the document, but cannot create the actual document, it would be too complex or expensive.

To illustrate this, consider the integration scenario "Google Form > Signi" where the data for a document template is passed to Signi, Signi creates the document, adds the data, provides signatures and returns the signed document. Similar to Google Form, integration can be done with other form solutions like Typeform , or from ERP forms, CRM, SCM systems etc.

Integration scenario for MAKE Integromat Google Forms > Signi with data transfer to template
Google Form	Integration scenario in Integromat	The resulting signed document sent to the email address from the form

Fill out the Signi API - Test Contract 2022 Source of data for the document to be signed. The Submit button sends the data for further processing.	Download Demo Integration - Google Forms > Signi The script accepts structured data from the form. Sends it to Signi along with the Signi template number where it should be added, Signi creates a document based on it and sends it for signature. The result of the submission to Signi is emailed for further processing.	The resulting signed document, created from the Test Agreement template and supplemented with data from the form, sent as an attachment to all signatories. May include signatures at plain, guaranteed, recognized and qualified levels, may be preceded by remote identification up to AML Act level, document management may include long-term archiving for decades.

Example integration scenario "GoogleDrive > Signi with file transfer" in Integromat

Signing a document created from a file is a solution for situations where your application can create a file to sign and also supply data about who should sign what when.

You can see an example of the integration scenario "Google Drive > Signi" where files from a Google Drive folder are passed to Signi for signing.

Integration scenario for MAKE Integromat Google Drive > Signi with file transfer
File on Google Drive	Integration scenario in Integromat	The resulting signed document
There is a file in the Google Drive folder to sign. - here For the placement of signatures, it uses so-called signature placement fields - placeholders, so that Signi can place signatures where they need to be.	Download Signi Integromat Blueprint - Google Drive - HTTP Request The script retrieves the files from the Google Drive folder and passes them to Signi. At the same time, it passes the signature script in JSON format to Signi - here In it, to determine where in the document whose signature will appear, the names of the fields for the location of the signatures - placeholders from the document - are provided for the people.	The resulting signed document sent as an attachment to all signatories May contain signatures at plain, guaranteed, recognized and qualified levels, may be preceded by remote identification up to AML Act level, document management may include long-term archiving for decades.

Download and upload example blueprints of integration scenarios

Example scenarios for integration with Signi via MAKE/Integromat can be found in this folder..
You can import them into your MAKE/Integromat environment via Import Blue Print in the integration scenario editor.
The example scenarios have the workspace DEMO API key in them, you set your workspace API key in the Signi module parameters or HTTP request in the integration scenario.
Similarly, you will edit signature scenarios in JSON file format, send your files for signature etc.

Download and upload example blueprints of integration scenarios in MAKE Integromat
Uploading a blueprint from Make / Integromat	Setting the API key to your workspace	JSON containing signature scenario details

Blueprints of integration scenarios for download