Scenario Stops at Set Variable module instead of going ahead

How To
, ,
1

I’m trying to build a scenario in Make to automate LinkedIn posts using data from Google Sheets. My setup is as follows:

Google Sheet -

  • Column A: Day 1, Day 2, etc. (Day 1 = 21st Aug)

  • Column B: Idea

  • Column C: GPT-generated input

  • Column D: Status column (generate post, ready for review, post content, content posted)

The flow works fine for generating and reviewing content. I’ve already prepared content till Day 30 and marked “Post Content” in Column D.

However, I’m facing an issue when trying to post automatically day-wise:

  • I’m using a Set Variable tool with this formula:
    "Day " & (1 + dateDiff(now; parseDate("2025-08-21"; "YYYY-MM-DD"); "days"))

  • On Day 2, instead of picking only Day 2’s row, the scenario stops at the Set Variable tool and tries to process all rows marked “Post Content.”

I want the scenario to pick only the current day’s row and post that to LinkedIn automatically, without manual intervention.

Question:
:backhand_index_pointing_right: How can I configure the scenario so that it runs day-wise (1 post per day), without stopping at the variable step or running all “Post Content” rows together?

Any guidance would be highly appreciated!

Thanks in advance :folded_hands:

Below is the screenshot of my scenario. The filters on router is based on column D to ensure if content is already generated it will be posted. And another snapshot of variable filter.

image
image1497×577 61.2 KB

image
image807×530 45 KB

image
image670×406 33.9 KB

3

Hi @D_19

Why don’t you just get rid of the “Day “ in column A and make it a number (1, 2, 3…)?

You’ll then use the same formula straight on the Search rows filter, returning only the current day, removing the Set variable and the filter. (You could even keep “Day “ but that would force a text comparison, instead of a numerical one).

This way you don’t need to return all lines every day, set a variable for each one and filter them based on value. This would even save lots of operations. Imagine after one year, fetching 400 rows and building 400 variables everyday, just to trash 399 instantly?

@damato

1 Like
4

hey Damato. Thank you for replying. This was really helpful. I actually implemented the scenario in same way. :slight_smile:

2 Likes