<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Phil Smith</title>
    <description>The latest articles on DEV Community by Phil Smith (@philyboysmith).</description>
    <link>https://dev.to/philyboysmith</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3586830%2Faa275e0b-3eed-470a-bd46-b81bf104789e.jpeg</url>
      <title>DEV Community: Phil Smith</title>
      <link>https://dev.to/philyboysmith</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/philyboysmith"/>
    <language>en</language>
    <item>
      <title>Instagram posts in Klaviyo/Mailchimp without Zapier tax</title>
      <dc:creator>Phil Smith</dc:creator>
      <pubDate>Tue, 27 Oct 2026 20:11:30 +0000</pubDate>
      <link>https://dev.to/philyboysmith/instagram-posts-in-klaviyomailchimp-without-zapier-tax-2beb</link>
      <guid>https://dev.to/philyboysmith/instagram-posts-in-klaviyomailchimp-without-zapier-tax-2beb</guid>
      <description>&lt;p&gt;You want the latest Instagram posts in a welcome series or a weekly brand email. The “easy” path is usually a Zap: new Instagram post → somehow → Mailchimp / Klaviyo. It works until the task meter spikes, the Zap breaks on a Meta permission change, or someone asks why the images in last month’s send are blank.&lt;/p&gt;

&lt;p&gt;There is a quieter option most email tools already support: a feed URL. Paste it into a native RSS block (Mailchimp) or a web feed (Klaviyo). No Zap. No Make scenario. No third widget whose free tier pauses when a campaign goes semi-viral.&lt;/p&gt;

&lt;p&gt;We built &lt;a href="https://feedframer.com" rel="noopener noreferrer"&gt;Feedframer&lt;/a&gt; for that path — among others. This is the email-shaped write-up: how it works, what it costs next to Zapier, and the trade-offs we will not paper over.&lt;/p&gt;

&lt;h2&gt;
  
  
  The usual stack (and why it feels expensive)
&lt;/h2&gt;

&lt;p&gt;Three common ways people get Instagram into email:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Approach&lt;/th&gt;
&lt;th&gt;What you pay for&lt;/th&gt;
&lt;th&gt;What goes wrong&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Zapier / Make&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Tasks / operations every time a post fires and an email tool is touched&lt;/td&gt;
&lt;td&gt;Metered cost scales with activity; OAuth reconnects; image URLs go stale; multi-step Zaps are another thing to babysit&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;View-capped Instagram widgets&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;A widget UI, then views&lt;/td&gt;
&lt;td&gt;Fine for a site embed; awkward in email; free tiers often &lt;strong&gt;pause the account&lt;/strong&gt; when views run out&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;DIY Graph API → your own RSS&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Engineering time&lt;/td&gt;
&lt;td&gt;Token refresh every ~60 days, media CDN copies, a host for the feed — same on-call as any Instagram integration&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Zapier is not evil. It is a tax on a problem that email platforms already solved for blogs: “give us a feed URL and we will pull it.” Instagram just does not publish a public RSS feed for your account. Someone has to turn posts into a feed (or JSON) that Mailchimp and Klaviyo can read.&lt;/p&gt;

&lt;p&gt;That someone can be you, or a small hosted API.&lt;/p&gt;

&lt;h2&gt;
  
  
  What “native” actually means here
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Mailchimp&lt;/strong&gt; has RSS-to-email automations. You paste an RSS URL, pick daily / weekly / monthly, and Mailchimp only sends when there is something new. Merge tags like &lt;code&gt;*|RSSITEM:CONTENT|*&lt;/code&gt; render the post body.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Klaviyo&lt;/strong&gt; has web feeds. You register a URL once under Settings → Other → Web feeds, then loop over it in any campaign or flow template. Klaviyo prefers &lt;strong&gt;JSON&lt;/strong&gt; over XML for this; more on that below.&lt;/p&gt;

&lt;p&gt;Neither tool needs Zapier for “pull latest posts into this email.” They need a stable HTTPS URL that returns posts in a format they understand.&lt;/p&gt;

