Tempo

Business software

Built when you ask for it

Sync Tempo worklog, account, team, and plan 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 Tempo connector syncs your time-tracking and planning data into analytics-ready tables in your data warehouse. Pull worklogs, accounts, teams, and plans from the Tempo 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:

  • Worklogs
  • Accounts
  • Teams
  • Plans

How it gets built

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

What you will need

API token (Bearer). In Tempo, select Settings in the Tempo sidebar, then API Integration under Data Access, and click New Token. Name it, set when it expires (30 days unless you change it), and give it full access or custom access that can view worklogs, which Ingest checks the token with. Click Confirm and copy the token: Tempo shows it only once.

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 Tempo connector?
Not as a finished connector yet. Ingest builds it from Tempo's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can Tempo data go to?
Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, ObsessionDB, 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.

Tempo API documentation: https://apidocs.tempo.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, ObsessionDB, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for SaaS teams: Asana, OpenAI (ChatGPT Enterprise), Clockify, Google Drive, Google Sheets, Jira.

Request Tempo