Published on Thu Jan 15 2026 00:00:00 GMT+0000 (Coordinated Universal Time) by Miguel Gonzalez Herrera

🤖 Tutorial: Automate the Search for Traffic Notifications in the BOE with Make.com and Apify

Managing traffic notifications for clients with multiple vehicles or entire fleets can be challenging. Manually checking the Official Notice Board (Tablón Edictal Único, TEU) every day is tedious and error-prone, with the risk of missing the deadlines to appeal a fine.

In this guide, we will show you how to create an automated system that handles this monitoring for you. You will learn how to set up a workflow that searches for traffic notifications daily by ID number or licence plate in the BOE, and sends you an immediate email alert.

We will use two powerful tools:

• Apify: To run an actor that extracts data from the BOE.
• Make.com: To orchestrate the workflow, read data from a Google Spreadsheet, and send email notifications.

By the end, you will have a system that automatically notifies you if a relevant announcement is published, letting you appeal within the deadline and avoid problems for your clients.

Step 1: Prerequisites

Before starting, make sure you have:

1. An Apify account: If you do not have one yet, sign up using the button below. The free plan is sufficient, as it provides monthly usage credits to run the actor.
   

   Create a free Apify account
   

2. A Make.com account: If you do not have one yet, sign up using the button below. You can use it for free with the 1,000 operations/month included in the Free plan.
   

   Create a free Make.com account
   

Step 2: Set Up the Scenario in Make.com

To make things easier, you can clone a pre-configured scenario from the following link:

https://eu1.make.com/public/shared-scenario/KiP0NS7Wtx1/trafico-notificaciones

The complete workflow looks like this:

Below is the configuration for each part.

1. Add the email where you want to receive notifications. Connect Google Drive and Google Sheets

Add the email address where you want to receive notifications.

The next step is to connect your Google Drive account to read the search terms from a Google Spreadsheet.

1. Create a Google Spreadsheet in your Google Drive with a column for the search terms.

2. In the Google Drive module in Make, connect your account and select the file and sheet you just created.

2. Connect Apify

Now we will connect Apify to search for notifications.

1. Connect Apify: Select the Apify module (Run an Actor) and connect your account using the recommended option.

2. Run an Actor: After connecting, the actor we are going to use will be pre-loaded. Save it and move to the next step.

3. Get the results (Get dataset items): Select the next Apify module to retrieve the results (the “dataset”) from the actor run.

3. Connect Gmail

Finally, if results are found, we will send an email.

1. Select the Gmail module and connect your account.

2. You will see the email you set at the beginning of the workflow in the your_email variable. Notifications will arrive there whenever a BOE announcement contains any of your search terms.

Step 3: How to Test the Workflow in Make

1. Find a real notification: Go to the latest BOE announcements for Traffic notifications and find one published today.

2. Copy a search term: Copy an ID number or a vehicle licence plate from a notification published that day.

3. Add it to your Google Spreadsheet: Paste the term into your Google Sheets file in the appropriate column. You can add multiple search terms, one per row.

4. Run the workflow: In Make.com, click “Run once”.

If the term appears in any notification that day, you will receive an email at the address you configured.

Step 4: Schedule the Workflow

The last step is to automate the execution so you do not have to do it manually.

1. In Make.com, activate the scenario.
2. Set up the schedule to run every day at a specific time — for example, at 9:00 AM.

That is it! From now on, Make.com will become your personal TEU watchdog, alerting you to any relevant traffic fine so you can act quickly.

Written by Miguel Gonzalez Herrera