> For the complete documentation index, see [llms.txt](https://docs.airops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airops.com/context/overview/company-context.md).

# Company Context

Company Context Steps connect your AirOps workflows with platforms that contain valuable business data about your company's operations, customers, and products. These integrations enable you to leverage internal company information for more personalized and contextually relevant content.

The Company Context Steps include:

1. [**Gong**](/context/overview/company-context/gong.md) -- access call recordings, transcripts, and metadata from your sales conversations

Company Context integrations transform how you create content by incorporating real business data from your sales conversations. These connections allow you to build workflows that leverage customer insights and sales intelligence.

With Company Context Steps, you can build workflows that extract insights from sales calls to inform content strategy, create case studies from successful sales conversations, and leverage customer feedback from conversations.

{% hint style="info" %}
Note: Company Context Steps are designed for Workflow applications. Authentication requires appropriate admin permissions for each respective platform.
{% endhint %}


---

# 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.airops.com/context/overview/company-context.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.