Skip to main content

Pendo

This connector captures data from Pendo into Flow collections.

It is available for use in the Flow web application. For local development or open-source workflows, ghcr.io/estuary/source-pendo:dev provides the latest version of the connector as a Docker image. You can also follow the link in your browser to see past image versions.

Supported data resources

The following data resources are supported through the Pendo API:

By default, each resource is mapped to a Flow collection through a separate binding.

Prerequisites

  • A Pendo account with the integration feature enabled.
  • A Pendo API key

Configuration

You configure connectors either in the Flow web app, or by directly editing the catalog specification files. See connectors to learn more about using connectors. The values and specification sample below provide configuration details specific to the Pendo source connector.

Properties

Endpoint

PropertyTitleDescriptionTypeRequired/Default
/credentials/access_tokenAPI KeyYour Pendo API key.stringRequired
/startDateReplication Start DateUTC date and time in the format "YYYY-MM-DDTHH:MM:SSZ". Data prior to this date will not be replicated.string1 hour before the current time

Bindings

PropertyTitleDescriptionTypeRequired/Default
/nameData resourceResource in Pendo from which collections are captured.stringRequired

Sample

captures:
${PREFIX}/${CAPTURE_NAME}:
endpoint:
connector:
image: ghcr.io/estuary/source-pendo:dev
config:
credentials:
access_token: <secret>
bindings:
- resource:
name: Feature
target: ${PREFIX}/Feature
- resource:
name: Guide
target: ${PREFIX}/Guide
- resource:
name: Page
target: ${PREFIX}/Page
- resource:
name: Report
target: ${PREFIX}/Report
- resource:
name: PageEvents
target: ${PREFIX}/PageEvents
- resource:
name: FeatureEvents
target: ${PREFIX}/FeatureEvents
- resource:
name: TrackEvents
target: ${PREFIX}/TrackEvents
- resource:
name: GuideEvents
target: ${PREFIX}/GuideEvents
- resource:
name: PollEvents
target: ${PREFIX}/PollEvents