Source connector

Instagram connector

Instagram integration for databases, warehouses and BI tools

Organic profile content and audience insights. Datrise captures Instagram entities such as media posts, stories, comments, followers, reach metrics and profile insights, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Instagram Platform API (Meta Graph API v26.0) authenticates with OAuth 2.0, incremental runs key on timestamp, and Instagram caps calls at Business Use Case rate limiting: calls within a rolling 24 hours are capped at 4,800 × the number of Instagram impressions on the professional account in the preceding 24 hours (no fixed ceiling below that); messaging endpoints have separate fixed caps, e.g. 2 calls/second per account for Conversations.

Of the 6 objects, 5 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `instagram_media_posts`) with a schema derived from the Instagram API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Instagram pipeline page, and join the waitlist to get the Instagram connector with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Instagram data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
media posts	instagram_media_posts	Upsert by primary key, incremental on updated-at
stories	instagram_stories	Upsert by primary key, incremental on updated-at
comments	instagram_comments	Upsert by primary key, incremental on updated-at
followers	instagram_followers	Upsert by primary key, incremental on updated-at
reach metrics	instagram_reach_metrics	Append-only, incremental by timestamp
profile insights	instagram_profile_insights	Upsert by primary key, incremental on updated-at

Instagram API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Instagram Platform API (Meta Graph API v26.0)
Authentication	OAuth 2.0 — OAuth 2.0 issues an app-scoped Instagram or Facebook User access token; short-lived tokens last 1 hour and must be exchanged for a long-lived token valid 60 days, which then has to be refreshed before expiry.
Pagination	cursor — Edges (media, comments, etc.) that support cursor pagination return `before`/`after` cursors in the response; the API does not surface `previous`/`next` links, so the caller has to build the next request's query string manually.
Rate limit	Business Use Case rate limiting: calls within a rolling 24 hours are capped at 4,800 × the number of Instagram impressions on the professional account in the preceding 24 hours (no fixed ceiling below that); messaging endpoints have separate fixed caps, e.g. 2 calls/second per account for Conversations
Incremental cursor	timestamp — IG Media only exposes a `timestamp` field (creation date, ISO 8601 UTC) with no `updated_at` equivalent, so edits to a caption or changes in engagement metrics on an existing post cannot be detected from the field alone.
Webhooks	Yes — Instagram webhooks (comments, mentions, messages, story_insights, etc.)
Bulk export	No
Deletes detectable	No

Official API reference

What bites when replicating Instagram

IG Media's only timestamp is the creation `timestamp`; there is no field that changes when a caption is edited or when `like_count`/`comments_count` change, so incremental polling by timestamp silently misses engagement updates on existing posts.
None of the documented webhook fields (comments, mentions, messages, story_insights, etc.) fire on deletion, so deleted media, comments, or stories cannot be detected without diffing a full re-list against previously stored IDs.
The main Business Use Case rate limit isn't a fixed number: it is 4,800 calls per 24 hours multiplied by the account's own impressions in that window, so a low-traffic account can be throttled at a very small absolute call count.
Long-lived access tokens expire after 60 days and must be actively refreshed before then; a connector that lets a token lapse has to send the user through the OAuth flow again rather than silently renewing.

Compare this against every other documented API

Popular destinations for Instagram

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Instagram connector FAQ

What Instagram data does the connector extract?: 6 objects: media posts, stories, comments, followers, reach metrics and profile insights. Each lands in its own table with types preserved; history-style objects (1: reach metrics) load as append-only streams.
Is the Instagram integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Instagram data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Instagram → destination pair has its own page with the object-to-table mapping.

Related sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Instagram pipeline with guided onboarding

Join the waitlist to get priority access for Instagram integrations with guided setup, schema-aware mapping, and production-grade incremental sync.