Make (formerly Integromat) is an application designed to help you connect your various tools together in order to automatically perform certain actions from one tool to another based on your needs.
Here are some integration examples you might consider:
Automate the creation of a candidate, company, contact, or even a requirement when a form of your choice is filled out, or following a response to a questionnaire
Create an action in BoondManager as soon as an event is added to your calendar
Create an action in BoondManager as soon as an email is received at a specific email address
Create a resource in BoondManager as soon as a candidate in your ATS is marked as hired
Automatically update the status of your invoices if you have a bank reconciliation tool (accounting software or other, etc...)
Post a message in a Slack channel each time a requirement, candidate, project, etc. is created
Post a message in a Teams channel each time a requirement is won
Add a candidate/contact to your newsletter every time a candidate/contact is created
Update a contact/candidate in BoondManager each time they unsubscribe from our newsletter
etc...
We will present some examples of these integrations to help you get familiar with the possibilities offered.
Check Your Permissions!
To use Make integrations with BoondManager, you will need to connect via Basic authentication. To do this, you must enable the permission found in your profile settings >"Intranet" tab > "Allow Rest API call from BasicAuth authentication".
Don't forget to do that because if you don't, you won't be able to use any of our triggers/actions and you'll get a 401 error.
If you have access to mutiple customers, this authorization is only active for the account you allowed it for.
The list of all customers you allowed Basic Auth for can be found at My Account > API Section
⠀
What is a Scenario? What is it for?
Definition of a Scenario
An initial trigger allows you to automatically execute the scenario when the corresponding rule is met (e.g., submission of a new form, receipt of an email from a specific sender, etc.). A Scenario is the combination of a trigger and one or more actions. Each trigger and action is provided by a tool or application (BoondManager, Gmail, TypeForm, Zendesk, etc.) and allows you to interact 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 you, based on input data (first name, last name, email address, etc.), 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: Enable 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 your webhook a name:
Finally, copy and paste the URL address provided by Make into your webhook in BoondManager by following the tutorial mentioned above (Enable and use webhooks):
Be Careful with Chaining in Your Make Scenarios
Be careful not to create scenarios based on very frequent webhooks, as you risk multiplying automated actions. For example, be cautious with the action creation webhook, which can be triggered dozens of times a day depending on your team’s usage. Don’t hesitate to use a filter after this webhook if you want to trigger other steps based on certain conditions (type of action, type of event, etc.)
⠀
Other Possible Triggers for a Scenario
If your scenario is based 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 an 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, creating, or updating records according to your defined processes, you can use sequences of Actions.
Search-Type Actions
These actions are mainly used to retrieve information from a record in order to chain other actions afterwards (check if the record exists, update it, etc.).
Some examples of available searches as of today:
Actions
Resources and candidates
Companies and CRM Contacts
Requirements
Creation-Type Actions
These actions allow you to automate the creation of objects in BoondManager. This notably allows you to automatically populate your BoondManager Database without having to manually enter certain information collected in your other applications.
Some examples of available creations as of today:
Actions
Resources and candidates
Companies and CRM Contacts
Requirements
Update-Type Actions
These actions allow you to automate the updating of data in BoondManager. This notably allows you to 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
Requirements
You have the above-mentioned actions at your disposal as well as ready-to-use scenario examples. You are therefore free to directly reuse these scenarios or create your own from BoondManager actions and other tools (TypeForm, Gmail, etc.)!
Beware of Infinite Loops!
Be careful not to create "endless" loops. For example, if you create a scenario that is triggered when an event is updated and in that same scenario you update the same type of record, you risk having a loop that will not stop. At least, not until you have used up your credits, and as a result, this can consume your entire Make subscription.
⠀
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 provide a candidate application form 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 a requirement in BoondManager for each questionnaire submission
Exactly the same as the point explained above, but this time with the creation of a requirement (and potentially the associated company/CRM contact record if it does not already exist) for each questionnaire submission.
And many other possible variations
You could, for example, use questionnaires and the available actions to:
Update records by selecting the mandatory fields yourself
Create formatted actions with the responses obtained from a questionnaire
Collect documents and automatically attach them to the correct records