🤖 This article was translated by AI.
🚨 Note
This feature is available for clients subscribed to an Advanced, Enterprise, or Business plan.
If you want to learn more about these plans, you can visit our website and contact us at [email protected] to discuss with our teams.
As soon as an event occurs in Boond, the actions you have defined are executed automatically. Less manual entry, always up-to-date data, no technical skills required.
Understanding an Automation: Triggers and Actions
An automation combines a trigger (the event that starts it) and one or more actions (what Boond executes next), which you visually assemble in an editor. All selections are made from lists, with the stages, steps, and labels from your environment: no technical input is needed.
Today, automations cover 12 modules: Candidates, Resources, Contacts, Companies, Opportunities, Positionings, Projects, Deliveries, Products, Purchases, Supplier invoices, and Actions.
The 3 Triggers
Event on a card | Triggered when a card is created, updated, or deleted in the module of your choice. You check the event(s) you are interested in: Creation, Update, Delete. |
State change | Triggered when a card enters the state you have chosen. You can optionally specify the starting state: the automation will only trigger for that specific transition. Note: a card created directly in this state does not trigger anything: a real change is required. |
Scheduling | Triggers automatically, at the frequency you define: daily, weekly, or monthly, at the chosen time. Since no card is the origin of the trigger, this trigger is combined with "Search cards" to target the cards to process. |
The 4 Actions
Retrieve a card | Opens a card so that subsequent actions can use it: either the card that triggered the automation, or a card linked to it: its company, its parent card, its manager… You choose from a list; only cards actually accessible at this step are offered, and if there is only one possible choice, it is already filled in. |
Search cards | Finds all cards in a module that match your criteria. You define them as in your usual searches: with the same filters window, or by reusing a saved search. It is impossible to validate a search with no criteria: you will never process an entire module by mistake. Actions placed on the output "For each card" are executed on each card found, one by one; those placed on "At the end" are executed only once, when everything is finished. |
Update a card | Edits one or more fields of the selected card. You add a line for each field to edit, and the input adapts: a list of values for a state, a calendar for a date, Yes / No for a checkbox. The values offered are always those from your environment. |
Condition | A checkpoint with two outputs, Yes and No. You choose a field, a comparison (is equal to, contains, is greater than, is empty…), and a value: the next steps are executed on the Yes branch only if the card meets the criterion. An advanced, optional mode allows expert users to write their own expressions. |
The power comes from the combination: a trigger followed by chained actions, including bulk (a search applies the sequence to each card found) and across linked cards, to act beyond the card that triggered the automation.
Configuring an Automation
Go to Administration → Customize
Click Automations
Click the + button
Name your automation (click the title "My automation") and choose your trigger: its panel opens to define the card type and, depending on the trigger, the events, destination state, or frequency
Add your actions in sequence by clicking the "+": each action opens upon addition to be configured
Save
Publish: your automation is active and will trigger as soon as the event occurs
Test before publishing
The Test button temporarily publishes your automation for validation. Then perform the action expected by the trigger: execution unfolds before your eyes, step by step, on the diagram.
Important
Automations actually modify your data. For your tests, use test cards rather than production cards.
Publish, Pause
A published automation is active: it triggers at each corresponding event. You can pause it at any time: it is retained with all its configuration and history, and will not trigger again until reactivated. Drafts and paused automations do not count toward your quota.
Execution Rights
Each automation runs with the rights of the person who created it: it will never be able to view or modify data beyond what its creator can do themselves. If rights are missing on a card, the relevant execution fails, visible in the monitoring.
Monitor Executions
Each automation has an Executions tab that logs all its triggers, from most recent to oldest: status (Success or Failure), start date, end date, duration, and responsible: the person whose action triggered the execution, or "Scheduled".
By selecting an execution, you view its path directly on the diagram: successful steps in green, failed step in red. In case of failure, the detail automatically opens on the relevant step: you can read the clear reason and the affected card. You always know what was done, on which cards, and why.
Quotas and Usage
Active Automations
The number of active automations (published and not paused) depends on your plan. A counter at the top of the list constantly shows you this. At maximum, publishing an additional automation is blocked: pause one to activate a new one. You freely choose which are active, and you can prepare as many drafts as you want.
Monthly Usage
A monthly usage gauge complements this counter: it reflects the volume of actions executed by your automations during the current month, within normal usage, and resets on the 1st of each month.
Use cases: Build Your First Automations
Important
The states, steps, and types used below are examples: adapt each example with your own values, the structure remains the same.
Use case 1 — Your dormant candidates wake up automatically
Each week, your talent pool is automatically requalified: no more forgotten profiles.
Scheduling: every week, Monday at 8:00 AM
Search cards: Candidates module, your talent pool criteria, built in the filters modal or imported from an existing saved search
On the "For each card" output: Update a card → State: To be contacted
→ 30 cards or 500: each matching candidate is requalified, one by one, every Monday morning. This is the standard pattern for any bulk processing: it works identically to requalify leads or archive old opportunities.
Use case 2 — The step follows the interview, not the other way around
Your recruiters create the Interview action; the candidate card advances automatically.
Event on a card: Action type, Creation event
Retrieve a card: the Trigger card (the created action)
Condition: the action type is equal to Interview: a call or email does not trigger anything
Retrieve a card: the Parent card (the candidate)
Update a card → Step: the corresponding step in your process
→ Your pipeline reflects the real pace of interviews, without re-entry.
Use case 3 — A won opportunity, an up-to-date CRM
The deal is signed: the contact and company instantly become Client.
State change: Opportunity type, destination state Won
Retrieve a card: the Trigger card (the opportunity)
Update a card: the linked Contact → State: Client
Update a card: the linked Company → Type: Client
→ No more "prospect" companies with three billed projects.
Use case 4 — A first action qualifies your contact
Your prospecting lists show "New" for contacts already called three times.
Event on a card: Action type, Creation event
Retrieve a card: the trigger action
Retrieve a card: the Parent card (the contact)
Condition: the contact state is equal to New: only contacts never worked are concerned
Update a card → State: Engaged
→ As soon as the first interaction is recorded on a new contact, their card advances. An already qualified contact is never touched again: the Condition guarantees it.
Important
After a Search cards, the card is already available on the "For each card" output: no need to add a Retrieve step. Retrieve is used to load another card than the one in the flow: a linked card.