> 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/docs/pt/integracoes/overview/company-context.md).

# Contexto da empresa

Os Company Context Steps conectam os seus workflows AirOps com plataformas que contêm dados empresariais valiosos sobre as operações, clientes e produtos da sua empresa. Estas integrações permitem-lhe aproveitar informações internas da empresa para criar conteúdo mais personalizado e contextualmente relevante.

Os Company Context Steps incluem:

1. [**Gong**](/docs/pt/integracoes/overview/company-context/gong.md) -- acesso a gravações de chamadas, transcrições e metadados das suas conversas de vendas

As integrações Company Context transformam a forma como cria conteúdo ao incorporar dados empresariais reais das suas conversas de vendas. Estas ligações permitem-lhe criar workflows que aproveitam insights dos clientes e inteligência de vendas.

Com os Company Context Steps, pode criar workflows que extraem insights de chamadas de vendas para informar a estratégia de conteúdo, criar estudos de caso a partir de conversas de vendas bem-sucedidas e aproveitar o feedback dos clientes proveniente das conversas.

{% hint style="info" %}
Nota: os Company Context Steps foram concebidos para aplicações Workflow. A autenticação requer as permissões de administrador adequadas para cada plataforma respetiva.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.airops.com/docs/pt/integracoes/overview/company-context.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.