Linking Rocketlane as a source

Alpha release

This source is currently in alpha. The interface and available tables may change.

The Rocketlane connector pulls your customer onboarding and professional services data — projects, tasks, time entries, users, and custom fields — into the PostHog data warehouse, so you can analyze it alongside your product data.

Prerequisites

You need a Rocketlane account with access to generate an API key.

Adding a data source

  1. In PostHog, go to the Sources tab of the data pipeline section.
  2. Click + New source and click Link next to this source.
  3. Enter your credentials (see Configuration below) and click Next.
  4. Select the tables you want to sync, choose a sync method and frequency, then click Import.

Once the syncs are complete, you can start querying this data in PostHog.

When linking Rocketlane, you'll need:

  • API key – generate an API key under Settings → API in the Rocketlane app. This single key grants read access to your projects, tasks, time entries, users, and fields.

Sync modes

All Rocketlane tables use full refresh sync. Rocketlane's list endpoints do not expose a server-side timestamp filter, so each sync reloads the full dataset.

Configuration

OptionTypeRequired
API keypasswordYes

Supported tables

TableDescriptionSync methodIncremental fieldPrimary key
projects

A Rocketlane project — a customer onboarding or professional-services engagement.

Full refresh
tasks

A Rocketlane task — a unit of work within a project, optionally grouped under a phase.

Full refresh
time_entries

A Rocketlane time entry — logged work against a project, task, or ad-hoc activity.

Full refresh
users

A Rocketlane user — a team member, partner, or customer with access to the account.

Full refresh
fields

A Rocketlane custom field definition, attached to projects, tasks, or users.

Full refresh

Troubleshooting

  • If you see an authentication error (401), your Rocketlane API key may be invalid or revoked. Generate a new key under Settings → API in the Rocketlane app, then reconnect.
  • If you see a permission error (403), your API key does not have access to the requested data. Check the key's permissions, then reconnect.

If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.

Community questions

Was this page useful?

Questions about this page? or post a community question.