Need

Would you like to create a contract or send it for signature as soon as an action has been performed in your third-party software?

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

Using Zapier, you can connect Tomorro to thousands of applications, automating and streamlining your work by minimizing repetitive manual actions.

Before you get started, read on for our tips to help you clarify and structure your requirements.

✅ In short: Adopt a structured approach!

This note will focus on 3 main points:

🪝 Understanding how the interface works

🥅 Clarify your needs in order to define your approach.

🧪 Configure and test before going into full production.

⚡️ What can I do with Zapier?

A true no-code tool, Zapier offers over 7,000 application integrations, providing great flexibility to connect various tools and automate your workflows. No technical skills required!

CRM (HubSpot, Pipedrive...): for automatic generation of your contracts as soon as a deal is won or reaches a certain stage.
HRIS: for automatic generation of your HR contracts as soon as the candidate accepts the promise of employment.
Database (Excel, Google Sheets, Typeform...): for automatic contract creation as soon as a new entry is added.

⚠️ Remember to check the compatibility of your third-party tool with Zapier:

Tomorro offers 2 ready-to-use Zapier actions:

Create a project
Send a project for signature

How does Zapier works ?

Zapier works on a simple principle: "A Trigger leads to an Action".

🚨 `Trigger`	💪 `Action`
Event that initiates automation and starts the flow.	Operation that takes place after the trigger has occurred.
Example of triggers (third-party tool) : Evolution of a field in third-party software e.g. "A lead becomes a customer in my CRM" Filling in a form e.g. "A new candidate sends me his personal information".	Tomorro actions : Creation of a project Send for signature

💡 Example of a Sales use case

Problem:

Every time one of my sales reps signs a new customer, I have to retrieve all the information about the company and enter it by hand in the contract's custom fields.

Solution:

🚨 Trigger: When the deal is signed (status of CRM field changes from "lead" to "customer")

💪 Action: Tomorro custom fields that automatically populate from the CRM and create the contract.

❓ How: Match CRM fields with Tomorro custom 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 by hand into the custom fields on the Tomorro platform.

Solution:

🚨 Trigger: The candidate fills in a form to enter his personal information.

💪 Action: Tomorro custom fields that fill in automatically from the form and create the contract.

❓ How: Match form fields with Tomorro custom fields.

Advantages & Disadvantages

ADVANTAGES	INCONVENIENTS
✅ Low human cost Quick and easy set-up Simplified maintenance once automation is in place ✅ Free version available: Free plan includes 100 zaps per month (excluding webhooks) Example: 1 zap = 1 contract creation OR 1 signature	⚠️ Limited functionality compared to API Fewer actions possible than with dedicated API integration Some complex automations will not be feasible.

🔦 Define your needs

To ensure smooth implementation of integration between the two platforms, it's essential to properly frame data flows upstream. Before getting started, make sure you have met the following prerequisites:

1️⃣ Validate functional prerequisites

Prerequisites
Validate the availability of your third-party tool on Zapier	Check via https://zapier.com/apps/tomorro/integrations
Identify internal stakeholders	⇒ Who needs to be involved in defining the requirement and configuring the automation? A lawyer, an IT manager, another department?
Define the flow and data to be exchanged	⇒ What processes need to be automated? ⇒ What information needs to be retrieved and sent between platforms?
Check technical requirements	Are there any constraints to be anticipated (licenses, security, etc.)?
Ensure access to necessary tools	⇒ Does the team responsible for setting up the automation have the required permissions for the third-party software concerned, Tomorro, Zapier, etc.?

2️⃣ Specify your process

⚙️ Defining operational requirements

Avant de configurer une automatisation, il est essentiel de bien définir votre besoin. Before setting up an automation system, it's essential to clearly define your needs.

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

Also make sure that the trigger :

✅ Is unique (avoid ambiguity)

✅ Is identifiable (easy to locate in your system)

✅ Does not generate special cases (limits complex exceptions)

📝 Recommended wording

We encourage you to structure your requirement as follows to make it easier to set up 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".

3️⃣ Identify data to be exchanged between tools

🔄 Define the data to be transmitted

It's crucial to identify what data is to be exchanged between your third-party software and Tomorro via Zapier. A good specification allows:

✅ Optimum alignment between systems

✅ Avoid double data entry

Mandatory data to be retrieved

Certain information is essential to the smooth running of the automation system. They must be correctly retrieved and mapped to Tomorro fields:

For contract creation

Project name, or any field used in Tomorro's naming nomenclature
Contractor name
Mandatory custom fields of the template as configured in Tomorro (summary sheet, generation form, conditions, approval workflows and archiving rules).

For sending by signature

Tomorro contract ID

Optional data to be retrieved

Some information, although not mandatory, may be useful for enriching the process and reducing manual input.

For contract creation

Model used for project creation
Document language
Non-mandatory fields in the template but present in the document

To send for signature

Note
E-mail addresses of signatories

🧑‍🔧 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
...

🔧 Configuration

1️⃣ Configure and test

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

🔍 Check that automations are working properly.

⚙️ Adjust parameters and data formats if necessary.

📢 Gather user feedback to fine-tune integration.

Testing does not need to be carried out in a sandbox environment. You can create dummy contracts or send them for signature from your production Tomorro account.

However, we recommend that you run your tests with a dedicated template, so that you can easily trace them and delete them once the configuration is ready.

2️⃣ Go live

If you've created a test template, remember to modify your configuration by pointing to the desired template.

Once the integration is in place:

🔎 Regularly monitor workflows for any malfunctions.

🤖 Update integrations in line with changes to connected tools or internal processes (watch out for changes to Tomorro model settings).

👥 Train users on new automations to ensure optimal adoption.

🪂 How do I get my Tomorro API key?

To connect Tomorro to Zapier, you'll need to obtain your API key. You'll find it on Tomorro by navigating to "My account > Integration > API > Manage integration", then clicking on "Generate API key".

🪝 I'd like to create an automation when an action is performed on Tomorro.

Unlike the automation described above, you may need to trigger an automation when an action is performed on Tomorro. This means that the automation trigger is no longer on the third-party software, but on Tomorro (in reverse).

It is perfectly possible to create an automation of this kind using a Webhook

LINK

🔗 I'd like to create an automation using API.