<pectus.ai/>
./pectus.ai — builder framework · self-hosted · MIT

Integrations

Pectus pulls performance data from the platforms a user already runs ads on, plus their organic search data. Each integration is a separate setup flow because every platform has its own approval and authentication quirks.

Order to set up:

  1. Google Search Console + Google Analytics 4 — covered in the main pectus.md install flow (uses a service account).
  2. Google Ads — see google-ads.md. Same OAuth client as Search Console / Analytics; needs a developer token + refresh token.
  3. Meta Marketing API (Facebook + Instagram) — see meta.md. System User token from Business Manager.
  4. LinkedIn Marketing API — see linkedin.md. Approval-gated (1–3 weeks) — start the application early.

Each tutorial lists the env vars it sets, what manual approval is required (and how long it typically takes), and the minimum scope of access we ask for.

Status, configuration, and a Test connection button for each integration live on the app’s own page in the CMS at /apps/<app-name>. The Apps top-nav entry lists them. A skill that needs data from an integration that isn’t connected will surface a clear error rather than silently producing empty output.