Skip to main content
Training avatar
Written by Training
Updated over a week ago

This feature is only available for the following plans:




Click here for more information on our plans.

Click on any of the following links to go to the sections within this article.

In today’s world, sales teams are using more and more applications to manage each stage of the business cycle, such as email marketing tools, survey platforms, and billing systems, to name a few. And in most cases, the data generated by these applications need to be transferred to their CRM through complex and manual processes, making this operation a difficult task to perform.

For this reason, the integration of ForceManager and Make has been designed to transform these processes, making them easier and more efficient to implement, by linking an infinity of applications to automate the creation and updating of new contacts, companies, opportunities, orders, etc.


1. What is Make?

Make, previously Integromat, facilitates the construction of workflows by connecting diverse applications, seamlessly creating automations to resolve complex problems, without needing the use of code.

Main characteristics of the Make integration


Free Access: Using the free version of Make, you can take advantage of all the benefits of the integration with ForceManager.


User-friendly and intuitive interface: The application allows you to drag and drop applications to connect them together, easily building workflows called "Scenarios".


Infinite workflows: This integration offers an infinite amount of possibilities, allowing you to connect ForceManager to over a thousand other applications.


Access data in real time:When creating a Scenario, you can access its execution in real time to ensure that it works correctly.


Accelerates implementation and reduces by cutting down the time and effort spent in building workflows. For example, it discards the need to pre-configure a server or develop code.


Facilitates collaboration: Make offers the option to invite other team members and assign distinct roles for the creation of workflows.

2. Start using the ForceManager and Make integration

To start enjoying all the benefits of this integration, create a free account using the following link: Once you’ve created an an account, proceed to the log in page.

Nota: If you wish to perform an advanced integration, or should you have any questions regarding the process of building workflows, we recommend you contact your IT Team to facilitate the implementation.

Furthermore, you can reach out to our Technical Team at for any additional support you may require. (Please keep in mind that this service bears an additional cost.)

3. Create your first scenario of ForceManager in Make

There are four steps to create your first scenario:

  1. Choose the applications you wish to use, taking into account the goal of automation.

  2. Build out your scenario.

  3. Run a test to ensure it works correctly.

  4. Finally, activate the scenario.

In the following video, we detail every step through a specific use case. In this example, the objective is to automatically register new leads in ForceManager each time someone responds to a survey on Typeform.

4. Available modules of ForceManager in Make

In the following list, you’ll find all the ForceManager modules that allow you to build workflows to automate the tasks of your team. These are divided into the sections corresponding to the ForceManager menus:

1. Accounts: The Accounts modules allow you to create, update, and locate a specific account. You can also view when a new account has been created or updated.


2. Contacts: These modules allow you to create, update, and locate specific contacts. You can also view when a new contact has been created or updated.


3. Opportunities: These modules allow you to create, update, and locate specific opportunities. You can also view when a new opportunity has been created or updated.


4. Activities: These modules allow you to create, update, and view specific activities.


5. Users: The Users modules allow you to retrieve a user’s information through their ID. Also, using the module called "List Users", you have the ability to extract a specific list of users.


6. Calendar: The Calendar modules allow you to create and update specific activities related to the calendar (meetings, tasks, etc.). You can also view when an activity has been created or updated in the calendar.


7. Sales orders: The Sales Orders modules allow you to create and update specific orders, and view when a new order has been created or updated.


8. Entities: These modules allow you to create, update, and locate specific entities.


9. Other: In this section you’ll find the "List" modules, which are key to returning data from the most frequent list of values.

"Make an API call", is a module that refers to any entity or action related to ForceManager’s API. This functionality is useful for cases where the standard module does not exist. For example, when you’re looking to "create or edit products."

For these specific cases, we recommend you to consult the documentation on ForceManager’s API.


5. What menus are accessible when entering Make?

In the following section, we showcase the essential menus that compose the application and their functions.


When you log in to your account, you will find the main menu on the left of the application. From this menu, you can access the different sections detailed below.

1. Organization:

This is the main dashboard of the application. From here, you’ll be able to see the users you’ve invited, the scenarios you’ve created, monitor the operations performed by your team, and update your subscription, etc.

2. Team:

The Team functionality allows you to gain control over scenarios and other data stored within Make. Keep in mind that an organization may contain more than one team, and one user may be a member of any of these teams. In the free version of Make, you only have one team available.

3. Scenarios:

A scenario is the primary functionality for building any automation in Make. A scenario consists of a series of modules that indicate how data should be transferred and transformed between applications and services.

4. Modules:

Make distinguishes 5 types of modules: Actions, Searches, Triggers, Aggregators, and Iterators. The latter two are used for the creation of advanced scenarios. In the following section, we describe what each of these modules are used for.

  • Actions: This is the most common type of module. Actions are responsible for returning a data bundle and sending it to the next module for processing

    • Example: "Creates" a a new order in ForceManager, and return a notification for processing in the next module.

  • Searches: A search-type module can return zero, one or more data bundles, which will be sent to the next module for processing

    • Example: Make a "List" of new subscribers from an audience in MailChimp, and return this data for processing in the next module.

  • Triggers: This type of module generates bundles when a change has occurred within the selected service or application. This change can be the creation, deletion, or updating of records. Make distinguishes between two types of triggers:

    • Poll triggers: These are designed to periodically poll if a change has occurred within the selected application. You can schedule these to run at intervals of time (every 15 minutes, every hour, daily, weekly, etc.)

    • Instant triggers: These detect the change instantly and you can identify them by having the "Instant"


      label next to the module name.

    • Example: Instantly "Watch" the new responses from a Typeform survey, and return this data for processing in the next module.

  • Aggregators:These are modules that accumulate multiple data bundles into one. Each aggregator returns only one bundle which is then passed to the next module for processing.

    • Example: "Aggregate" multiple strings of a CSV file in a single row.

  • Iterators: These modules divide arrays into multiple separate bundles. Each iterator returns one or more bundles that are then passed to the next module for processing.

    • Example: "Retrieve" attachments from an email and divide them into separate bundles.

Consult this article on Make Modules to learn more about the types of modules available.

5. Templates:

In this section, you’ll find predefined templates that allow you to create your scenarios in an easier way. To learn more, go to the Template Gallery in Make.

6. Connections:

In this section, you can consult and manage the connections you’ve established. You can also obtain the IP address of Make to connect the application with other servers. Refer to the Make Connections article to learn more about this functionality.

7. Webhooks:

Webhooks allow you to exchange data between two systems, in this case, using webhooks will make it easier to send data to Make from HTTP. To learn more about this functionality, see the article on Webhooks in Make.

8. Keys:

Through this section, you have the ability to manage your public and private keys. For example, this is used in the Encryptor application to encrypt or decrypt specific messages. Go to the article Keys in Make to learn more about this functionality in detail.

9. Devices:

If you’re looking to use the Make app on your Apple iOS or Android device, you can do it from the "Devices" section, following the instructions described in the article Add your devices to Make.

10. Data stores:

A data store is similar to a database, and is responsible for collecting data from each scenario. In this section, you can view and manage all data stores.

Did this answer your question?