Connectors

    Every data source, one governed inbox

    DataInbox ingests business events from streams, databases, SaaS apps, files, IoT brokers, webhooks, and SDKs. Every event is validated against a schema in the semantic catalog before any AI agent or workflow can act on it.

    Event streams and message brokers

    • Apache Kafka: Consume topics as verified business events.
    • Confluent Cloud: Managed Kafka streams with schema registry alignment.
    • Redpanda: Kafka-compatible streams routed into the inbox.
    • AWS Kinesis: Stream ingestion with replay and ordering.
    • Google Pub/Sub: Push or pull subscriptions, validated at ingest.
    • Azure Event Hubs: High-throughput event capture and routing.
    • NATS / RabbitMQ: Subject and queue based event routing.

    Databases and warehouses

    • PostgreSQL: CDC via logical replication or polling.
    • MySQL / MariaDB: Row-level changes turned into events.
    • MongoDB: Change streams as inbox messages.
    • Snowflake: Query or stream tables into governed events.
    • BigQuery: Scheduled or streaming export to inbox topics.
    • Databricks: Delta table change feeds.
    • Redshift: Materialized streams or scheduled extracts.

    SaaS and business apps

    • Stripe: Payments, refunds, disputes, payouts.
    • Salesforce: Opportunities, accounts, cases as events.
    • HubSpot: Contacts, deals, marketing engagement.
    • Shopify: Orders, customers, inventory, fulfillment.
    • Zendesk: Tickets and conversation events.
    • Intercom: Conversations, leads, product events.
    • SAP / Oracle ERP: Documents and master data via adapters.
    • NetSuite: Transactions and customer records.

    Files and documents

    • AWS S3: Object events and structured file ingest.
    • Google Drive / OneDrive: Document drops parsed to events.
    • SFTP / FTP: Scheduled file pickup with validation.
    • CSV / Parquet / JSON: Schema-mapped into business events.

    IoT and sensors

    • MQTT brokers: Device telemetry as inbox events.
    • OPC UA: Industrial machine signals.
    • AWS IoT Core: Device shadows and rule-routed payloads.

    Webhooks and HTTP

    • Inbound webhooks: Per-source signed endpoints with replay protection.
    • REST polling: Scheduled pulls with delta tracking.
    • GraphQL subscriptions: Live query results as events.

    SDKs and bring your own

    • JavaScript / TypeScript SDK: Client and server event emission.
    • Python SDK: Producer for backend services and notebooks.
    • Java / Go SDKs: High-throughput producers.
    • REST Event API: POST any event to the inbox with a schema id.
    • Datalayer / GTM: Stream browser events alongside analytics.

    Connector FAQ

    What data sources can DataInbox connect to?

    DataInbox ingests from event streams (Kafka, Confluent, Redpanda, Kinesis, Pub/Sub, Event Hubs, NATS), databases (PostgreSQL, MySQL, MongoDB), warehouses (Snowflake, BigQuery, Databricks, Redshift), SaaS apps (Stripe, Salesforce, HubSpot, Shopify, Zendesk, Intercom, SAP, NetSuite), files (S3, Drive, SFTP, CSV, Parquet, JSON), IoT brokers (MQTT, OPC UA, AWS IoT Core), inbound webhooks, REST polling, GraphQL subscriptions, and SDKs for JavaScript, Python, Java, and Go.

    How do I send a custom event to DataInbox?

    Use the REST Event API or one of the SDKs. Every event is POSTed with a schema id and payload. The schema is registered in the semantic catalog and validated at ingestion. No code is required when sources are connected through the prebuilt connectors.

    Are events validated at ingestion?

    Yes. Every event is validated against its schema in the semantic catalog before it becomes a Verified Business Event. Invalid events are rejected with a structured error and routed to a dead-letter inbox for review.

    Can DataInbox run alongside Kafka or Confluent?

    Yes. DataInbox consumes Kafka and Confluent topics as native sources and can also produce events back to them. It is not a replacement for the broker, it is the governance and routing layer above it.

    Does DataInbox support GA4 or datalayer events?

    Yes. Browser datalayer and GTM events can be streamed in parallel to GA4 so analytics and AI consume the same governed event stream without duplicate instrumentation.

    Need a connector that is not listed?

    Any HTTP, queue, database, or file source can be connected through the REST Event API or an SDK.