Integrations connect Appmint to the services you already use — payment providers, carriers, ad platforms, messaging, marketplaces and AI providers.
What connects
| Category | Services |
|---|---|
| Payments | Stripe, PayPal, card terminals |
| Shipping | Carrier rating, labels and tracking |
| Advertising | Facebook, Google Ads, Twitter/X |
| Marketplaces | Amazon, eBay, Etsy, Walmart, Shopify, Google Merchant Center |
| Messaging | Email providers, SMS and voice, WhatsApp |
| AI | Anthropic, OpenAI, Google Gemini, DeepSeek, ElevenLabs |
| Business | Accounting, calendars, storage and identity providers |
Connecting a service
Most connections use OAuth: you authorize Appmint from the provider's own screen, and the resulting credentials are stored against your organization rather than in your code.
Connections are configured under Configuration, and their status is visible per service, so a connection that has expired is apparent before it silently stops working.
Each provider needs its callback registered in that provider's console. A callback registered for one environment will not work in another, and the failure appears at the provider rather than in Appmint's logs.
Webhooks
Inbound webhooks let a provider notify Appmint when something happens on their side — a payment settled, a shipment moved, a message was delivered.
Webhook endpoints identify the organization from the URL itself rather than from a header, because the provider calling them has no way to send tenant headers.
Marketplace channels
Selling on external marketplaces is more than a connection — it needs category mappings, attribute mappings, pricing rules and order aggregation. That has its own surface: see sales channels.
Building your own
Anything not covered by a built-in connector can be driven through the AppEngine API with an API key, or triggered from an automation making an outbound call.