&lt;p&gt;Feedframer’s job: connect a &lt;strong&gt;Business or Creator&lt;/strong&gt; Instagram account once, refresh the token on our side, copy media to our CDN, and expose:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;RSS: &lt;code&gt;https://feedframer.com/api/v1/rss?api_key=YOUR_API_KEY&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;JSON: &lt;code&gt;https://feedframer.com/api/v1/me?api_key=YOUR_API_KEY&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Same key. Same posts. Pick the format the email tool wants.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Honest prerequisites:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Personal Instagram accounts lost API access when Basic Display shut down (December 2024). Business or Creator only.&lt;/li&gt;
&lt;li&gt;Free plan: &lt;strong&gt;6 posts&lt;/strong&gt; per account in the feed, &lt;strong&gt;unlimited API calls&lt;/strong&gt;, JSON / GraphQL / RSS, no card required.&lt;/li&gt;
&lt;li&gt;Premium: &lt;strong&gt;$6/month or $60/year&lt;/strong&gt; — more posts (up to 100), hourly Instagram checks instead of daily, responsive image sizes.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;We cap posts, not views. A big send does not pause the feed.&lt;/p&gt;

&lt;h2&gt;
  
  
  Mailchimp: RSS automation in four steps
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;In Feedframer, open &lt;strong&gt;RSS Feed&lt;/strong&gt;, pick the account, copy the URL (it includes the API key — treat it like a password).&lt;/li&gt;
&lt;li&gt;In Mailchimp: &lt;strong&gt;Automations&lt;/strong&gt; → flow templates → &lt;strong&gt;Share blog updates via RSS&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Paste the Feedframer URL, choose how often to send, optionally tick “Resize RSS feed images.”&lt;/li&gt;
&lt;li&gt;In the email body, use something like:
&lt;/li&gt;
&lt;/ol&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;*|RSSITEMS:|*
&lt;span class="nt"&gt;&amp;lt;div&lt;/span&gt; &lt;span class="na"&gt;style=&lt;/span&gt;&lt;span class="s"&gt;"margin: 0 0 32px 0;"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
  *|RSSITEM:CONTENT|*
  &lt;span class="nt"&gt;&amp;lt;p&lt;/span&gt; &lt;span class="na"&gt;style=&lt;/span&gt;&lt;span class="s"&gt;"color: #666666; font-size: 12px;"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;Posted *|RSSITEM:DATE:F j, Y|*&lt;span class="nt"&gt;&amp;lt;/p&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;/div&amp;gt;&lt;/span&gt;
*|END:RSSITEMS|*
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Use &lt;code&gt;*|RSSITEM:CONTENT|*&lt;/code&gt; for the image. Avoid &lt;code&gt;*|RSSITEM:IMAGE|*&lt;/code&gt; — for many video posts that points at an MP4, and email clients will not show it as a picture. Feedframer’s &lt;code&gt;content&lt;/code&gt; already includes a sensible still for videos.&lt;/p&gt;

&lt;p&gt;Mailchimp only fires when the feed has posts it has not sent yet. First send looks back 24 hours / 7 days / 30 days depending on cadence; later sends take everything new since the previous one. Posts need to be in the feed at least a few hours before the send (Mailchimp’s rule, not ours).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Free-plan gotcha:&lt;/strong&gt; we check Instagram &lt;strong&gt;daily&lt;/strong&gt; on Free. If you post and Mailchimp runs before our next check, that post is not in the feed yet. Weekly or monthly automations are more forgiving than daily ones. Premium checks hourly; you can also hit &lt;strong&gt;Refresh Posts&lt;/strong&gt; on the dashboard after publishing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Klaviyo: web feed (prefer JSON, not RSS)
&lt;/h2&gt;

