The Instagram channel the klien switches on, answered under your brand.
The Instagram connector lives inside Business OS. The klien grants Meta consent on the workspace you provisioned. Inbound DMs and comments land on the chat desk, get grounded in the klien catalog, and go back out as replies under your partner brand. You stay the operator on record. The klien keeps the audience.
Runs under
Your partner brand, on the workspace you provisioned for the klien.
Serves
The klien team, with one desk for DMs, comments, and all other channels.
Talks to
The klien end customers, on the Instagram handle the klien already owns.
The klien clicks connect. The operating layer does the rest.
A Meta consent dialog opens on the klien workspace. The klien picks the Professional account they own. The connector subscribes to the message and comment webhooks, resolves the IGSID, and the chat desk goes live. No tokens flow back to the partner UI. No klien data crosses tenant boundaries.
instagram_business_basic
Resolve the connected Instagram Professional account. Display the username, profile picture, and follower count inside the klien workspace so the klien can confirm the right handle is wired up.
instagram_business_manage_messages
Receive inbound DMs through the Instagram Messaging webhook, and post replies through the official Messaging API. Reply flow only fires after the klien grants consent and the operating layer composes a grounded answer.
instagram_business_manage_comments
Receive comments left on the connected account, post replies, and hide spam when the klien rule allows it. Used by the comment workflow inside the chat desk, not by any prospecting tool.
Five surfaces, nothing else.
The connector pulls only what the chat desk needs to answer a thread. Profile browsing, story metadata, audience insights, and prospecting fields stay out of scope.
Account identifiers
Instagram Professional account ID (IGSID), username, profile picture URL, linked Facebook Page ID. Used to render the connection and to address API calls.
Connection tokens
Long-lived access token issued by Meta. Stored encrypted at rest. Never returned to the partner. Used only for outbound calls from the operating layer.
Inbound messages
Sender IGSID, message text, attachment URLs, timestamps, conversation thread ID. The grounding layer reads these to compose a klien-faithful reply.
Outbound replies
Generated reply text, send timestamp, Meta message ID, success or failure status. Logged against the klien thread for the audit trail.
Webhook metadata
Event type (message, reaction, comment, postback), delivery time, signature verification result. Used to keep the desk in sync with the channel.
One klien account, one Instagram silo.
No partner can reach into another partner book. No klien can reach into another klien on the same partner book. The connector is engineered so the boundary holds at the database, not just at the UI.
01
The klien connects through their own Meta consent
The OAuth dialog opens inside the klien workspace. The klien picks the Professional account they own. The token comes back attached to that klien tenant, not to the partner, not to Laras, not to any other klien.
02
Tenant scope is enforced at the database layer
Every Instagram row carries the klien tenant id. Postgres row-level security blocks any read that does not match the active tenant. A partner cannot see another partner klien. A klien cannot see another klien on the same partner book.
03
No partner reads the raw token
The token lives in the operating layer. Reply composition and send happen on the same surface that holds the klien catalog and policies. The partner UI shows status, volume, and outcomes, never the secret.
04
Klien can disconnect in one click
A klien revokes the connection from inside their workspace settings, or from Meta directly. The token, the webhook subscription, and the cached identifiers are cleared within minutes. Past threads remain as business history under the klien tenant.
Not a scraper. Not a prospecting tool. Not a data resale layer.
No selling
The connector never resells, rents, or shares klien Instagram data with advertisers or data brokers. It exists to answer threads on the klien account, period.
No scraping
It does not crawl public Instagram profiles to build lists. Inbound conversations are the only source of customer data the connector reads.
No partner export
The partner cannot download the klien customer book. Reporting shows volume, outcomes, and quality, not contact-level export.
No training on klien data
Klien threads are not used to train models. They are stored to ground the next reply on the same thread, and to keep the audit trail.
Sell the Instagram channel as a klien outcome, not a license you resell.
You set the price. Subscription, retainer, project, outcome. The operating layer runs quietly under your brand on the klien account, and the Instagram channel becomes something the klien wants to keep paying you for.
For the platform addendum used during Meta App Review, see the Privacy Policy and Data deletion references.