Need

Would you like to retrieve data from your contracts to process it in third-party software, or simply be notified when one of these five actions is performed?

A contract has been created
A contract has been deleted
A contract has been fully signed
A contract status has been changed
An automatic reminder has been triggered

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

With webhooks, you can connect Tomorro to thousands of applications, automate and streamline your work, and minimise repetitive manual actions.

Before you get started, this page offers advice to help you clarify and structure your needs.

What can you do with webhooks?

Webhooks allow you to process all the data contained in a Tomorro project summary sheet. This makes it possible to connect thousands of third-party applications such as Make, Power Automate, n8n or Zapier (paid) without any technical knowledge.

Here are some of the uses observed among some of our customers:

Messaging & notifications (Slack, Teams, email, etc.) to receive automatic alerts about contract updates
CRM (HubSpot, Pipedrive, etc.) to automatically update opportunities and track the progress of signed contracts
Database (Excel, Sheets, Airtable, etc.) for recording and centralising contract information in real time

🚨 Remember to check the compatibility of your third-party tool with:

How does it work?

To create our automation, we will use Tomorro webhooks as triggers.

The objective is therefore simple:

‘A trigger (webhook) causes an action’.

Tomorro offers five ready-to-use triggers:

A contract has been created
A contract has been deleted
A contract has been fully signed
A contract status has been changed
An automatic reminder has been triggered

`Trigger`	`Action`
Event that initiates automation and starts the flow.	Operation that takes place after the trigger has occurred.
Tomorro triggers: A contract has been created A contract has been deleted A contract has been fully signed A contract status has been changed An automatic reminder has been triggered	Example actions (third-party tool): Update a field in the CRM Automatically create an IT ticket to prepare equipment for the new employee after the contract is signed Send a Slack/Teams alert

Sales use-case example

Problem:

Every time a contract is signed, my team has to manually go into the CRM to update the opportunity and change its status. This leads to oversights and a lack of follow-up.

Solution:

Trigger: A contract is fully signed on Tomorro.
Action: The field associated with the opportunity status in the CRM (HubSpot, Salesforce, Pipedrive, etc.) is automatically updated to ‘customer’.
How: Match Tomorro custom fields with CRM fields.

HR use-case example

Problem:

Once an employment contract has been signed, the HR team must manually send a message to IT and managers to prepare for the new employee's arrival. This can lead to delays or oversights.

Solution:

Trigger: A contract is fully signed on Tomorro.
Action: A message is automatically sent on Slack or Microsoft Teams to notify the HR and IT teams.
How: Configure the automatic message to be sent and the channel to send it to.

Pros and Cons

Advantages:

✅ Low human cost

- Quick and easy setup

- Simplified maintenance once automation is in place

✅ Free version available: Make's Free plan includes 1,000 actions per month.

You can also create automations with PowerAutomate (less flexible) and Zapier (paid).

Disadvantages:

⚠️ Limited functionality compared to the API - Fewer actions possible than with a dedicated API integration - Some complex automations will not be possible.

Define your needs

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

1️⃣ Validate the functional prerequisites

Check the availability of your third-party tool on Make, Power Automate, n8n, Zapier

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 need to be automated? What information needs to be retrieved and sent between platforms?

Check the technical prerequisites: Are there any constraints to anticipate? (Licences, security, etc.)

Ensure access to the necessary tools: Does the team responsible for configuring the automation have the required permissions for the third-party software concerned, Tomorro, Make/Power Automate/n8n/Zapier, 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 locate 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 an action triggered on my third-party software... ...when a trigger occurs on Tomorro.

The information exchanged is the ‘list of custom fields’ from Tomorro to my third-party tool.

Example 1:

I want to send a notification on the Teams channel ‘#HR’ ... ... as soon as the contract has been deleted on Tomorro. No data exchange, just notification

Example 2:

I want to fill in the fields associated with my deal on my CRM ... ... as soon as the contract is fully signed on Tomorro. The information exchanged is the name of the co-contractor, their address and their SIRET number from Tomorro to my CRM.

3️⃣ Identify the data to be exchanged between the tools

Define the data to be transferred

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

Which field(s) in the third-party software correspond to the information retrieved from Tomorro?
Example: If there is a field called ‘Counterparty address’, it must be matched with the equivalent field ‘Service provider address’ in the third-party software to ensure proper synchronisation.

Does the data format of the third-party software match the Tomorro fields
Example: Does the data format of the third-party software match the Tomorro fields?

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

Example:

Name of Tomorro smart field	Type of Tomorro smart field	Smart field name third-party software	Smart field type third-party software	Status
Address of counterparty	Text	Address of supplier	Text	Available
Date of signature	Date	Date of signature	Date	To create (on Tomorro or third-party software)
…

Configuration

1️⃣ Configure and test

Before deploying on a large scale, conduct tests to:

Verify that the automations are functioning correctly
Adjust settings and data formats if necessary
Gather user feedback to refine the integration

💡 It is not necessary to perform tests in a test environment (sandbox). The creation of dummy contracts or sending for signature can be done from the Tomorro production account.

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

2️⃣ Go live

If a test template has been created, remember to modify your configuration by selecting the desired template. Once integration is in place:

Regularly monitor workflows to detect any malfunctions.
Update integrations according to changes in connected tools or internal processes (be careful with changes to Tomorro template settings).
Train users on new automations to ensure optimal adoption.