&lt;p&gt;Klaviyo can ingest XML, but their own docs push JSON — and for Instagram that advice is right. In our RSS feed, a video’s enclosure is often an MP4. In JSON you get &lt;code&gt;thumbnailUrl&lt;/code&gt; for a still and &lt;code&gt;mediaType&lt;/code&gt; so you can label videos. Layout control is better too: separate caption, permalink, and image fields instead of one HTML blob.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Settings → Other → &lt;strong&gt;Web feeds&lt;/strong&gt; → Add Web Feed.&lt;/li&gt;
&lt;li&gt;Name it something without spaces, e.g. &lt;code&gt;Instagram&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;URL: &lt;code&gt;https://feedframer.com/api/v1/me?api_key=YOUR_API_KEY&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Method &lt;code&gt;GET&lt;/code&gt;, content type &lt;code&gt;JSON&lt;/code&gt;.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Then in an HTML block inside a campaign or flow email:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;table&lt;/span&gt; &lt;span class="na"&gt;role=&lt;/span&gt;&lt;span class="s"&gt;"presentation"&lt;/span&gt; &lt;span class="na"&gt;width=&lt;/span&gt;&lt;span class="s"&gt;"100%"&lt;/span&gt; &lt;span class="na"&gt;cellpadding=&lt;/span&gt;&lt;span class="s"&gt;"0"&lt;/span&gt; &lt;span class="na"&gt;cellspacing=&lt;/span&gt;&lt;span class="s"&gt;"0"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
  {% for item in feeds.Instagram.posts|slice:":3" %}
  &lt;span class="nt"&gt;&amp;lt;tr&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;td&lt;/span&gt; &lt;span class="na"&gt;style=&lt;/span&gt;&lt;span class="s"&gt;"padding: 0 0 24px 0;"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
      &lt;span class="nt"&gt;&amp;lt;a&lt;/span&gt; &lt;span class="na"&gt;href=&lt;/span&gt;&lt;span class="s"&gt;"{{ item.permalink }}"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
        &lt;span class="nt"&gt;&amp;lt;img&lt;/span&gt;
          &lt;span class="na"&gt;src=&lt;/span&gt;&lt;span class="s"&gt;"{% if item.thumbnailUrl %}{{ item.thumbnailUrl }}{% else %}{{ item.mediaUrl }}{% endif %}"&lt;/span&gt;
          &lt;span class="na"&gt;alt=&lt;/span&gt;&lt;span class="s"&gt;"{{ item.caption|default:'Instagram post'|truncatechars:100 }}"&lt;/span&gt;
          &lt;span class="na"&gt;width=&lt;/span&gt;&lt;span class="s"&gt;"560"&lt;/span&gt;
          &lt;span class="na"&gt;style=&lt;/span&gt;&lt;span class="s"&gt;"display: block; width: 100%; max-width: 560px; height: auto;"&lt;/span&gt;
        &lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
      &lt;span class="nt"&gt;&amp;lt;/a&amp;gt;&lt;/span&gt;
      {% if item.caption %}
      &lt;span class="nt"&gt;&amp;lt;p&lt;/span&gt; &lt;span class="na"&gt;style=&lt;/span&gt;&lt;span class="s"&gt;"margin: 8px 0 0 0;"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;{{ item.caption|truncatechars:200 }}&lt;span class="nt"&gt;&amp;lt;/p&amp;gt;&lt;/span&gt;
      {% endif %}
      &lt;span class="nt"&gt;&amp;lt;p&lt;/span&gt; &lt;span class="na"&gt;style=&lt;/span&gt;&lt;span class="s"&gt;"margin: 8px 0 0 0;"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&amp;lt;a&lt;/span&gt; &lt;span class="na"&gt;href=&lt;/span&gt;&lt;span class="s"&gt;"{{ item.permalink }}"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;View on Instagram&lt;span class="nt"&gt;&amp;lt;/a&amp;gt;&amp;lt;/p&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;/td&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;/tr&amp;gt;&lt;/span&gt;
  {% endfor %}
&lt;span class="nt"&gt;&amp;lt;/table&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Change &lt;code&gt;Instagram&lt;/code&gt; if you named the feed differently. &lt;code&gt;|slice:":3"&lt;/code&gt; shows three posts; Free maxes at six in the response.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What Klaviyo will not do:&lt;/strong&gt; start a flow because a new Instagram post appeared. Web feeds are content you pull into a send that was triggered by something else (welcome series, campaign schedule, purchase, and so on). If you need “email the list every time we post,” Mailchimp’s RSS automation is the better fit.&lt;/p&gt;

&lt;p&gt;Keep the feed URL private. If you regenerate the API key, update Klaviyo immediately — a failing web feed can stop emails that depend on it from sending.&lt;/p&gt;

&lt;h2&gt;
  
  
  Cost sketch: Zapier tax vs a feed URL
&lt;/h2&gt;

