Skip to content
AetherDocs0.1.0-alpha.0

Connectors

Connectors bring in activity from the tools you already use and turn it into one common format. Nothing changes in your app.

14 available connectors

CategoryProvidersDirection
CRMHubSpot, Salesforceinbound
CommerceShopifyinbound
BillingStripeinbound
MarketingKlaviyoinbound
Product analyticsSegment, PostHog, GA4inbound
SupportZendesk, Intercominbound
ProjectJira, Linearinbound + outbound
MessagingSlackinbound + outbound
GenericSigned webhook (HMAC-SHA256)inbound + outbound

How a connector works

  1. 01ConfigureEnable per tenant (off by default) and add provider credentials. Secrets are never stored in config or returned by the API.
  2. 02TestPOST /v1/integrations/connectors/{type}/test checks the credential.
  3. 03Sync or receivePull with /sync, or receive signed webhooks. Every inbound webhook is written to WebhookInbox before processing.
  4. 04NormalizeProvider payloads map to canonical events (event_type, source, external_id, occurred_at, properties).
  5. 05ObserveAudit, metering (connector_sync, webhook_ingested), and sync health are recorded.
◈Outbound deliverySlack, Linear, and Jira can also receive actions. Provider webhooks feed outcomes back to the graph.
▲ReadinessReal provider API calls need credentials. Connector readiness is not a claim of certified production sends.
+How many connectors are there?
22 today: 21 named providers plus a generic signed webhook.
+Can I build my own?
Use the signed webhook or the feed API for any system not in the catalog.