Help: Extract first image from Weebly RSS → Baserow via Make.com

[DEKO]

What is your goal?

I’m trying to pull specific pieces of information from my Weebly blog using its RSS feed and automatically insert that data into a Baserow table. The end goal is to display these blog posts inside my Baserow App Builder setup, so the entries update themselves without manual copying or rewriting.

What is the problem?

Right now, Baserow is receiving completely blank rows from my Make.com scenario. Even though the RSS module successfully detects new Weebly blog posts, none of the fields I map are actually showing up in the final Baserow record.

A big part of the issue is how Weebly formats its RSS feed. The “image” field in the feed is always empty, and every bit of content — text, formatting, and all images — is shoved into one giant HTML blob inside the description field. That means the first image I need is buried somewhere inside that HTML.

What have you tried so far?

I tried adding a Text Parser module in Make.com to extract the first src from the description, but I can’t get the parser to run correctly. Without that working, I can’t isolate the image URL or send it to Baserow. So at the moment, the scenario runs, but the row it creates in Baserow is blank.

I’m stuck at the Text Parser step. I’m not sure what I’m supposed to do with this pop-up window. Normally when I run the scenario, I get a bundle I can use to move on to the next module, but this time nothing is coming through, so I can’t continue.

Screenshots: scenario setup, module configuration, errors

I get a bundle from the Watch RSS feed item.

No idea what I am supposed to do now.

This is how my baserow module is set up. It creates a row when it runs, but its blank.

[samliew]

Welcome to the Make community!

You cannot individually run a single module if you don’t have example input data values for each required field, which you must input into the dialog box when you manually run a single module. This is because when you run a module directly, the mapped variables in the fields are null (do not contain any value).

Instead, try running the full scenario by clicking the “Run Once” button:

Polling Triggers & Empty “Check Runs”

Also, the “Watch RSS feed items” module is a POLLING trigger, and not an INSTANT (Webhook) trigger.

If you don’t see any bundles from the trigger module and operations on the rest of the modules, it means there are no new responses (empty output bundle) when the scenario ran to check for new items. This is called a “Check run”.

There are two main types of triggers, Polling (scheduled), and Instant (webhooks). Polling triggers can only run on a schedule. Instant triggers can be run as soon as data is received by the webhook.

• Polling means Make checks external service for changes (pull changes to Make).
• Webhook (instant) triggers means external service calls Make when there are new changes (push changes to Make).

The module you are using does not push changes — it’s basically a API request that Make has to occasionally “call” to fetch the latest changes/items.

To find out more on the different types of Trigger modules, see refer to Types of Modules and Webhooks sections of the Make Help Centre.

If you want your scenario to only run when there is new data (and not on a schedule or timed interval), see if your app has an “Instant” or “Webhook” trigger in Make. If not, check if the third-party service has a feature that can send out a webhook when content is created/updated - and then you can point it to a “Custom Webhook” trigger in your scenario.

If you want to re-run your scenario on older data,

Polling Triggers: Epoch Panel & Selecting Older Data

Go to the Epoch Panel, by right-clicking on the trigger module (polling triggers only), and select “Choose where to start” from the list of options in the context menu.

If you select “From now on”, the next time the scenario runs it will only return new data (or nothing if there is no new data).

You can also select other old data to re-run your scenario with next using the “Choose manually” option. This will then show you a list of previous historical items you can select to process the next time the scenario is triggered.

For more information, see

• Types of Triggers
• Selecting the First Bundle

You can learn more in these Make Academy units:

Expanding my first scenario

• Adding a Router
• Adding a Filter
• More options with Filters
• Overview of scheduling
• Run once

Modules, scheduling and bundles

• Blueprints
• Different types of modules - search
• Different types of modules - action
• Introduction to triggers
• Scheduling your scenario
• Introduction to bundles

Hope this helps! If you are still having trouble, please provide more details.

— @samliew