&lt;p&gt;Numbers move, so treat this as a shape, not a quote:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A Zap that watches Instagram and pushes into an ESP usually wants a &lt;strong&gt;paid&lt;/strong&gt; Zapier (or Make) plan once you leave the free task allotment. Every post, every retry, every test send can burn tasks.&lt;/li&gt;
&lt;li&gt;A view-metered Instagram widget is priced for &lt;em&gt;embeds&lt;/em&gt;, not for “Klaviyo fetched this JSON on send.” Hit the free view cap and the account pauses — honest metering, bad surprise on a product launch week.&lt;/li&gt;
&lt;li&gt;Feedframer Free is enough to prove the path: six recent posts, unlimited calls, no card. Premium is a flat &lt;strong&gt;$6/mo&lt;/strong&gt; (or &lt;strong&gt;$60/yr&lt;/strong&gt;) when you need more than six posts or fresher checks.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You still pay Mailchimp or Klaviyo. You stop paying a middleware tax for a feed those tools already know how to read.&lt;/p&gt;

&lt;h2&gt;
  
  
  When this is the wrong tool
&lt;/h2&gt;

&lt;p&gt;Be boringly honest:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Need multi-network UGC walls&lt;/strong&gt; (TikTok + Instagram + moderation queue) → an aggregator (Juicer and friends), not us.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Need a WordPress grid with a visual builder&lt;/strong&gt; → Smash Balloon; we are an API, not a theme customizer.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Need a new Instagram post to trigger a Klaviyo flow&lt;/strong&gt; → native web feeds do not do that; use a Zap/webhook path or Mailchimp RSS automation instead.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Compliance says tokens and media never leave your VPC&lt;/strong&gt; → DIY Graph API (and budget the 60-day refresh). Related reading on why tokens die quietly: &lt;a href="https://dev.to/philyboysmith/your-instagram-embed-will-die-in-60-days-and-how-to-stop-it-cck"&gt;Your Instagram embed will die in 60 days (and how to stop it)&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Personal Instagram account&lt;/strong&gt; → Meta will not give you the API. Switch to Business/Creator or stop here.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Soft checklist
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Confirm Business or Creator.&lt;/li&gt;
&lt;li&gt;Connect once at &lt;a href="https://feedframer.com" rel="noopener noreferrer"&gt;feedframer.com&lt;/a&gt;; copy RSS for Mailchimp or JSON for Klaviyo.&lt;/li&gt;
&lt;li&gt;Do not put raw Instagram CDN URLs into a long-lived email archive — use a host that copies media (we do).&lt;/li&gt;
&lt;li&gt;Decide what “free limit” means before a client launch: six posts in the feed is a hard cap, not a soft nag.&lt;/li&gt;
&lt;li&gt;Document key rotation: regenerate on the dashboard → update the URL in the ESP the same day.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Soft CTA
&lt;/h2&gt;

&lt;p&gt;If the goal is “Instagram in the email without another Zap,” try the Free tier, paste the URL into Mailchimp or Klaviyo, and send yourself a test. Upgrade only if six posts or daily freshness is not enough.&lt;/p&gt;

&lt;p&gt;If the goal is a custom site grid in Next or Astro, the same key speaks REST and GraphQL — email was just the excuse for this article.&lt;/p&gt;

</description>
      <category>instagram</category>
      <category>email</category>
      <category>klaviyo</category>
      <category>mailchimp</category>
    </item>
    <item>
      <title>Your Instagram embed will die in 60 days (and how to stop it)</title>
      <dc:creator>Phil Smith</dc:creator>
      <pubDate>Mon, 26 Oct 2026 13:28:34 +0000</pubDate>
      <link>https://dev.to/philyboysmith/your-instagram-embed-will-die-in-60-days-and-how-to-stop-it-cck</link>
      <guid>https://dev.to/philyboysmith/your-instagram-embed-will-die-in-60-days-and-how-to-stop-it-cck</guid>
      <description>&lt;p&gt;You ship an Instagram grid on a marketing site. It looks great in staging. Three months later the homepage shows an empty box — or worse, last month’s posts forever — and nobody filed a ticket because nothing “crashed.”&lt;/p&gt;

&lt;p&gt;This is not bad luck — it is how Meta’s Instagram access tokens work.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Instagram tokens die
&lt;/h2&gt;

