Skip to content
Integrations

Agency software integrations, and what the operator does with each

These agency software integrations are not a logo wall. Each page lists the actions NeoAI can genuinely perform against that app, generated from the registry the operator executes through — and each one says what the integration cannot do, which is the half nobody publishes.

An integration page that is written by hand starts rotting on the day it ships. These render from `capabilitiesForApp`, the same list the Connections screen prints on its cards and the same list the runtime dispatches through, so adding a capability grows the page and removing one shrinks it.

Apps without a page are still connected and still work — they are listed below without a link rather than given a stub. A catalogue that covers every app badly is worse than one that covers some of them properly.

Everything connected

18 apps are connected. 7 of them have a page.

The grid is the whole list, and it is generated from the same registry the Connections screen reads. The pages above are the ones that have been written and read by somebody — the rest connect and work exactly the same way.

Marked apps need the provider’s own app review before they will serve a production account at scale. We say so on the card rather than letting you find out at the first API call.

  • Gmail
  • Outlook
  • Google Calendar
  • Calendly
  • Google Meet
  • Slack
  • WhatsApp
  • Notion
  • Google Docs
  • Google Drive
  • Google Sheets
  • HubSpot
  • Facebook
  • Instagram
  • LinkedIn
  • YouTube
  • Google Analytics
  • Google Maps

Start with one client and one connection.

Nothing here needs a migration or a configuration project. Connect a mailbox, designate the contacts for a single client, and read what the operator has drafted by the morning.

Nothing optional runs until you say so.

The cookies that keep you signed in, and nothing else unless you turn it on. What we collect