56 providers are available today, and the list grows — new ones appear without a platform upgrade on your side, because the registry is server-side.
Each provider declares a type (what kind of thing it is) and use cases (what it can be used for). Features pick an integration by use case rather than by name, which is why a shipping feature works with whichever carrier you have configured.
Social media
Sixteen providers. Used for publishing, engagement, community and advertising.
| Provider | Use cases |
|---|---|
| Facebook, Instagram, Ads, Social Media | |
| Instagram (via Facebook) | Instagram, Ads |
| LinkedIn, Ads, Social Media | |
| X / Twitter | Twitter, Ads, Social Media |
| TikTok | TikTok, Ads, Social Media |
| YouTube | YouTube, Video, Social Media |
| Pinterest, Ads, Social Media | |
| Snapchat | Snapchat, Ads, Social Media |
| Reddit Community, Content Sharing, Discussion Forums | |
| Discord | Discord Bot, Community Management, Gaming |
| Telegram | Telegram Bot, Messaging |
| Slack | Messaging, Social Media |
| Twitch | Twitch Streaming, Gaming, Live Content |
| Bluesky | Bluesky, Social Media |
| Mastodon | Mastodon, Social Media |
| Threads | Threads, Social Media |
| Google Business Profile | Google Business, Google My Business |
Payments
Seven providers. All payment integrations are bring-your-own — funds land in your account, so the credentials must be yours.
| Provider | Use cases |
|---|---|
| Stripe | Payment, Subscription |
| PayPal | Payment, Subscription |
| Paddle | Payment, Subscription |
| Helcim | Payment, Subscription |
| Gift card | Payment, Gift Card |
| Account balance | Payment, Account Balance, Wallet |
| Offline payment | Payment, Offline Payment |
Gift card, account balance and offline payment are internal tenders — cash, store credit and wallet balance — handled through the same payment interface as cards.
Marketplaces
Seven providers, for listing and selling on external storefronts. Bring-your-own, since these are your seller accounts.
| Provider | Use cases |
|---|---|
| Amazon | Amazon, E-commerce, Marketplace, Product Sync |
| eBay | eBay, E-commerce, Marketplace, Product Sync |
| Etsy | Etsy, E-commerce, Marketplace, Product Sync, Handmade |
| Walmart | Walmart, Marketplace, E-commerce, Product Sync |
| Shopify | Shopify, E-commerce, Product Sync |
| WooCommerce | WooCommerce, WordPress, E-commerce, Product Sync |
| Bing Shopping | Bing Shopping, Microsoft Ads, E-commerce, Product Sync |
See sales channels for how listings, inventory and orders are kept in step across them.
Shipping and logistics
Five carriers and aggregators, all sharing the Shipping, Logistics use case — so shipping features work with whichever you configure.
EasyPost · ShipEngine · Shippo · FedEx · UPS · Stamps.com
Messaging, email and voice
| Provider | Use cases |
|---|---|
| Twilio | SMS, Voice, Phone |
| Infobip | SMS, Email, Phone |
| AWS | Email, SMS, Marketing, Transactional Email, Domain Registration |
| SendGrid | Email, Marketing, Transactional Email |
| Mailgun | Email, Transactional Email, Marketing |
| Resend | Email, Transactional Email, Marketing |
Twilio is the clearest sub-account case: accepting its agreement provisions you an isolated sub-account rather than sharing ours.
AI
| Provider | Use cases |
|---|---|
| Anthropic | AI |
| OpenAI | AI, Voice, Chat, Analytics |
| Google Gemini | AI |
| DeepSeek | AI |
AI providers are the most common fallback case — they work immediately on platform credentials, and you can switch to your own key at any point. See Vibe Agent.
Google and Microsoft
Two broad providers spanning many services rather than one.
Google — Email, Ads, Shopping, Maps, Display & Video, Extensions, Audiences, Negative Keywords, Bidding, Voice, Speech, Translation.
Microsoft — Voice, AI, Translation, Email, Calendar, Outlook, Contacts, Tasks.
Databases
MongoDB · MySQL · PostgreSQL
For reading from or writing to an external database as part of a workflow or data sync.
Other
| Provider | Use cases |
|---|---|
| Firebase | Push, Database |
| MQTT | IoT, MQTT |
| Figma | Figma, Design |
| Zapier | Integration |
Picking by use case rather than by name
Features request an integration by use case. A shipping quote asks for Shipping; a text message asks for SMS.
That indirection is why swapping FedEx for UPS, or SendGrid for Resend, is a configuration change rather than a code change — and why a provider added to the registry becomes usable by existing features without anything being rewritten.