Integrations
Integrations & Webhooks
Integrations connect outside tools to Mailneo — forms and commerce platforms feed subscribers and automation triggers, and the Developer API integration issues the key and webhook that power custom code. This guide covers the catalog, each connect flow, and the developer surface.
In this guide you will:
- connect an integration and configure newsletter auto-sync
- know which credential each provider needs
- generate an API key and verify inbound webhook signatures
The Integrations page
Open Integrations from the app (it is also embedded as the Integrations tab in Settings). The page shows stat cards (Total Available, Connected, Active, Errors), search, a status filter, and category tabs. Available integrations:
| Integration | Category | How it connects |
|---|---|---|
| Developer API | Developer | Generates an API key and a webhook URL |
| Google Sheets | Apps | OAuth (availability currently limited — see below) |
| Notion | Apps | OAuth |
| Airtable | Apps | API key |
| Tally | Apps | Webhook URL you paste into your Tally form |
| WordPress | Apps | Site URL + username + Application Password |
| WooCommerce | Commerce | Site URL + Consumer Key / Consumer Secret |
| Polar.sh | Commerce | API key |
| Gumroad | Commerce | API key |
Google Sheets connections may show a "No longer available" badge while the OAuth verification that gates the integration is pending — existing connections remain visible but new ones cannot be made until it is re-enabled.
Newsletter auto-sync
Every connected integration can feed the newsletter system: choose a target list, whether created subscribers go through double opt-in, and which tags to stamp on them. That is how a Tally form submission or a WooCommerce customer becomes a subscriber — and the corresponding automation triggers ("Form submitted", "Makes purchase", "Data synced") fire from the same events.
The Developer API integration
Connecting Developer APIcreates your team's API credentials. Its manage dialog has two tabs — API Keys and Logs:
- Your API Key — one key per team, sent as the
x-api-keyheader. Only the prefix stays visible; Regenerate replaces it (the old key stops working immediately, and the full key is shown exactly once). - Webhook URL — an inbound endpoint unique to the integration, plus a Signing secret (admins can reveal it). Inbound calls are signed with
X-Webhook-Signature: sha256=<hex>, an HMAC you should verify before trusting a payload. - Rate Limits — 100 requests/minute for single operations, 10/minute for bulk operations.
- Logs — recent API activity and bulk-sync history for debugging.
curl https://api.mailneo.co/api/v2/contacts?limit=25 \
-H "x-api-key: $MAILNEO_API_KEY"The API key is team-wide, shown once, and regenerating it cuts off anything still using the old one. Store it in a secrets manager, never in client-side code or version control.
Going further
The full REST surface — campaigns, contacts, newsletters, webhook subscriptions — is documented in the API Reference; outbound webhook mechanics (endpoints, HMAC verification, replay) are covered in API concepts — webhooks. Ready-made tooling — the TypeScript SDK, n8n node, and MCP server — lives under Resources.
Troubleshooting
- Integration shows an error — reconnect it from its card; OAuth tokens and application passwords expire or get revoked.
- Webhook events not arriving — check the Logs tab; confirm the external service posts to the exact webhook URL and that your handler returns a 2xx.
- 429 responses — you hit the per-minute limit; back off and batch where possible.