Which integrations work today and which are still waiting
The 247 cards in Integrations fall into groups: connected with a real account, reaching sign-in, checked with a made-up key, and waiting on someone else's approval.
Of the 247 cards in Integrations, 22 have been connected with a real account, 116 reach the service's own sign-in page, 49 take a key that the service checks, 4 connect through their own window, and 54 are waiting for someone else. The card you want may be in any of them, so here is what each group means.
The groups
- Cards
- 22
- What it means
- Someone connected a real account once. The token may have lapsed since.
- Cards
- 116
- What it means
- Omne opens the service's own sign-in page. Nobody has finished the sign-in yet.
- Cards
- 49
- What it means
- The service rejected a fake key in its own words, so Omne reaches it. A real key has not been tried.
- Cards
- 4
- What it means
- beehiiv, Bluesky, Medium and Telegram. The window was not run in this check.
- Cards
- 54
- What it means
- Cannot connect until someone else acts.
- Cards
- 2
- What it means
- Amazon S3 got no answer from the endpoint tried, and Stripe has no app keys saved on the live address yet, so Connect cannot start.
Connected with a real account
Gmail, Google Ads, Google Analytics, Google Business Profile, Google Drive, Google Photos, Search Console, Tag Manager, YouTube, Hashnode, Kick, MailerLite, Mastodon, Pinterest, Substack, Skool, Tumblr, Twitch, Vimeo, X, Granola and Wispr Flow.
Reach sign-in but not finished
These show the service's real sign-in, so the connection is wired, but a complete connection has not been seen. Examples include the other Google apps (Calendar, Docs, Sheets, Slides, Forms, Contacts, Tasks, Meet, Admin, Gemini), GitHub, Notion, Slack, Discord, Dropbox, Kit, TikTok, WordPress, Zapier, Linear, Supabase, HeyGen, Higgsfield and Runway. If one fails after you sign in, contact support and name the service.
Key-based services
Services such as Resend, Flodesk, Typefully, Vercel, Webflow, Ghost, SendGrid, Twilio, Typeform, Brevo and Semrush take a key you paste. Omne checks the key with the service and shows the service's own refusal if it is wrong. A made-up key was refused in each service's words, which proves the check reaches the service. A real key for most of them has not been tried.
Waiting on someone else
These cannot connect yet, for reasons outside Omne's code. See Integrations waiting for approval.
Sync sources are separate
Settings also has Sync sources, under Workspace. Those read saves, bookmarks and highlights into your Library, and they are a separate list from Integrations. Of them, RSS, Readwise, Instagram saves, passive capture and browser bookmarks have been read with real data. The others are built but not yet proven with a real account, including Substack saved, Mastodon bookmarks, Bluesky saved, YouTube liked and playlists, X bookmarks, Snipd, Readwise Reader, Reddit, Pinterest, TikTok favorites, Threads, Facebook and LinkedIn saves.
Reading this honestly
A connection can succeed and a feature built on it still be limited. Business Profile, for example, reads nothing until Google grants access through its form. Connecting an account is the first step. What Omne can do with it is listed in the panel under What Omne can do.
The numbers change as more services are proven, so treat the lists as a snapshot.
Last updated November 3, 2026
There's a real person behind Omne, so ask anything.