> For the complete documentation index, see [llms.txt](https://docs.filed.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.filed.com/reference/plugins/integrations/communications/ping.md).

# Ping

Connect Ping so Filed can read what was said in your client meetings — the meeting list, transcripts, the summaries Ping writes, and the action items it picks out. Ping stays the system of record. Filed only reads; it never creates, edits, or deletes anything in Ping.

Ping connects through its own sign-in and consent page. You authorize Filed for one Ping workspace, and Filed names the connection after it.

## Before you start

* A Ping login with access to the workspace whose meetings Filed should read.
* API access enabled for that workspace. Ping's public API is in beta and each workspace is enabled by Ping — ask them if you have not been enabled yet.

## What Filed asks Ping for

When you authorize Filed, Ping shows the access Filed is requesting:

* **Read your profile and workspace** — so the connection can be named after the workspace it opens.
* **Read meetings** — titles, times, and status.
* **Read transcripts** — the speaker-by-speaker record of a meeting.
* **Read summaries** — the summaries Ping has finished writing.
* **Read action items** — the follow-ups Ping extracted, with status and due date.

Every one of these is read-only. Filed cannot start a recording, change a meeting, or tick off an action item in Ping.

## Connect Ping

{% stepper %}
{% step %}

### Start the connection in Filed

Go to **Plugins**, open **Ping** under communications, and click **Connect**. Name the connection so your team can tell which Ping workspace it opens.
{% endstep %}

{% step %}

### Authorize Filed in Ping

Filed opens Ping in a small window. Sign in if prompted, choose the workspace Filed should read, and approve the access request.
{% endstep %}

{% step %}

### Wait for verification

Filed confirms the authorization and reads the workspace details. The connection becomes **Active** and is named **Ping (workspace name)**.
{% endstep %}
{% endstepper %}

To read a different Ping workspace, connect Ping again and authorize that one. Each connection opens exactly one workspace.

## What Filed can do with Ping

Ask **Analyst** about a connected workspace. It can:

* List the meetings in the workspace and open any one of them
* Read a meeting's transcript, with each speaker's words in order
* Read the summaries Ping has completed for a meeting
* List the action items Ping extracted, with their status and due dates

{% hint style="info" %}
**Ping does not know your Filed clients.** Its API carries no client or participant information, so Filed cannot file a meeting against a taxpayer on its own. Name the meeting you mean — by title, date, or the client discussed in it — and Analyst will find it.
{% endhint %}

## Example prompts

* "Summarize what we agreed with the client in this week's Ping meetings"
* "Pull the transcript of yesterday's planning call and list the tax positions discussed"
* "What action items came out of the last meeting in Ping?"

## Troubleshooting

### Ping shows an error instead of the authorization page

Confirm you are signed in to the Ping account that can reach the workspace. If Ping reports that Filed is not available to your organization, ask Ping to enable API access for your workspace.

### A transcript comes back empty

Ping only has a transcript once it has finished processing the recording, and some meetings never get one. Analyst will say the transcript is not available rather than guess at its contents — check the meeting in Ping.

### A meeting is missing from the list

The connection sees only the meetings the authorized account can reach in the workspace it was connected to. Check the meeting in Ping under that account, and connect the other workspace if it lives somewhere else.

### The connection stopped working

Ping's access expires or can be revoked in Ping. Open the connection in Filed and choose **Reconnect** to authorize it again. The connection keeps its name and history — do not create a second connection to work around it.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.filed.com/reference/plugins/integrations/communications/ping.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.