With Meta connected, Fostr pulls Facebook, Instagram, WhatsApp, and Ads data directly into your AI operating system. This page highlights the key credential requirements, access permissions, and visibility settings so your team knows how Meta information flows into Fostr, who can access it, and how to keep usage secure and role‑appropriate in automated workflows.

Credentials and Access

To activate the Meta integration, Fostr requires a System User Access Token provisioned through Meta’s Business Manager. These credentials are tied to an app within the Business Manager environment and grant access to the supported APIs for Facebook, Instagram, WhatsApp, and Ads. Typical credential components include:

• The System User Access Token linked to the Meta Business Manager
• The Business Manager ID and System User ID associated with the token
• The App ID configured for Fostr’s Meta integration
• (Optional) Ad Account ID(s) for retrieving advertising campaigns and insights

The integration is configured at the tenant level, meaning a single set of Meta business credentials provides consistent access to messaging data (FB, IG, WhatsApp), Ads Manager, and Page-/post-level insights across the organization’s connected accounts.

All credentials are encrypted and securely stored within the Integration record in Fostr. Access is restricted to Administrators and authorized internal stakeholders, with environment‑level protections ensuring they cannot be exposed or modified outside approved update events.

Meta does not rely on user‑issued OAuth in this setup; instead, long‑lived System User tokens are used. These tokens must be refreshed periodically in accordance with Meta’s security model. A test instance is available, allowing teams to validate credential accuracy, confirm permissions, and simulate data ingestion before deploying the integration to production use.

Permissions and Visibility

Once enabled, the Meta integration makes data from configured surfaces available inside Fostr workflows. Typical use cases include:

• Accessing inbound and outbound message threads from Facebook, Instagram, and WhatsApp
• Retrieving Ads Manager performance data including campaigns, ad sets, and insights
• Surfacing Page or post‑level analytics, comments, and engagement data for connected Facebook and Instagram properties
• Linking Meta data to Fostr Actions for use in lead tracking, client communications, and performance monitoring

Access inside Fostr is governed by a combination of Meta’s API token scopes and Fostr’s internal role model:

• Only internal users with the appropriate Fostr roles (e.g., Admins, Operators, CS Implementers) can view or act on ingested Meta data.
• Visibility is scoped to the pages, ad accounts, and assets granted to the Business Manager and the connected System User.
• Fostr never overrides Meta’s data‑sharing rules; if the System User token lacks access to a property, it will not appear in Fostr.

Visibility is not configurable at the integration layer itself. Instead:

• Fostr role permissions determine who in the tenant can see Meta‑sourced Recordsets or Actions.
• Access remains in line with both the permissions of the Meta account providing the credentials and Fostr’s internal security framework.

The Meta integration requires ongoing maintenance of tokens and business account permissions:

• If the System User token expires, or if permissions to pages/ad accounts are revoked, Fostr will lose access to Meta data.
• In these cases, Administrators must generate a new long‑lived token in Business Manager and update the Integration record in Fostr to restore connectivity.