> ## Documentation Index
> Fetch the complete documentation index at: https://docs.findtempo.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Artifacts

> How Tempo ingests artifacts from your connected sources on its own, what it does with each one, and what to do in the rare case something was not captured.

A deal artifact is one piece of source context Tempo has ingested for a deal: a call transcript, an email thread, a Slack thread, a document, a CRM note, or a note a seller recorded. Tempo extracts [observations](https://docs.findtempo.co/context-layer/observations.md) from most artifacts. [Themes](https://docs.findtempo.co/themes.md), [Signals](https://docs.findtempo.co/signals.md), and your AI tools use those observations.

Tempo ingests calls, emails, threads, and documents from connected sources and links them to deals. Some sources need a deal link or matching contacts. If Tempo does not capture relevant context, you can add it by hand.

## Artifacts arrive from your connections

| Connection | What arrives | Learn more |
| - | - | - |
| Salesforce, HubSpot, or CSV import | Your opportunities and their accounts. Every artifact is tied to a deal or to the deal's account. | [Salesforce](https://docs.findtempo.co/integrations/salesforce.md), [HubSpot](https://docs.findtempo.co/integrations/hubspot.md), [CSV import](https://docs.findtempo.co/integrations/csv-import.md) |
| Google Workspace | Email threads with the account, calendar events, and Google Meet transcripts | [Google Workspace](https://docs.findtempo.co/integrations/google.md) |
| Granola, Gong, Fathom | Call transcripts and meeting notes as calls are recorded | [Granola](https://docs.findtempo.co/integrations/granola.md), [Gong](https://docs.findtempo.co/integrations/gong.md), [Fathom](https://docs.findtempo.co/integrations/fathom.md) |
| Slack | Messages from channels mapped to a deal, by the channel's capture mode. On **Auto**, up to a year of history is imported when the channel is linked. | [Slack](https://docs.findtempo.co/integrations/slack.md) |
| Notion | Pages linked to a deal | [Notion](https://docs.findtempo.co/integrations/notion.md) |
| BigQuery | Call transcripts, CRM-captured email, and CRM notes your team already replicates to the warehouse | [BigQuery](https://docs.findtempo.co/integrations/bigquery.md) |

In the app, each artifact shows its source, such as Gong, Gmail, Slack, Notion, or CRM note. Tempo also stores its own background research for a deal; it is not something you add, and signals do not listen in it.

## How Tempo processes artifacts

Tempo processes artifacts from connections and artifacts you add by hand.

1. **Tempo ties it to a deal or its account.** Tempo ties an artifact to one deal when its source or a person names that deal, such as a Slack channel mapping, a CRM call association, or an upload. When Tempo matches it another way, such as through a deal's contacts, email-domain rules in **Settings** → **Opportunity Contacts**, or calendar events, it keeps the artifact on the deal's account. A deal with no account keeps the artifact itself.
2. **Tempo extracts observations.** Most artifacts produce typed, cited observations. A calendar event that only schedules a meeting produces none. See [Observations](https://docs.findtempo.co/context-layer/observations.md).
3. **Tempo updates CRM fields.** New evidence can produce CRM updates, depending on the field's update behavior. See [Fields and CRM updates](https://docs.findtempo.co/admin/fields.md).
4. **The artifact appears in Tempo.** It shows on the Artifacts page, in the deal's **Deal activity**, and on the deal's **Artifacts** tab. Processing progress shows in the sidebar while new artifacts are being analyzed.

An artifact kept on an account also counts as evidence for that account's deals when it falls within a deal's time span. It appears on the deal's **Artifacts** tab with an **Account** label. Deal state and answers from your AI tools can use it as evidence for that deal.

## Keep ingestion complete

Most gaps in the intelligence layer come from a source that is not connected or a deal that is not linked, not from artifacts that need to be added by hand. For admins:

* Connect every source your team uses. See [Set up your organization](https://docs.findtempo.co/admin/setup.md).
* Map each deal's Slack channel and choose its capture mode. See [Slack](https://docs.findtempo.co/integrations/slack.md).
* Link the Notion pages that hold deal plans and account notes. See [Notion](https://docs.findtempo.co/integrations/notion.md).
* Keep **Opportunity Contacts** current so email threads reach the right account and its deals.
* Watch for failed processing. When a deal has artifacts that failed, its **Artifacts** tab shows **Reprocess failed (N)**. Click it to retry. Over MCP, `manage_artifacts` with `reprocess_failed` does the same.

## Review what Tempo has

The Artifacts page is the first page you see after signing in. In the sidebar, under **Team**, click **Artifacts**.

The table lists every artifact across the deals you can access, with **Artifact**, **Type**, **Opportunity**, and **Date Added**. Use **Find artifact...** to search by title, and **Find an opportunity** to limit the table to one deal. Click a row to preview the artifact and read what was extracted from it.

Some artifacts are kept on an account rather than one deal. The table lists them too. Each shows the account name with an **Account** label. Click the account name to open its account page.

## Add something Tempo did not capture

Add an artifact by hand only when no connection carries it: a transcript from a recorder you do not connect, a document a buyer shared outside your connected tools, or a voice note after a call you took on the road.

**1. Open the deal**

Open the opportunity, then click **Add Artifacts** in the header.

**2. Pick how to add it**

Choose a panel: upload a file, **Paste text** (as notes, a document, an email, a transcript, or a chat), record or upload a **Brain Dump**, link a Granola meeting, or link a **Notion Page**.

**3. Set the date**

Each panel asks when the content happened. Tempo records that date on the artifact.

**4. Let it process**

The artifact goes through the same steps as one a connection delivered. If you paste text that already exists on the deal, Tempo tells you it is a duplicate and does not add it again.

From an AI tool, `write_artifact` adds a note, a recap, content fetched from another integration, a file, or audio to a deal. Use it for context the tool has in hand that Tempo does not sync, not for sources Tempo already reads.

## Retract an artifact

Retract an artifact when it is wrong, duplicated, or a test. Retraction is permanent.

**1. Open the deal's artifacts**

On the opportunity page, click the **Artifacts** tab.

**2. Delete the artifact**

Hover the artifact and click the trash icon.

**3. Confirm**

The dialog says "Deleting this artifact will remove any updates associated with it and regenerate affected updates. This action cannot be undone." Click **Delete**.

Retracting an artifact:

* removes every observation derived from it, so they are never cited again,
* removes pending CRM update proposals built on those observations and regenerates the deal's remaining proposals from the remaining evidence,
* deletes the stored file, and
* records an "Artifact deleted" entry in the deal's activity.

## Work with artifacts from your tools

Four MCP tools cover artifacts. See the [MCP tool catalog](https://docs.findtempo.co/developers/mcp-tools.md) for parameters.

| Tool | What it does |
| - | - |
| `list_artifacts` | Lists artifact metadata for a deal or an account, or finds artifacts whose text contains an exact phrase. |
| `get_artifact` | Reads an artifact's text in pages. |
| `write_artifact` | Adds an artifact to a deal. Kinds: `chat` for notes and recaps, `mcp` for content fetched from another integration, `file` for a document or image, `brain_dump` for audio. Every write needs an ISO 8601 timestamp with UTC (`Z`) or a numeric UTC offset. Writing content that already exists on the same deal returns the existing artifact instead of creating a duplicate. For `mcp` content, new content at a source URL already on the deal updates that artifact. If that new content already belongs to a different artifact on the deal, Tempo returns a conflict. |
| `manage_artifacts` | `retract` removes one artifact with the same effects as deleting it in the app. `reprocess_failed` retries artifacts whose processing failed. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.