How sources work

A source is one connection between a project and a tool you already run, and every piece of evidence Adduce holds arrived through one.

A source belongs to one projectCopy Anchor Link

Sources are scoped to a project, never to the workspace. Two projects reading the same PostHog account each hold their own source, with their own credential and their own sync. A project may hold several sources of the same kind — two Intercom workspaces, three transcript collections — and nothing crosses between projects.

Every source has a Type from the catalog, a name you choose, and, for a source read over an API, a status: Connected, Error, or Not configured. A transcripts collection shows No transcripts yet or its file counts instead. Each source shows a signal count: the pieces of evidence Adduce has taken from it.

Adding one takes four steps, or three for uploadsCopy Anchor Link

Add source opens a wizard. For a tool Adduce connects to over its API the steps are Choose integration, Connection details, Establishing connection and Result. For an upload source — a transcripts collection — there is nothing to connect to, so the third step is skipped and the steps are Choose integration, Name the collection and Result.

The first step lists every connector. A tile marked Beta works but has not been proven against a real customer account yet; a tile marked Coming soon cannot be chosen.

The connection test runs before anything is savedCopy Anchor Link

Choosing Continue on Connection details tests what you entered before the source exists. Most connectors are checked against the tool itself: Adduce calls a cheap read endpoint with your credential, so a wrong region or a revoked token is caught on the spot. A few are checked only for shape — PostHog is one — and for those the first sync is what proves access.

If the test fails, no source is created. The result names what went wrong, and the field to correct.

The first sync backfills, then Adduce syncs dailyCopy Anchor Link

The first sync reaches back as far as that connector's backfill window — full history for PostHog, ninety days for Intercom, a trailing window for the observability tools. Each source page names its own.

After that every source syncs once a day, at 03:00 UTC. Sync now on the source page runs one immediately. Only one sync per source runs at a time, so a long backfill is never overtaken by the nightly run. A source whose last sync failed shows Error and is left out of the daily run until a Sync now succeeds, so a failure never repeats itself unnoticed each night.

Sync history is the record of what happenedCopy Anchor Link

The source page lists its recent runs, newest first, each with its outcome and how long it took. A completed run shows how much evidence it added. A failed run shows a short reason — authentication expired, rate limited by the provider, a configuration problem — and expands to the full message the tool returned.

Credentials are replaced by deleting and adding againCopy Anchor Link

There is no edit form for a source's credentials. To rotate a key, delete the source and add it again with the new one; the next sync is a full backfill.

Deleting asks you to type the source's own name, and it removes the evidence that source produced along with it. Themes built from that evidence lose it too.

Where to see this in AdduceCopy Anchor Link

• Sources in a project's sidebar holds the list and the Add source button. The destinations Adduce writes to have their own Destinations page under Delivery.
• A source's own page has a header with Sync now (or Upload transcripts) and a ⋯ menu with Delete source. Below it, one status line shows whether the source is healthy and when it last synced. The Sync history section lists recent runs; Gong adds a Calls tab, Amplitude adds a Funnels tab, and upload sources show Files. A panel on the right holds Details and Help.
• Pipeline shows how much evidence arrived, and from which source.

What's nextCopy Anchor Link