Every Source You Report On, Wherever You Need the Answer

When a report needs a source OWOX has no connector for, the usual answers are a vendor roadmap, a script only its author can fix, or a CSV exported by hand every month. With Custom Connectors, your AI assistant writes that connector from the API's docs.

• Give the assistant OWOX's manifest guide and the API's documentation, then import the JSON it returns.
• Test it against the live API before anything depends on it; every publish is a version you can roll back.
• The data loads into your own warehouse as a scheduled Data Mart, and keys stay in OWOX, never with the assistant.

Marketing wants a new ad channel in next week's cross-channel report, and its endpoint can offer a hundred fields under API names like date_start. Store them all, and business users wade through unused columns and ask you what each one means. In a Connector Data Mart, you pick the fields that land and name each one for business.

• The unique-key fields the connector merges rows on stay selected, however few fields you tick.
• Only the fields you tick are stored in your warehouse; the alias lives in the Output Schema, so the stored column keeps its name.
• Google Sheets headers and Data Studio's field list show the alias, not the API field name.
• Ask Claude or ChatGPT about spend through OWOX MCP, and it receives each field's alias and description, not just an API name like date_start to guess at.

When the CEO wants a new reporting or AI tool, you check where the company's data will live, and a tool that keeps its own copy decides how much history you keep. OWOX runs on the warehouse you already own.

• Every Data Mart runs its SQL in your own Google BigQuery, Snowflake, AWS Redshift, AWS Athena or Databricks, against your tables and their full history.
• When the business asks which number is right, the answer sits in your own warehouse, where your SQL can check it.
• Connectors load raw data from ad platforms and SaaS tools into your warehouse, so reports stop being stitched from CSV exports.
• Leaving OWOX never means losing the data: the tables stay, and the data model exports as OKF Markdown or JSON.

A report people open every morning is only as fresh as its last run, and a stale one looks exactly like a current one. Triggers import the source and deliver the report on a schedule you set on the Data Mart.

• Run it every working day, on a set date each month, at set times on chosen days of the week, or on an interval, each trigger in its own timezone.
• A failed run emails Project Admins and Data Owners, or calls your webhook, on by default; Run History shows the error and every run's status.
• You set the order: the connector imports into your warehouse first, then each report delivers.