Operator protocol

For each customer, record eligibility and actual capability per platform and action; keep source, date, account, API version and readback evidence. Confirm the relevant Skill was loaded and the customer's scope was selected. Collect facts and gaps before generating copy or a campaign specification. Present the complete account, Page, route, source, destination, assets, currency, budget and PAUSED specification for owner approval before any live write.

Create only new PAUSED entities within the approved scope; read each back. An uncertain result requires reconciliation before another write. Inspect each live placement in Ads Manager before claiming it renders correctly. Verify website and native-form lead routes separately, then test source, deduplication, status and recovery against the customer's own destination. Record unsupported or untested claims in the capability audit. These steps are requirements for an operator, not capabilities proved by this release.

Choose the customer's connection before creating credentials

Discover the Meta and destination connectors already available in the customer's agent host. Verify ownership, the exact account/Page/form or website route, the requested read/write action and its permissions. Reuse a suitable authorized connector for a supervised action and read its result back. If a capability is missing, describe the specific customer-owned app, permission or connection needed and obtain approval before setup. A new Google Cloud project or standalone OAuth is not a universal prerequisite for a supervised Skill run. An existing Meta app is usable only when its scope, permissions and separation between customers fit the actual action; a new app is not automatically required for every customer.

When the customer deliberately chooses a self-managed Marketing API route, guide the customer through current official Meta documentation before any account action. Have the account owner create their own Meta developer app, associate the correct business and ad-account assets, request only permissions needed for the selected read/write action, establish secure credential storage, and perform a read-only test of the selected account first. The operator must stop for the owner's participation and approval at app, access, credential and external-write steps. Never ask for an access token or app secret in chat, put one in the teaching kit, or claim a Skill created the app. An existing authorized connector may use its own app/OAuth and needs no separate app from the student. Distinguish own-account development/testing from access to other client accounts; app review, access level or business verification may apply. Confirm current requirements from Meta rather than relying on UI labels in this document. Source: https://github.com/facebook/facebook-nodejs-business-sdk

Keep permission purposes distinct: ads_read can support ad-data reading; ads_management is needed for ad management; native Meta lead retrieval needs leads_retrieval and appropriate Page/Lead Access and terms. A website lead route needs its own form, measurement and destination, not necessarily native-form retrieval permission. Verify the current platform requirements, app access level and customer assets for each route. Do not assume an App Review exemption.

Choose lead delivery and continuous operation

For a supervised lead write, verify the existing CRM/Sheets connector can access the exact destination, send a bounded request with a stable lead key, observe its result, read back the record and journal the outcome. A prepared plan alone is not delivery. A successful agent-mediated test does not prove webhook ingestion or operation after the chat closes.

For ongoing receipt, first consider a suitable native form-to-CRM integration the customer already operates. Offer customer-owned n8n only when custom routing, mapping, multiple destinations, retry or status feedback needs a workflow. Before setup, specify source trigger and authentication, tenant and field mapping, stable lead key, target write and readback, uncertain-write reconciliation, bounded retries, failure alerts, status return, owner, minimum permissions and retention. This release includes no configured n8n workflow or always-on service.