Docs / Data sources / Jibble

Jibble

Business software

Built when you ask for it

Sync Jibble time entry, people, project, and timesheet data into your warehouse. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.

The Jibble connector syncs your time-tracking and attendance data into analytics-ready tables in your data warehouse. Pull time entries, people, projects, and timesheets from the Jibble API, with Ingest handling auth, pagination, and retries so the tables stay current.

What you would get

Each of these arrives as its own table, kept current on the schedule you choose:

  • Time entries
  • People
  • Projects
  • Timesheets

How it gets built

  1. Choose Jibble when you set up a pipeline, with the warehouse it goes to and a schedule.
  2. Ingest reads Jibble's documentation, and you choose the tables you want.
  3. Ingest builds the connector and tests it against Jibble itself.
  4. A person at Ingest reviews and publishes it, and your pipeline starts on its own.

What you will need

OAuth 2.0 (client credentials). The organization owner creates a Client ID and Client Secret under Organization settings, then exchanges them for a bearer access token.

You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.

Questions

Does Ingest have a Jibble connector?
Not as a finished connector yet. Ingest builds it from Jibble's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can Jibble data go to?
Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
Do I need to write code?
No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

Jibble API documentation: https://docs.api.jibble.io/

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for SaaS teams: Asana, Jira, Airtable, Clockify, Facebook Ads, Frankfurter.

Request Jibble