Need
You want to exchange data between Tomorro and a third-party software package, but you don't know where to start?
This quick memo is for you
Objective
Why is this useful?
Better define your needs to minimize subsequent adjustments.
Facilitate technical implementation by providing a clear vision of the desired process.
To make sure that automation corresponds to your day-to-day use.
Why automate?
Save time: eliminate repetitive tasks.
Standardized processes: by standardizing your working methods.
Reduce errors: reduce inconsistencies in your data.
Centralized data: for a better flow of information.
🔦 Définition of requirements
⚙️ Définition of operationnal requirements
Before configuring an automation, it's essential to clearly define your need. To do this, focus on the end goal: What is the purpose of my automation?
Also, make sure 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
I want action in platform1...
... as long as trigger in platform2
Information exchanged is list from platform2 to platform1
Example:
I want to create a contract in Tomorro... ... as soon as the "deal status" field changes from "prospect" to "customer" in my CRM
The information exchanged is the contracting party's name, address and SIRET number from CRM to Tomorro.
If you're at a loss and can't clearly define your needs, here's a decision tree to guide you towards more complete documentation.
⽊ Decision tree
What kind of data exchange are you planning?
🔧 Configuration
1️⃣ Configure and test
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
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.