To connect Instagram Public Data to ChatGPT:
- Sign up free at portermetrics.com and connect your Instagram Public Data account with your Google account.
- In ChatGPT, click + → Connectors → Manage connectors → Add custom connector, name it Porter, paste
https://mcp.portermetrics.com/mcp, then click Add and authenticate with Google.
That’s it, you’re connected. Porter’s free plan covers up to 3 Instagram Public Data profiles with no usage limits on ChatGPT’s free plan. No credit card required.
What makes Porter different:
- 30+ Instagram Public Data metrics and dimensions across every reporting level in one connection.
- Universal Instagram Public Data MCP. Hosted white-label dashboards and client portals, competitor tracking with public profile analysis, content strategy validation with cross-platform data. Your whole Instagram Public Data operation runs from one chat.
Prerequisites
- A Porter Metrics account with your Instagram Public Data account connected (free tier is enough to try it end-to-end)
- A ChatGPT account — the free plan works for ChatGPT Web; a Pro subscription is needed for Codex and Desktop MCP features
- Admin or standard access to the Instagram Public Data profiles you want to connect
Connect Instagram Public Data to ChatGPT with MCP
For this tutorial we’re going with the MCP method. Here’s a quick explainer of what MCP is and why it’s the best path for Instagram Public Data.
MCP (Model Context Protocol) is the open standard that lets AI tools like Claude, ChatGPT, Codex and others access and use external APIs — the things that make tools like Instagram Public Data work under the hood. Instead of building a custom integration for every AI tool you use, you install one MCP and every compatible AI gets access to the same data.
The full setup takes under 5 minutes and breaks into three moves: connect Instagram Public Data to Porter, point ChatGPT at the Porter MCP, and ask your first question.
1. Connect your Instagram Public Data data to Porter
Porter sits between Meta’s Instagram Graph API / Business Discovery API and ChatGPT. It handles OAuth, rate limiting, pagination and all the plumbing so ChatGPT only ever sees clean, structured data.
Sign up for Porter. Create a free account at portermetrics.com. The free tier is enough to run this full workflow end-to-end.
Connect your Google. In Porter, click Create → pick ChatGPT as the destination → select Instagram Public Data as the source → sign in with Google to grant access to your profiles.
Select your profiles. Choose the Instagram Public Data profiles you want ChatGPT to query. When you select multiple profiles under a single connection, Porter automatically blends their data together so you can query them as one.
Optional: enable automatic BigQuery storage if you’re connecting multiple profiles with large data volumes. This keeps ChatGPT’s responses fast even at scale.
2. Connect the MCP to ChatGPT
Porter’s MCP URL is what you paste into ChatGPT. Once added, ChatGPT can query Instagram Public Data data on demand in any conversation.
Go to chatgpt.com and click the + icon in the chat input to open the tools menu.
In the menu that opens, hover over Connectors and click Manage connectors.
In the Connectors panel, click the + button at the top of the list to start adding a new connector.
Pick Add custom connector from the dropdown that appears.
A dialog opens with the name and URL fields. Type Porter in the first field to name the connector.
In the second field, paste https://mcp.portermetrics.com/mcp. Leave the advanced settings alone.
Click Add at the bottom right of the dialog. ChatGPT opens a sign-in window — use the same Google account linked to your Porter workspace and approve access.
Once the authorization finishes, you’ll see Porter’s tools appear in the connectors panel. You’re ready to start asking questions (and, for connectors that support it, running actions).
For a fuller walkthrough with screenshots at every step, see the Porter MCP tutorial.
3. Start building questions and dashboards
With Porter connected, open a new ChatGPT chat and ask anything about your Instagram Public Data in plain English. ChatGPT calls Porter behind the scenes, pulls live data from Meta, and answers with tables, charts, or summaries.
Try one of these to verify the setup is working:
For a full catalogue of copy-paste prompts organized by use case (performance, competitor monitoring, client reporting, agencies, brand teams, creators, cross-channel), jump to the prompts section below.
Alternative ways to connect Instagram Public Data to ChatGPT
Porter MCP is the path we just walked through and the one we recommend for most marketers. It is not the only way to get Instagram Public Data data in front of ChatGPT, though. The most common alternatives are Instagram Public Data’s direct API, a live Google Sheets bridge or CSV upload, and BigQuery for scale. Each has trade-offs, so pick the one that fits how your team already works.
- 🔌 Instagram Public Data’s direct API — Talk to Meta’s Instagram Graph API yourself. Maximum control, but you handle auth, rate limits and pagination — and you only get one source. (Meta doesn’t ship an official MCP yet.)
- 📊 Google Sheets — Live Sheet or one-off CSV upload. Auditable, familiar, faster for big exports — but aggregation happens in the Sheet, not the API.
- 🗄️ Google BigQuery — For large profiles or agencies running multi-profile analysis. BigQuery aggregates; ChatGPT only queries pre-built summaries.
Via the Porter Metrics app in the ChatGPT marketplace
If you’d rather not paste a connector URL, install Porter straight from ChatGPT’s app gallery — it’s the same Porter connection behind the scenes, published as an approved ChatGPT app:
- Open the Porter Metrics app page in ChatGPT (or search “Porter Metrics” in the apps gallery).
- Click Connect and sign in with the same account you use in Porter.
- Authorize it and ask your first Instagram Public Data question — same live data as the MCP.
The trade-off to know: the marketplace app only updates after each ChatGPT review cycle, while the MCP updates the moment Porter ships. If you want every new tool and data source immediately, use the MCP; if you want the one-click install and don’t mind waiting for new features, the marketplace app is the shortest path — including write actions through your connected Porter account.
Via Instagram Public Data’s direct API
If you’re building a product around Instagram Public Data — or you’re a developer who’d rather own every layer of the integration — the most direct path is talking to Meta’s Instagram Graph API yourself, or — where it exists — Instagram Public Data’s own official MCP. Instagram Public Data doesn’t ship an official MCP yet, so going direct means writing API calls yourself in Codex or your own scripts. Whichever route you pick, you still follow Meta’s rate limits & quotas. Either way you skip Porter and call Meta from your own code, from Codex, or from Instagram Public Data’s own connector.
The trade-off to know. Going direct gives you maximum control and the freshest possible data — every endpoint, every parameter, no abstraction layer in between. But you’re now responsible for OAuth flows, refresh tokens, rate limits, pagination, schema changes, and error retries. And critically, you only get one source. The moment you also want Google Ads, GA4 or Shopify in the same conversation, you’re back to building (or stitching together) more integrations.
When this makes sense: engineering teams that need a single source with full control, products that ship Instagram Public Data data as a feature (where you own the integration anyway), or one-off scripts where you don’t mind writing the auth and pagination code yourself. For marketers who want to ask questions in plain English and blend Instagram Public Data with the rest of their stack in a single conversation, the Porter MCP path is dramatically less work.
Via Google Sheets (live Sheet or manual CSV)
If your team already lives in Google Sheets — or you want a paper trail before ChatGPT touches anything — feed Instagram Public Data into a Sheet, then let ChatGPT read the Sheet. You can automate the Instagram Public Data → Sheets pipeline with Porter so it refreshes daily, or do one-off CSV exports from Instagram Public Data’s native UI for static analysis.
The trade-off to know. With the MCP path, ChatGPT calls Meta’s API directly and Meta does the filtering and aggregation on its side — clean and deterministic. With the Sheets path, ChatGPT aggregates inside the Sheet itself, which can introduce hallucinations on totals, averages, and joins when you have thousands of rows. The upside is speed: for very large date ranges or historical analysis, a pre-built Sheet is dramatically faster than live API calls.
When this makes sense: finance teams that want to review numbers before ChatGPT acts on them, agencies already delivering client reports in Sheets, historical analysis across years of data, or any case where you care more about speed than real-time freshness.
Read the full Sheets tutorial →
Via Google BigQuery (for scale)
This is the path most people overlook — and it’s the one that saves you when your Instagram Public Data profile gets serious. A single large social media analyst or an agency managing 10+ profiles will hit API rate limits and latency problems querying ChatGPT directly. ChatGPT will literally tell you it’s taking too long or timing out on big pulls.
BigQuery fixes that. You load Instagram Public Data data into BigQuery tables on a schedule, then connect BigQuery to ChatGPT — either through a BigQuery MCP or via Codex with SQL queries. Instead of asking ChatGPT to pull raw Instagram Public Data data, you let BigQuery aggregate into small, optimized tables, and ChatGPT only queries the summarized output. Scale problem solved.
When this makes sense: enterprise profiles with thousands of public profiles and posts, agencies running multi-profile analysis across 10+ clients, or any team already using BigQuery as a data warehouse. Porter loads Instagram Public Data (and 25+ other sources) directly into BigQuery so you don’t have to build your own ETL.
Connecting Instagram Public Data to Codex
Most marketers lump ChatGPT and Codex together and miss the biggest advantage of the entire MCP ecosystem. They’re not the same tool — and the difference matters enormously once you start working with Instagram Public Data data seriously.
ChatGPT is a chat interface. You ask a question, ChatGPT pulls live data through the MCP, answers, maybe builds a quick dashboard inside the conversation. Great for one-off analysis. The problem: everything is ephemeral. Want to refresh the dashboard tomorrow? You regenerate it from scratch. Want the same report every Monday? You re-ask the question every Monday.
Codex is ChatGPT running inside your computer’s terminal. Because it has access to your filesystem, runtime, and other developer tools, it doesn’t just answer questions — it can build real software. Persistent scripts, scheduled routines, HTML apps, internal dashboards, integrations that run 24/7 without your input. Once it’s connected to Porter’s MCP for Instagram Public Data, a whole category of work becomes possible.
What Codex unlocks that ChatGPT alone cannot
This is where the MCP ecosystem pays off most. Because Codex can combine Porter’s MCP with other MCPs — Firecrawl for web scraping, Airtable for structured data, Notion for wikis, Vercel for deployment, Slack and Gmail for delivery — you’re no longer querying data. You’re building tools.
Feed Codex your Instagram Public Data targets and goals — follower count thresholds, engagement rate benchmarks, posting frequency targets — and ask it to generate a custom competitive intelligence dashboard for each client. It builds the HTML, pulls live data, deploys to a URL. No Data Studio embed to break when the vendor changes pricing, no template constraints. The dashboard updates automatically because it queries Porter’s MCP on every page load.
Best for:agencies that want white-label client dashboards without Looker or Data Studio dependencies.
Combine your own Instagram Public Data performance from Porter with competitor public profiles and hashtag trends scraped via Firecrawl. Codex stitches both into a weekly competitive intelligence report — your numbers next to their posting frequency, engagement rates, and content themes, with an LLM summary on top of what changed week over week. Runs on cron, lands in your inbox every Monday morning.
Best for:in-house teams that need market context, not just internal numbers.
Use Airtable or Notion as the schema, Porter as the data source. Codex keeps every page populated with current Followers count, Media count of likes, and Media count of comments for every profile — no stale screenshots, no copy-paste from Excel. New hires read one wiki entry and have full context on a client’s account.
Best for:agencies and ops teams onboarding analysts or rotating account managers frequently.
A Codex routine on cron pulls Instagram Public Data via Porter, evaluates thresholds — Followers count drops below threshold, Media count of likes spikes 2× the trailing average — and pushes Slack or Gmail alerts the moment something crosses the line. You stop checking dashboards reactively; the dashboard checks itself and tells you when to look.
Best for:any team that’s ever discovered a problem 48 hours too late because nobody opened the report.
Bottom line: ChatGPT is for quick questions and ad-hoc dashboards. Codex is for building apps, live dashboards, alerts, and actual tools — anything you want to run on its own without re-asking. Same Porter MCP URL works in both, so you don’t pick once and lock in.
Use cases: what you can actually do once Instagram Public Data is connected to ChatGPT
Getting the connection right is half the battle. The real value shows up in what you do next. Here are the use cases Porter users build around their Instagram Public Data data — from simple Q&A to full client-facing workflows.
1. Chat and ask questions directly
The simplest use case — and still the one 80% of marketers start with. Open ChatGPT, ask a question, get an answer grounded in live data.
It’s the fastest way to replace a daily Instagram app / Instagram native UI check-in. But chat is table stakes — the interesting use cases come next.
2. Blend Instagram Public Data with your social / marketing data (Meta Ads, Shopify, HubSpot)
This is where a 360° view gets real. When you connect Instagram Public Data and your marketing/social data (Meta Ads for paid social amplification, Shopify for e-commerce competitor tracking, HubSpot for lead-gen content analysis), ChatGPT can map public Instagram profiles and posts to actual content strategy decisions and competitive positioning — using account names, media captions, and posting dates — and give you competitive benchmarking that no platform-side number can.
ChatGPT handles the account names and posting dates mapping and joins. You get a client-ready competitive benchmarking report that no single platform can generate on its own.
3. Automated alerts and notifications on Slack or Gmail
With Codex you can turn Instagram Public Data monitoring into a routine that runs on its own. Hook Porter’s MCP (for the data) together with a Slack or Gmail MCP (for delivery), then write a Codex scheduled task that pulls performance every morning and pings you only when something actually needs attention.
No dashboards, no daily check-ins. The report comes to you — and only when it matters.
4. Client-ready presentations with live data (Gamma, HTML, PDF)
A common agency pain: you send clients a Data Studio link, manual spreadsheet breaks, the client panics — and you spend an hour explaining a broken dashboard. With ChatGPT you can build the presentation itself — as a Gamma deck, a custom HTML page, or a PDF — populated with live numbers each time.
The presentation becomes a delivery artifact you send to the client, not a dashboard that depends on another tool staying up. No broken iframe, no login prompts, just the content.
Instagram Public Data fields and metrics you can query with ChatGPT
Before you start writing prompts, it helps to know what data is actually available. Porter MCP gives ChatGPT access to 30 Instagram Public Data fields and metrics across every reporting level, plus breakdowns by date, media type, account, and hashtag. And the same MCP URL also unlocks 25+ other sources — so ChatGPT can blend Instagram Public Data with Google Ads, GA4, Shopify, HubSpot and more in a single prompt.
Prompts you can copy-paste today
…organized by job: Agencies, Brand teams, Creators & DTC, Cross-channel.
1. Prompts for agencies managing multiple clients
When you’re running competitor benchmarking across multiple client accounts.
2. Prompts for brand teams and content strategists
When you’re optimizing content calendars and posting schedules.
3. Prompts for creators and DTC founders
When you’re growing your own audience and iterating on content.
4. Cross-channel prompts
When you’re blending Instagram Public Data with other marketing channels for a full-funnel view.
How to use Codex for Instagram Public Data without getting banned
This is the nightmare scenario for any marketer running Instagram integrations through a Meta Developer account. Unlike a consumer Instagram ban, a developer account suspension is irreversible and cascades to every app, Business Manager, and client asset tied to that identity. The cost isn’t just downtime — it’s lost client trust, broken automations, and weeks of rebuilding infrastructure. For agencies and social media analysts using Instagram Public Data at scale, the real risk isn’t a temporary rate-limit error; it’s a permanent platform exile triggered by behavior Meta’s automated systems flag as suspicious.
Meta’s enforcement is behavior-based and quota-based, not tool-based. Meta doesn’t ban accounts because you used Claude, an MCP server, or Porter Metrics. It throttles or suspends because of how the API was used: excessive request velocity, missing or expired permissions scopes, scraping private data boundaries, or triggering automated-write patterns from apps not in Live mode. Instagram Graph API applies rate limits per user and per app , and exceeding them returns HTTP 429 errors with exponential backoff. Read-only access to public profiles and posts is generally safe if rate limits are respected. Bursty parallel requests, repeated token failures, or attempts to access non-public data (stories, DMs, private accounts) are not. Meta’s automated review also flags apps with abnormal traffic patterns — for example, a sudden spike from a single IP or app making thousands of profile lookups in minutes — which can trigger a Business Manager or app review suspension without human warning.
The two behaviors that actually get accounts banned
After reviewing official docs and community threads, two patterns come up again and again.
1. Running unapproved apps in Development mode against live public data at scale. Instagram Graph API apps must pass App Review and be switched to Live mode before they can access data from users who are not app admins or testers. Running a custom MCP or scraper in Development mode and pointing it at hundreds of public profiles looks, to Meta’s systems, like an unauthorized scraping bot. This is one of the most common triggers for app suspension cited in developer forums. Instead: use a reviewed, Live-mode app — or rely on a managed platform like Porter that handles app review and token lifecycle for you.
2. Ignoring rate-limit headers and retrying aggressively on HTTP 429. Instagram Graph API returns x-app-usage and x-ad-account-usage headers that show how close an app is to its limit. Developers who ignore these and retry immediately — or worse, spin up parallel connections — burn through their quota and flag the app as abusive. InsightfulPipe and GitHub ig-mcp both document “strict rate limits” as a primary pain point. Instead: implement exponential backoff (wait at least the Retry-After seconds specified in the 429 response) and batch requests rather than firing them individually.
Both behaviors trigger Meta’s automated enforcement. If you want to use ChatGPT for Instagram Public Data safely, follow the 5-rule protocol below.
The 5-rule safety protocol
Based on Meta’s documented rate limits and quotas and the behaviors that have actually caused account suspension — not guesswork:
-
Stay in read-only mode. Instagram Public Data connectors should never attempt to publish, comment, DM, or modify account settings. Porter’s Instagram Public Data connector is read-only by design — zero risk of accidental publishing or TOS-violating write operations. This is the safest posture because Meta’s automated enforcement weights write abuse far more heavily than read abuse.
-
Respect rate-limit headers and back off on 429. . Meta’s rate-limiting documentation states that exceeding limits triggers throttling and can escalate to app suspension. Porter enforces this automatically by batching requests and applying platform-level backoff when
x-app-usageapproaches the threshold. If you’re building a custom MCP, implement at least a 2-second delay between profile lookups and never retry a 429 before theRetry-Afterheader value. -
Use a reviewed, Live-mode app — or a managed platform. Apps in Instagram Graph API Development mode can only access data from app admins and testers. Attempting to scale public-data collection from Development mode is a documented suspension trigger. Porter operates through reviewed, Live-mode infrastructure so you never risk a personal developer account. If you self-build, submit your app for App Review and switch to Live mode before any production use.
-
Never store or expose PII scraped from public profiles. Public Instagram data still contains personal information: usernames, bios, profile photos, locations. GDPR and CCPA apply to how you process and retain this data, even if it was publicly visible. Porter does not persist raw profile data beyond the session window needed for analysis. If you export to Sheets or databases, anonymize identifiers and set a retention policy of .
-
Label data freshness honestly — never claim “real-time.” Instagram Public Data has a lag of minutes to hours, not seconds. InsightfulPipe documents this explicitly: “API data can lag by minutes, not seconds.” — InsightfulPipe, Jan 2026. Porter surfaces the last-sync timestamp on every dataset so you and your stakeholders know exactly how fresh the data is. Presenting stale data as real-time damages trust and can lead to flawed campaign decisions.
What Porter MCP does differently: it enforces these safeguards at the platform level so you don’t have to manage them manually. Porter’s Instagram Public Data connector is read-only by default — there is no code path that can publish, comment, or modify an account. Rate limiting is handled with automatic backoff and request batching, so you never hit a 429 or trigger Meta’s velocity alerts. The connector operates through reviewed, Live-mode app infrastructure — your personal Meta Developer account is never exposed to suspension risk. Every dataset carries a freshness timestamp, and Porter’s field reference explicitly scopes to public-only data (no DMs, no stories, no private accounts). That’s the behavior Meta’s automated systems reward: predictable, low-velocity, read-only, public-data access that stays within platform boundaries.
Frequently asked questions
Ready to chat with your Instagram Public Data?
Open ChatGPT, add the Porter connector, and ask your first question. If you don’t have Porter yet, start a free trial and connect your Instagram Public Data account — you’ll be chatting with your campaigns in under five minutes.
rocket_launchStart free Porter trialopen_in_newOpen ChatGPT