Make (formerly Integromat) is an application designed to help you log in your different tools to each other so you can automatically perform certain actions from one tool to another according to your needs.
Here are some integration examples you might consider:
Automate the creation of a candidate, a company, a contact, or an opportunity when a form of your choice is filled out, or after a questionnaire response
Create an action in BoondManager whenever an event is added to your calendar
Create an action in BoondManager whenever an email is received at an email address
Create a resource in BoondManager whenever a candidate in your ATS is marked as recruited
Automatically update the states of your invoices if you have a bank reconciliation tool (accounting tool or other, etc...)
Post a message in a Slack channel for every opportunity, candidate, project creation, ...
Post a message in a Teams channel every time an opportunity is won
Add a candidate/contact to your newsletter every time a candidate/contact is created
Update a contact/candidate in BoondManager every time they unsubscribe from our newsletter
etc...
We will present some examples of these integrations here to help you get familiar with the possibilities offered.
Check your permissions!
To use Make integrations with BoondManager you will need to log in via Basic authentication. For this, you must enable the permission found in the configuration of your card > "Intranet" tab > field "Allow API Rest calls via BasicAuth authentication".
Don't forget to enable it, because if you don't, you'll get an error message preventing you from proceeding.
If you have access to several interfaces, this permission will only be valid for the account where you activated it.
The summary of interfaces where this configuration is enabled can be found on the My Account > API Section page
⠀
What is a Scenario? What is it used for?
Scenario Definition
An initial trigger allows the scenario to be automatically executed when the corresponding rule is met (e.g.: submission of a new form, receipt of an email from a specific sender, ...). A Scenario is the combination of a trigger and one or more actions. Each trigger and action is made available by a tool or application (BoondManager, Gmail, TypeForm, Zendesk...) and allows interaction with the relevant tool.
The scenario will then perform the actions one by one until the last one is completed.
What does it enable?
Each Make action enables, from input data (last name, first name, email address...), to directly perform an action in the BoondManager application but also, conversely, to retrieve information from BoondManager to send it to another application.
⠀
Using BoondManager webhooks to trigger a scenario
So you can trigger processes when an event occurs in BoondManager, we provide you with a large number of webhooks.
For more information, see the dedicated tutorial to create your first webhook in BoondManager: Activate and use webhooks
Using webhooks with Make
In your Make scenario, choose Webhooks as the first trigger step:
Then select Custom webhook then Add and give a name to your webhook:
Finally, copy-paste the URL address provided by Make into your webhook in BoondManager by following the tutorial mentioned above (Activate and use webhooks):
Be careful with chaining in your Make scenarios
Be careful not to create scenarios based on very frequent webhooks, as you may multiply automated actions. For example, be cautious with the action creation webhook, which can be triggered dozens of times per day depending on your teams' usage. Don't hesitate to use a filter behind this webhook if you want to trigger other steps based on certain conditions (action type, event type, ...)
⠀
Other possible triggers for a scenario
If your scenario relies on an external event to BoondManager, you can also use many other external applications that will trigger your scenario:
Adding a row in a Google Sheets, Excel, or other spreadsheet
Receiving responses to a TypeForm, Google Forms, or even via external webhook
Specific events from your other applications, the possibilities are endless!
⠀
Usage examples provided by Make
Make provides many ready-to-use integrations: See integrations
⠀
Possible Actions after scenario trigger
To automate reading, creation, or updating cards according to your defined processes, you can use sequences of Actions.
Search-type actions
These actions are mainly used to retrieve information from a card in order to chain other actions afterwards (check if the card exists, update it, ...).
Some examples of available searches today:
Actions
Resources and candidates
Companies and CRM Contacts
Opportunities
Creation-type actions
These actions allow you to automate the creation of objects in BoondManager. This lets you automatically supply your BoondManager Database without manually entering certain information collected in your other applications.
Some examples of available creations today:
Actions
Resources and candidates
Companies and CRM Contacts
Opportunities
Update-type actions
These actions allow you to automate updating data in BoondManager. This lets you ensure that your information entered in BoondManager is properly synchronized with your other applications.
Some examples of available updates:
Actions
Resources and candidates
Companies and CRM Contacts
Opportunities
You have at your disposal the actions mentioned above as well as ready-to-use scenario examples. You are therefore free to reuse these scenarios directly or create your own from BoondManager actions and other tools (TypeForm, Gmail…)!
Beware of endless loops!
Be careful not to create "endless" loops. For example, if you create a scenario that triggers when an event is updated and in that same scenario you update the same type of card, you risk having a loop that won't stop. At least, not until your credits expire, and as a result, it may consume your entire Make plan that you paid for.
⠀
Examples of Action usage
Create a candidate in BoondManager for each questionnaire submission
This type of integration will be useful if you are looking for a simple way to make a candidate application form available to your candidates. Such an interface will allow you to work from a questionnaire (Typeform, others) and import into BoondManager all the information entered by the candidate.
Create an opportunity in BoondManager for each questionnaire submission
Exactly the same as the point explained above but this time with the creation of an opportunity (and potentially the associated company/CRM contact card if it doesn't already exist) for each questionnaire submission.
And many other possible variations
You could, for example, use questionnaires and the actions made available to:
Update cards by choosing yourself the mandatory fields
Create formatted actions with the answers obtained from a questionnaire
Collect documents and automatically attach them to the correct cards