Need
Would you like to create automations and match data between Salesforce and Tomorro?
This quick memo is for you, to get you ready to set up the interface.
Thanks to our native Salesforce integration, you can connect Tomorro to automate and streamline your work.
Before you get started, you'll find our tips on this page 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 you do with the Tomorro widget integrated into Salesforce?
The Salesforce x Tomorro connection enables you to exchange all data present on Tomorro projects, but also to receive all types of data from Salesforce.
This enables your Salesforce operational teams to streamline and automate their actions, in two ways:
Automatically
Set up from an administrator account, the native Salesforce x Tomorro integration enables you to create a contract from a template on Tomorro automatically as soon as a Salesforce field reaches a predefined stage. The contract will be created in "draft" or "signed" status, depending on the predefined parameters.
Manually
Directly inserted into the Salesforce "opportunities" object, the Tomorro widget allows, once set up, to communicate and exchange data between the two software programs whenever you want to :
Start a negotiation
Import a signed document
How does automatic connection work ?
How does automatic connection work ?
Tomorro's native integration offers 2 ready-to-use automatic actions from Salesforce:
Start a negotiation
Import a signed document
🚨 | 💪 |
Event that initiates automation and starts the flow. | Operation that takes place after the trigger has occurred. |
As soon as a field in a salesforce object reaches a certain predefined stage. | Tomorro actions : • Start a negociation • Import an already signed document |
Option: retrieve PDF files stored in Salesforce from Tomorro.
💡 Example of a "start a negotiation" use case.
💡 Example of a "start a negotiation" use case.
Problem:
I want to create a contract from my Salesforce opportunity in order to retrieve the data that corresponds to it to avoid duplicates and errors.
Solution:
🚨 Trigger: As soon as my opportunity reaches the "closed won" stage.
💪 Action: A new project is created in Tomorro with the status of "under negotiation" from a predefined template and thanks to the data previously mapped between the two software packages.
❓ How: Match Salesforce fields with Tomorro cocontracting fields.
💡 Example use case "Import a signed document".
💡 Example use case "Import a signed document".
Problem:
I want to keep track of my signed documents in both Salesforce and Tomorro.
Solution:
🚨 Trigger: As soon as my opportunity reaches the "closed won" stage.
💪 Action: A new project is created in Tomorro at "signed" status from a predefined template and thanks to data previously mapped between the two software packages. PDF files stored on Salesforce move up as attachments in the Tomorro project.
❓ How: Match Salesforce fields with Tomorro co-contracting fields.
How does the manual connection work?
How does the manual connection work?
Through the widget, the native Tomorro integration offers 2 ready-to-use manual actions from Salesforce:
Start a negotiation
Import a signed document
🚨 | 💪 |
Event that initiates automation and starts the flow. | Operation that takes place after the trigger has taken place. |
Triggers from Salesforce (see green box image above) | Tomorro actions : • Start a negociation • Import an already signed document |
💡 Example of a "start a negotiation" use case.
💡 Example of a "start a negotiation" use case.
Problem:
I want to create a contract from my Salesforce opportunity in order to retrieve the data that corresponds to it to avoid duplicates and errors.
Solution:
🚨 Trigger: From the Tomorro widget in Salesforce, selecting "start a negotiation"
💪 Action: A new project is created in Tomorro with the status of "in negotiation" from a predefined template and thanks to data previously mapped between the two software packages.
❓ How: Match Salesforce fields with Tomorro cocontracting fields.
💡 Example use case "Import a signed document".
💡 Example use case "Import a signed document".
Problem:
I want to keep track of my signed documents in both Salesforce and Tomorro.
Solution:
🚨 Trigger:From the Tomorro widget in Salesforce, by selecting "import a signed document"
💪 Action: A new project is created in Tomorro with "signed" status from a predefined template and thanks to data previously mapped between the two software packages.
❓ How: Match Salesforce fields with Tomorro co-contracting fields.
🔦 Define your needs
To ensure a smooth implementation of the integration between the two platforms, it's essential to frame the data flows upstream. Before getting started, make sure you have met the following prerequisites:
1️⃣ Validate functional prerequisites
1️⃣ Validate functional prerequisites
Prerequisites | |
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 automation parameters have the required permissions for the third-party software concerned, Tomorro, etc.? |
If automatic generation is set up | Which "master" account will create projects on Tomorro? |
2️⃣ Specify your process
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 Salesforce 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 a new project on Tomorro...
... as soon as I use the Tomorro widget on Salesforce
The information exchanged is the "amount" field and the "product(s) sold" list of the "opportunity" object from Salesforce to Tomorro
.
❌ Bad example: "The information needed to complete my Tomorro contract."
✅ Specify instead: The "amount" field and the "product(s) sold" list of the "opportunity" object (specify detail).
The great power of native Tomorro integration is that these steps can be :
Manual or automatic
Multiple
Cascading
Bidirectional
Originating from multiple Salesforce objects
3️⃣ Identify data to be exchanged between tools
3️⃣ Identify data to be exchanged between tools
🔄 Define the data to be transmitted
🔄 Define the data to be transmitted
It's crucial to identify what data is to be exchanged between your third-party software and Tomorro. A good specification enables :
✅ Optimum alignment between systems
✅ Avoid double data entry
🧑🔧 Tomorro configuration prerequisites: questions to ask yourself
Question | Example |
Which Tomorro field(s) does the information retrieved from Salesforce correspond to (and vice versa)? | Example: If a "Provider's address" field is present, it must be matched with the equivalent "Co-contractor's address" field in Tomorro to ensure correct synchronization. |
Does the data format of the third-party software match the Tomorro fields (and vice versa)? | Does the data format of the third-party software match the Tomorro fields? |
Which account should perform the action on Tomorro? Which account should perform the action on Salesforce? | 💡 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, to check the correspondence of fields and their format.
Example :
Salesforce field name | Corresponding Salesforce object | Third-party software field format | Tomorro field name | Tomorro field format | Status |
Address of service provider | Account | Text | Contractor address | Text | Available |
Amount | Opportunity | Number | Amount | Number | Available |
Product(s) sold | Opportunity | Selector | Product(s) sold | Selector | Available |
... |
🔧 Configuration
1️⃣ Configure and test
1️⃣ Configure and test
For this kind of integration, it may be necessary for you and your IT team to carry out testing on sandbox environments.
On the Tomorro side, we can provide you with the information you need to make this connection, but we suggest you get in touch with your third-party software to see if they can do the same.
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.
2️⃣ Go live
2️⃣ Go live
If the tests were carried out on a sandbox environment, you'll need to reconfigure the exchange on the correct environment. 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.
More