Provider catalogue and setup
Before building a custom integration, ask your NewsTeam project owner whether an existing service covers the workflow. They supply its reachable service URL and the configuration for your environment. The developer pack does not provision a hosted integration or provider account.
Registered production source
Section titled “Registered production source”Updated 17 October 2026
The catalogue below covers content, identity and billing integrations. Available service URLs and provider configuration depend on your NewsTeam environment. Contact the relevant teams below to activate and verify an integration for your organisation.
| Integration / type ID | Source capability and setup | Activation contact |
|---|---|---|
WordPress / wordpress | Inbound; source URL, optional authenticated access and mapping settings | Integrations team + source CMS owner |
Ghost / ghost | Inbound; Ghost URL and Admin API key | Integrations team + source CMS owner |
Medium / medium | Inbound; reachable export archive URL | Integrations team + archive owner |
ArcXP / arcxp | Inbound; API base URL, access token, website IDs/public URLs | Integrations team + source CMS owner |
CosMoS / cosmos | Inbound; host, consumer/access credentials, publications and public Site URL | Integrations team + source CMS owner |
FTP Export / ftp | Outbound; FTP/SFTP address, port, credentials and writable destination path | Integrations team + destination owner |
WorkOS / workos | Identity; server API key, client ID and approved sign-in/callback setup | Integrations team + identity owner |
Paystack / paystack | Billing; public/secret keys and intended products/provider environment | Integrations team + billing owner |
Polar / polar.sh | Billing; access token, production/sandbox selection and products | Integrations team + billing owner |
Entitlement Service / entitlement-service | Billing-shaped entitlement/product/subscription reads; service URL, API key and optional Cloudflare Access credentials. Does not supply checkout, portal or purchase callback handling | Integrations team + entitlement service owner |
Activate and verify a provider
Section titled “Activate and verify a provider”- Have the integration owner confirm the deployed service version and reachable protected URL, supported SDK contract, selected type and recognised capabilities in your NewsTeam environment.
- In organisation integration settings, save provider attributes and configure the appropriate inbound/outbound/identity/billing tabs. Store secrets in trusted service/configuration storage, never in a public website or mobile bundle.
- For inbound, agree the Bucket, workflow status, content policy, cursor and auto-publish behavior. Capture a small fixture, replay it and check article IDs, URLs, bylines, widgets and media permissions before enabling automatic imports.
- For outbound, confirm the destination and supported trigger; test a safe sample, retries and duplicate handling. For identity, test sign-in, token exchange, sign-out and failure recovery. For billing, use configured test accounts and the intended provider to verify products, checkout/callback, subscriptions and entitlements.
- Record the named activation owner, date, deployed environment/service version and the tested path in your project handover. Repeat acceptance after an integration, provider or contract upgrade.
SDK methods and release boundaries
Section titled “SDK methods and release boundaries”Published @newsteam/plugin-sdk@1.0.0-alpha.3 provides typed discovery, inbound/outbound, identity, billing and action interfaces, plus OnWebhook and OnEvent. An interface is not evidence of provider signature validation, notification reconciliation or a completed operator workflow. Checkout browser returns and asynchronous provider notifications require separate tests.
Additional editorial actions, analytics, automation and provider-notification capabilities are in development. These are directions for the platform rather than a list of available provider integrations. We will document supported workflows when they are released and verified in the target environment. Site-configured browser analytics remain a separate client feature.
Start custom work with the current importer example or developer pack. Public products use the V1 client and subscription recipe, not integration RPCs.