Need

Would you like to minimise repetitive manual tasks in your contract management by connecting Tomorro with other software?

This quick memo is for you, to help you prepare for setting up the interface.

Thanks to our public API, you can connect Tomorro to thousands of applications to automate and streamline your work.

Before you get started, you will find our tips on this page to help you clarify and structure your needs.

In summary: Adopt a structured approach!

This note will focus on three main points:

Understanding how the interface works
Clarify your needs in order to define your approach
Configure and test before going live

What can you do with the API?

An API (Application Programming Interface) is a set of rules and protocols that enable software programs to communicate and exchange data with each other.

CRM (HubSpot, Pipedrive, etc.): to automatically update opportunities and track the progress of signed contracts, or to automatically generate your contracts as soon as the deal is won or reaches a certain stage.
HRIS: to automatically generate your HR contracts as soon as the candidate accepts their job offer.
Storage (Google Drive, SharePoint, OneDrive, etc.): to automatically archive signed documents.
Database (Excel, Google Sheets, Typeform, etc.): to record and centralise contract information in real time or to automatically create your contracts as soon as a new entry is added.
Messaging & notifications (Slack, Teams, email, etc.) to receive automatic alerts about contract updates.

⚠️ Remember to check the compatibility of your third-party tool with API calls.

How does the API work?

APIs allow you to exchange all data stored on Tomorro, but also to receive all types of data from third-party software.

In short, it is essentially a language that allows software to communicate with each other and exchange data.

Tomorro offers a wide range of ready-to-use actions:

Documentation on the capabilities of the Tomorro public API (to be shared with your IT team): https://developers.gotomorro.com/welcome

Configured automations can be triggered by a trigger (see below). However, the trigger can also be programmed and recurring (e.g. every night at 11 p.m.).

🚨 `Trigger`	💪 `Action`
Event that initiates automation and starts the flow.	Operation that takes place after the trigger has occurred.
Exemple de déclencheurs outil tiers : • Evolution d’un champ du logiciel tiers • Remplissage d’un formulaire	Examples of third-party tool triggers:• Change in a field in the third-party software• Form completion
Exemple de déclencheurs Tomorro : • Un contrat a été créé • Un contrat a été supprimé	Examples of Tomorro triggers:• A contract has been created• A contract has been deleted

Example of a Sales use case

Problem:

I maintain a database of my customers on my CRM system, including their associated information (name, company registration number, address, etc.).

I want to use this same data when creating my contracts to avoid duplicates and errors.

Solution:

Trigger: As soon as a field associated with customers is modified in my CRM
Action: Tomorro co-contractor fields are updated accordingly
How: Match CRM fields with Tomorro co-contractor fields

Example of an HR use case

Problem:

Every time I need to create a new employment contract, I have to retrieve all the information about the candidate and enter it manually into the custom fields on the Tomorro platform.

Solution :

Trigger: The candidate fills out a form to provide their personal information.
Action: Tomorro custom fields are automatically filled in from the form and create the contract.
How: Match the form fields with the Tomorro custom fields.

Advantages & Disadvantages

ADVANTAGES	DISADVANTAGES
Endless possibilities With our public API, virtually any action can be automated between your third-party software and Tomorro.	Costly configuration - Depending on your third-party software and the complexity of the automation, configuring the interface can be more or less difficult. - Requires coding knowledge.

Define your need

To ensure smooth integration between the two platforms, it is essential to properly frame the data flows upstream. Before you begin, make sure you have met the following prerequisites:

1️⃣ Validate functional prerequisites

Prerequisites
Confirm the availability of your third-party tool	Check with your IT team or directly with your service provider that connection via API is possible and can be configured.
Identify internal stakeholders	⇒ Who should be involved in defining requirements and configuring automation? A legal expert, an IT manager, another department?
Define the flow and data to be exchanged	⇒ Which processes should be automated? ⇒ What information should be retrieved and sent between platforms?
Check the technical requirements	Are there any constraints to anticipate? (Licences, security, etc.)
Ensuring access to the necessary tools	⇒ Does the team responsible for configuring the automation have the necessary permissions for the relevant third-party software, Tomorro, etc.?

2️⃣ Specify your process

Defining operational requirements

Before configuring automation, it is essential to clearly define your requirements.

To do this, focus on the ultimate goal: What is the purpose of my automation?

Also ensure that the trigger from your third-party tool:

Is unique (avoids ambiguity)
Is identifiable (easy to spot in your system)
Does not generate special cases (limits complex exceptions)

Recommended wording

We encourage you to structure your requirement as follows to facilitate the implementation of your automation:

I want action triggered on platform1...

... as soon as trigger element on platform2

Information exchanged is "list of custom fields" from platform2 to platform1

Example :

I want to create my contracts automatically on Tomorro...

... as soon as the "deal status" field changes from "prospect" to "customer" in my CRM.

❌ Bad example: "My Hubspot opportunity has signed."

✅ Specify instead: The "deal status" field changes from "prospect" to "customer".

The great power of the API is that these steps can be:

Multiple
Cascading
Bidirectional

3️⃣ Identify the data to be exchanged between tools

Define the data to be transmitted

It is crucial to identify which data needs to be exchanged between your third-party software and Tomorro. A good specification allows for:

Optimal alignment between systems
Avoiding double data entry
Tomorro configuration prerequisites: questions to ask yourself

Question	Example
Which Tomorro field(s) does the information retrieved from the third-party software correspond to?	Example: If a "Provider's address" field is present, it must be matched with the equivalent "Contractor's address" field in Tomorro to ensure correct synchronization.
Does the data format of the third-party software match with the Tomorro fields?	Does the data format of the third-party software match the Tomorro fields?
Which account should perform the action on Tomorro?	Tomorro tip: The use of a third-party "Tomorro bot" account (for example) can be used to create this kind of automatic contracts.

We suggest you build a correspondence matrix as shown below, in order to check the correspondence of the fields and their format.

Example :

Third-party software field name	Third-party software field format	Tomorro field name	Tomorro field format	Status	Third-party software field name
Service provider address	Text	Contractor address	Text	Available	Service provider address
Date of signature	Date	Date of signature	Date	To be created (on Tomorro or third-party tool)	Date of signature
...

Nous vous proposons de construire une matrice de correspondance tel que présenté ci-dessous, afin de vérifier la correspondance des champs et leur format.

Exemple :

Nom du champ logiciel tiers	Format du champ logiciel tiers	Nom du champ Tomorro	Format du champ Tomorro	Statut
Adresse du prestataire	Texte	Adresse du cocontractant	Texte	Disponible
Date de signature	Date	Date de signature	Date	A créer (sur Tomorro ou l’outil tiers)
…

Configuration

1️⃣ Configure and test

For this type of integration, it may be necessary for you and your IT team to run tests on test environments (sandboxes).

Tomorro will provide you with the information you need to make this connection. However, we recommend that you contact your third-party software provider to see if they can do the same.

Before deploying on a large scale, carry out tests to:

Check that the automations are working correctly.
Adjust settings and data formats if necessary.
Gather user feedback to refine the integration.

2️⃣ Go live

If testing was performed in a sandbox environment, the exchange will need to be reconfigured in the correct environment.

Once integration is in place:

Regularly monitor workflows to detect any malfunctions.
Update integrations in line with changes to connected tools or internal processes (be mindful of changes to Tomorro model settings).
Train users on the new automations to ensure optimal adoption.