Linking Goldcast as a source

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

Learn more

Alpha release

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

The Goldcast connector syncs organizations, events, agenda items, and more into the PostHog data warehouse, so you can analyze them alongside your product data.

Prerequisites

Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.

Adding a data source

In PostHog, go to the Sources tab of the data pipeline section.
Click + New source and click Link next to this source.
Enter your credentials (see Configuration below) and click Next.
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.

Enter your Goldcast API token to sync your virtual event and webinar data.

An org admin can create a personal access token in Goldcast Studio under Settings → Tokens. The token is shown only once, so copy it immediately.

API access requires a Pro, Premium, or Enterprise plan, and the token feature must be enabled by Goldcast support.

You'll be asked for:

API token

Sync modes

Each table can be synced in one of several modes, depending on what the source supports:

Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
Incremental – only new or updated rows are synced on each run, using a cursor field (such as an updated_at timestamp). Cheaper than a full refresh, but deletes aren't captured.
Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.

See sync methods for a full explanation of how each mode works and how to choose between them.

All Goldcast tables are full refresh. Each sync replaces the contents of the table.

Configuration

Option	Type	Required
`API token`	password	Yes

Supported tables

Table	Description	Sync method	Incremental field	Primary key
`organizations`	The Goldcast organization (workspace) that owns the events, including its branding, plan, and integration settings.	Full refresh	—	id
`events`	A Goldcast event — the base object of the platform. An event is a virtual or hybrid gathering that can contain sessions, agenda items, tracks, and members.	Full refresh	—	id
`agenda_items`	Agenda items scheduled within events — the individual slots that make up an event's programme.	Full refresh	—	id
`discussion_groups`	Discussion groups (breakout rooms and booths) within events, where attendees gather for smaller conversations.	Full refresh	—	id
`tracks`	Tracks group related agenda items within an event, letting attendees follow a themed strand of sessions.	Full refresh	—	id
`webinars`	Webinar configuration and schedule for each event. Fetched per event, so `event` identifies the parent event.	Full refresh	—	event, id
`event_members`	People associated with an event — registrants and attendees — including their attendance, engagement, and marketing attribution. Fetched per event.	Full refresh	—	event, id
`broadcasts`	Broadcasts are the live sessions within an event — the stages attendees watch, with their schedule, live state, and engagement settings.	Full refresh	—	id
`broadcast_polls`	Polls run during a broadcast, with their answer options. Fetched per broadcast, so `broadcast` identifies the parent broadcast.	Full refresh	—	broadcast, id
`ticket_types`	Ticket types defined for events, which control the tracks a registrant can access. Resolves the ticket type on event members.	Full refresh	—	id
`speakers`	Speakers listed on each event. Fetched per event, so `event` identifies the parent event.	Full refresh	—	event, id

Troubleshooting

If the connection fails with an authorization error, the API token is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.

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.