&lt;p&gt;Business and Creator accounts only (personal accounts lost API access when Basic Display shut down on 4 December 2024). The flow:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;User completes OAuth → you get a &lt;strong&gt;short-lived&lt;/strong&gt; token (hours).&lt;/li&gt;
&lt;li&gt;You exchange it for a &lt;strong&gt;long-lived&lt;/strong&gt; token (~&lt;strong&gt;60 days&lt;/strong&gt;).&lt;/li&gt;
&lt;li&gt;Before that window closes, you must call the refresh endpoint and &lt;strong&gt;persist the new token&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;If you miss the window, refresh fails. The user has to log in again.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Refresh is roughly:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight http"&gt;&lt;code&gt;&lt;span class="err"&gt;GET https://graph.instagram.com/refresh_access_token
  ?grant_type=ig_refresh_token
  &amp;amp;access_token={long-lived-token}
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Gotchas:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Refresh only works while the token is still valid (usually only after it is older than 24 hours).&lt;/li&gt;
&lt;li&gt;Password changes and security checkpoints invalidate the session — refresh will not save you; re-auth is required.&lt;/li&gt;
&lt;li&gt;Even with a healthy token, &lt;strong&gt;Instagram CDN &lt;code&gt;media_url&lt;/code&gt; values expire&lt;/strong&gt;. Cached pages that stored those URLs show broken images later.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Fetching once and saving JSON is not enough. You need a scheduler, durable token storage, error alerts, and your own media copies.&lt;/p&gt;

&lt;h2&gt;
  
  
  DIY Graph refresh (sketch)
&lt;/h2&gt;

&lt;p&gt;If you want to own it, the minimal viable loop is:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;every day (real cron, not "when someone visits"):
  1. Load stored long-lived token
  2. If token age &amp;gt; ~50 days (or always weekly): call refresh_access_token
  3. Save the new access_token + expires_in
  4. Fetch /{ig-user-id}/media with fields you need
  5. Download media to your bucket/CDN; store stable URLs in your DB
  6. On Graph errors (especially code 190): alert a human, do not silently render an empty grid
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;In Next.js / Node use a real cron (Vercel cron, GitHub Action, worker). In PHP do &lt;strong&gt;not&lt;/strong&gt; rely solely on WP-Cron on a quiet site.&lt;/p&gt;

&lt;p&gt;Also budget Meta app review (when needed), API version upgrades, and field-name churn.&lt;/p&gt;

&lt;p&gt;DIY is free in dollars. It is not free in on-call.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why WordPress Instagram plugins go blank
&lt;/h2&gt;

&lt;p&gt;Plugins like Smash Balloon do the right idea: store a token, refresh on a schedule, render a grid. The failure mode is environmental:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;WP-Cron is fake cron&lt;/strong&gt; — it runs on page views. Quiet sites may never fire refresh near day 60.&lt;/li&gt;
&lt;li&gt;Failures are often &lt;strong&gt;quiet&lt;/strong&gt;: empty or stale markup; marketing is not watching &lt;code&gt;wp-admin&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Password/session changes surface as API error 190 — reconnect fixes it, but only if someone notices.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;On WordPress: real system cron → &lt;code&gt;wp-cron.php&lt;/code&gt;, alert on API errors, document re-auth for clients. Off WordPress (or tired of owning Meta’s token lifecycle): a hosted feed API moves that loop off your servers.&lt;/p&gt;

&lt;h2&gt;
  
  
  Hosted options, compared (developer lens)
&lt;/h2&gt;

&lt;p&gt;Not every “Instagram widget” product is the same. For code that needs &lt;strong&gt;data&lt;/strong&gt;, check JSON access, image hosting, refresh behaviour, and what happens when free quota runs out.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Approach&lt;/th&gt;
&lt;th&gt;Best for&lt;/th&gt;
&lt;th&gt;Watch-out&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;DIY Graph API&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Full control, unusual fields&lt;/td&gt;
&lt;td&gt;Token refresh, Meta app, expiring media URLs&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Smash Balloon&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;WordPress grid UI&lt;/td&gt;
&lt;td&gt;WP-only; renewal pricing; still depends on cron/reconnect&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Behold&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Polished widget + public JSON&lt;/td&gt;
&lt;td&gt;Free tier ~&lt;strong&gt;1,200 views/mo&lt;/strong&gt;, then &lt;strong&gt;account paused&lt;/strong&gt;; paid plans still meter views on most tiers&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Feedframer&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;REST / GraphQL / RSS, flat pricing&lt;/td&gt;
&lt;td&gt;Free capped at &lt;strong&gt;6 posts&lt;/strong&gt; (not views); Premium &lt;strong&gt;$6/mo or $60/yr&lt;/strong&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;A useful third-party roundup (Sep 2026) that scores JSON, Reels, carousels, and image hosting side by side: &lt;a href="https://electricblaze.com/developer/instagram-feed/comparison.html" rel="noopener noreferrer"&gt;Instagram Feed APIs for Developers, Compared&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Behold and view caps
&lt;/h3&gt;

