Instagram profile posts

What it does

One Instagram profile's grid, scrolled and filed as rows: permalink, caption and thumbnail. Uses the session already in this profile, so it runs on this machine only.

It runs against one profile, through that profile's own proxy and with its own cookies — so the pages load the way that account's owner would see them. It navigates, so give it a profile whose session you are happy to have in use.

The 16 steps

The real tree, read out of the pack the launcher ships. Indentation is nesting: the steps under a loop run once per row, and the ones under a branch run only when the condition above them holds. Every {{…}} is a value filled in at run time — from the row being walked, from a setting on the run, or from the profile itself.

Each of those is one of the step types on the automation reference, with the same fields the editor shows and the same fields an agent is handed over the local API.

The tables it uses

These load with the recipe. A dataset is a typed table your workspace owns — the columns are named and typed up front so the steps can address them, and every one of them is yours to rename, extend or fill from a file afterwards.

Re-running updates the row it already wrote rather than adding a second one. That is what the match column in the save step is for, and it is the difference between a status check and a table that doubles in size every pass.

What it asks you for

Settings are filled in when the run starts, and every profile can hold its own values — which is how one workflow serves a whole folder of accounts.

account

Account · text · required

The handle, with or without the @. Not a URL — the run builds it, so a link copied out of the app with its tracking parameters still works.

max_items

Stop after · number

How many posts to keep. The scroll stops as soon as it has this many, so a small number is a short run rather than a truncated one.

Loading it

In the launcher, open Automations, choose Load a starter pack, and pick Social. Untick anything you do not want. The tables land first, then the workflows, then a project called Social that links them together.

What arrives is an ordinary automation row. Open it in the editor, change a step, rename it, delete it — nothing in the app treats it as special afterwards, and loading the pack a second time makes a fresh copy rather than overwriting the one you edited. Tables are the opposite: an existing table of the same name is reused and keeps its rows.