Practical examples of GraphQL queries for fetching calls, signals, and documents from the BuildBetter API.
interview
field to list calls. We request id
, name
, and started_at
for each call. The nested type
selection fetches the call’s type name (if types are used in your setup). The attendees.person
nested selection fetches each participant’s first and last name. The result will be an array of up to 5 calls, each with a list of attendees. If you need more calls, adjust the limit
or use pagination.$callId
to filter extraction
records for a specific call. The query returns signals sorted by their occurrence time in the call. For each signal, we get the summary
and context
text. We also get start_sec
and end_sec
which indicate when in the call the signal happens. The types
array gives the category of the signal, and topics
gives any tagged topics. Finally, attendee.person
provides the name of the participant who spoke that signal’s content. This query is useful to display a timeline of important points in a call along with who said them and what they are about.$callId
with the actual call ID you want to inspect. If running via a GraphQL client, provide callId
in the query variables. Only signals from calls you have access to will be returned (others are filtered out by the server’s permissions).
document_by_pk
field to fetch a single document by its primary key (ID). For that document, we request its name
, status
, and content
. We also get the created_at
timestamp and the creator
(with the creator’s name). The input_data
array is included to list any calls that contributed to this document. For each related call, we fetch its id
, name
, and started_at
. If the document was created from multiple calls, you will see multiple entries in input_data
. If it was from a folder, the call
field would be null and a folder
field might appear (not requested above for brevity).docId
. The response will give you the document’s content and relevant metadata. For example, you can display the document’s title, status (e.g., Completed or Processing), who created it, and list the calls that were summarized to create it.
These examples can be modified as needed – you can request additional fields or fewer fields depending on what you need for your application. Remember that GraphQL will only return the fields you ask for, so omitting fields can reduce payload size.