&lt;p&gt;Behold is strong if you want a drop-in widget. The free-tier trap is the &lt;strong&gt;view meter&lt;/strong&gt;: hit the cap and feeds pause until next month — honest metering, surprising outage on a shared client launch.&lt;/p&gt;

&lt;h3&gt;
  
  
  Smash Balloon and WordPress
&lt;/h3&gt;

&lt;p&gt;On WordPress with layouts and a customizer, Smash Balloon is the incumbent. It is not an API for Astro or a Klaviyo RSS block, and token issues still appear when cron or re-auth is neglected.&lt;/p&gt;

&lt;h3&gt;
  
  
  Feedframer (what I built)
&lt;/h3&gt;

&lt;p&gt;I got tired of re-implementing OAuth + refresh + CDN for “just show my posts.” &lt;a href="https://feedframer.com" rel="noopener noreferrer"&gt;Feedframer&lt;/a&gt; is a small Instagram Feed API: connect a Business/Creator account once; we refresh tokens, fetch on a schedule (daily Free / hourly Premium), copy media to our CDN, and expose &lt;strong&gt;REST, GraphQL, or RSS&lt;/strong&gt; on one key.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Free:&lt;/strong&gt; 6 posts/account, &lt;strong&gt;unlimited API calls&lt;/strong&gt;, all three formats, no card.&lt;br&gt;&lt;br&gt;
&lt;strong&gt;Premium:&lt;/strong&gt; $6/month or $60/year — more accounts/posts, hourly refresh, responsive sizes.&lt;/p&gt;

&lt;p&gt;In the 30 days to 25 October 2026 we served ~&lt;strong&gt;1.1M requests&lt;/strong&gt;, &lt;strong&gt;840K media files&lt;/strong&gt;, &lt;strong&gt;1.8 TB&lt;/strong&gt;, and &lt;strong&gt;130K API calls&lt;/strong&gt; — mostly without marketing. The token problem is real enough that people find a fix when they need one.&lt;/p&gt;

&lt;h2&gt;
  
  
  When DIY vs hosted
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Stay DIY when:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;You already have a Meta app in production and an on-call rotation that understands Graph errors.&lt;/li&gt;
&lt;li&gt;You need fields or workflows a host does not expose.&lt;/li&gt;
&lt;li&gt;Compliance requires tokens and media to never leave your VPC.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Prefer hosted when:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;You are embedding &lt;em&gt;your&lt;/em&gt; (or a client’s) feed on a site and do not want a Meta project per client.&lt;/li&gt;
&lt;li&gt;You need RSS for Mailchimp/Klaviyo without building a bridge.&lt;/li&gt;
&lt;li&gt;You have been burned by a blank homepage and do not want a 60-day calendar reminder.&lt;/li&gt;
&lt;li&gt;You want unlimited request volume on a cheap plan without a view counter pausing the widget.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Prefer a WordPress plugin when:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The CMS is WordPress and stakeholders want a visual grid builder more than a JSON response.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A practical checklist either way
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Confirm the Instagram account is &lt;strong&gt;Business or Creator&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Never rely on Instagram CDN URLs in a long-lived cache — copy media.&lt;/li&gt;
&lt;li&gt;Refresh tokens on a &lt;strong&gt;real&lt;/strong&gt; scheduler; alert on auth errors.&lt;/li&gt;
&lt;li&gt;Decide what “at the free limit” means for your vendor (pause? watermark? soft upgrade nag?) before you put it on a client domain.&lt;/li&gt;
&lt;li&gt;Document re-auth steps for whoever owns the Instagram password.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Soft CTA
&lt;/h2&gt;

&lt;p&gt;Hosted path: connect once at &lt;a href="https://feedframer.com" rel="noopener noreferrer"&gt;feedframer.com&lt;/a&gt;, copy the key, &lt;code&gt;GET /api/v1/me&lt;/code&gt;. Free is enough for a portfolio; upgrade for more than six posts or hourly updates.&lt;/p&gt;

&lt;p&gt;DIY path: automate refresh this week — not on day 59. Future you will not thank you, but they also will not page you about an empty grid.&lt;/p&gt;

</description>
      <category>instagram</category>
      <category>api</category>
      <category>webdev</category>
      <category>javascript</category>
    </item>
  </channel>
</rss>
