Connectors block 10: 11 listed marketing, SEO and engagement adapters

[helpcodeai]

Summary

Block 10 of the connector backlog: marketing analytics, SEO data and customer-engagement services that Composio covers and we didn't. SISTRIX was also searched for by two Cloud workspaces. Eleven adapters are listed (Amplitude, Segment, Semrush, Ahrefs, SISTRIX, DataForSEO, Braze, Customer.io, Iterable, OneSignal, plus Yandex Disk from block 9). No test accounts exist for them, so every tool was compared with the vendors' own SDKs, OpenAPI specs and MCP servers and with maintained clients that call these APIs (recorded real calls where available); mismatches were fixed. Moz (method names differ between its own code and current docs) and Google Photos stay unlisted.

Changes

• Analytics: Amplitude (23 tools: segmentation, funnels, retention, active users, sessions, revenue, cohorts, user search, taxonomy; US/EU hosts; query-cost limits in descriptions), Segment Public API (29 tools: workspace, sources, destinations, warehouses, tracking plans, functions, event volume, delivery overview, usage, audit trail; all writes off; credential fields stripped from settings).
• SEO: Semrush (21 reports, CSV answers explained, unit costs, display_limit 10 by default), Ahrefs v3 (18 tools, column-based unit costs, default select, limit 10), SISTRIX (18 tools, credit costs), DataForSEO (18 tools, live endpoints only, prices per call, errorWhen for errors inside HTTP 200, POST reads marked read-only), Moz JSON-RPC (15 tools, async keyword suggestions).
• Engagement: Braze (23, all 15 REST instances), Customer.io App API (26), Iterable (23, US/EU), OneSignal (16). Message sends need confirmation and an explicit "yes, send" for segments or several recipients; deletes are installed switched off.
• Every GET tool keeps answers small with a response mapping.
• Vendors with an official remote MCP server (possible later bridges): Amplitude, Semrush, Ahrefs, SISTRIX, Moz (beta), Braze (beta), Customer.io, OneSignal; DataForSEO and Iterable publish local ones.

Type

• New feature

Testing

• Added/updated unit tests

• node scripts/validate-adapters.mjs --warn: 427 adapters passed, 0 failed, no warnings on the new files.

• node scripts/regenerate-catalog.mjs: 427 adapters. node scripts/adapter-count.mjs --check: OK (412 listed).

• packages/backend: npx tsc --noEmit -p tsconfig.json clean; npm test 593 suites, 16,231 tests passed; npm run lint 0 errors.

• Code review, 14 Oct 2026: about 280 tools checked one by one; fixes: Amplitude chart results on /csv, OneSignal delete-user answer, Braze user deletion by email and canvas_entry_properties, Customer.io numeric transactional ids and campaign metrics fields, DataForSEO instant-page checks, Semrush filter examples and keyword-gap columns, SISTRIX parameter notes. Counts 401 -> 412 adapters, 6,007 tools.

• Live without credentials: every vendor answers 401/403 to a wrong key on its real routes. Credentialed live specs (gated by RUN_<SLUG>_LIVE=1) come before listing; DataForSEO's live spec uses its free sandbox.

Known gaps: Moz and OneSignal have no GET health check (Test connection reports not_found/403; the install probe is the reliable check).

Cloud and self-hosted behave the same: catalog JSON only.

Checklist

• My code follows the existing code style
• I have tested my changes locally
• All existing tests pass (npm test)
• This PR has a descriptive title